Some services run really good behind a reverse proxy on 443, but some others can really become an hassle… And sometimes just opening other ports would be easier than to try configuring everything to work through 443.

An example that comes to my mind is SSH, yeah you can use SSLH to forward requests coming from 443 to 22, but it’s so much easier to just leave 22 open…

Now, for SSH, if you have certificate authentication or a strong password, I think you can feel quite safe, but what about other random ports? What risks I’m exposing my server to if I open some of them when needed for a service? Is the effort of trying to pass everything through 443/80 worth it?

  • ganymede@lemmy.mlEnglish
    2·
    11 hours ago

    People iterate through all the IPv4 addresses since there are only 4,294,967,296 possible addresses. There are 340,282,366,920,938,463,463,374,607,431,768,211,456 possible IPv6 addresses

    i love your thinking!!

    do you have a backup in case you accidentally find yourself locked out from an ipv4-only network?

    • bigfondue@lemmy.worldEnglish
      2·
      9 hours ago

      Not really. My home network doesn’t have any port forwarding so nothing is exposed. I have a VPS, but nothing really important is on there, and I pretty much exclusively use it from home. Anyway all those failed logins were just trying defaults like user admin password admin. If you have a strong password or ssh key it really doesn’t matter, but I just hated knowing people were trying to get in, even if it was just half-assed attempts to find a unsecured machine.

      If I really needed to use IP4 to get in, I could always just log onto Vultr’s web console and enable IP4 again.