Apparently I installed that thing in 2006 and I last updated it in 2016, then I quit updating it for some reason that I totally forgot. Probably laziness…

It’s been running for quite some time and we kind of forgot about it in the closet, until the SSH tunnel we use to get our mail outside our home stopped working because modern openssh clients refuse to use the antiquated key cipher I setup client machines with way back when any longer.

I just generated new keys with a more modern cipher that it understands (ecdsa-sha2-nistp256) and left it running. Because why not 🙂

  • n2burns
    link
    fedilink
    arrow-up
    141
    arrow-down
    4
    ·
    14 days ago

    Because why not 🙂

    Because security.

    • ExtremeDullard@lemmy.sdf.orgOP
      link
      fedilink
      arrow-up
      52
      arrow-down
      18
      ·
      edit-2
      14 days ago

      It’s behind a firewall. The only thing exposed to the outside is port 22 - and only pubkey login too.

      And gee dude… It’s been running for 18 years without being pwned 🙂

      • n2burns
        link
        fedilink
        arrow-up
        66
        arrow-down
        3
        ·
        14 days ago

        And it’s not like it contains any sensitive information. I’m sure all your emails are just friendly correspondence with your pen pal.

      • schizo@forum.uncomfortable.business
        link
        fedilink
        English
        arrow-up
        33
        arrow-down
        2
        ·
        14 days ago

        I’d still maybe build a modern OpenSSH package.

        There’s been an awful lot of RCEs in the past two decades and uh, if that’s rawdogging the internet, I’m honestly shocked you haven’t been hit with any by now.

        • Sbauer@lemmy.world
          link
          fedilink
          arrow-up
          3
          ·
          13 days ago

          Eh, building anything modern on a system that old would be painful I bet.

          Maybe you could use https://github.com/openssh/openssh-portable since that’s meant to be portable. I’d certainly would give it a try if I didn’t want to bother trying to upgrade that system. Then again, trying to upgrade it through the releases to a modern Debian might be fun too.

      • Lucy :3@feddit.org
        link
        fedilink
        arrow-up
        25
        arrow-down
        2
        ·
        14 days ago

        How do you know? Do you constantly monitor running processes, performance and network connections?

      • rhacer@lemmy.world
        link
        fedilink
        English
        arrow-up
        8
        arrow-down
        2
        ·
        14 days ago

        Did you really only use it when you were home? If you used it outside the firewall then port 25 must have been open also.

        I used to run my own server and this was in the early 90s. Then one day, perusing the logs I realized I was not smart enough on the security front to even attempt such a thing. It was quickly shut down and the MX record moved to an outsourced mail provider.

    • psycho_driver@lemmy.world
      link
      fedilink
      arrow-up
      7
      arrow-down
      11
      ·
      14 days ago

      Most ‘hackers’ are just mid tier (mediocre) IT level types who rely on existing exploits floating around in the wild. It’d probably be hard to find any still in circulation for such an old system.

      • limonfiesta@lemmy.world
        link
        fedilink
        English
        arrow-up
        23
        arrow-down
        1
        ·
        edit-2
        14 days ago

        We’re not talking about some punch card COBOL machine he jimmy rigged with network access, it’s an old Debian Linux box with SSH enabled.

        It’s not like Metasploit would have a tough time finding unpatched vulnerabilities for it…

          • limonfiesta@lemmy.world
            link
            fedilink
            English
            arrow-up
            2
            arrow-down
            1
            ·
            edit-2
            14 days ago

            Unless it’s for SMTP only, it’s probably a back end sever to some other front facing box, or service, that has IP addresses whitelisted for email.

            I’m pretty sure I read one of his comments elsewhere talking about tunneling everything over SSH, so I assume that’s what he meant, but I could be mistaken.

            Regardless, using an EOL distro as an internet facing SSH server that’s 8 years behind on SSH updates, is probably a bad idea.

      • Possibly linux@lemmy.zip
        link
        fedilink
        English
        arrow-up
        4
        arrow-down
        2
        ·
        14 days ago

        It isn’t the “hackers” you should worry about. Its the nation states that take over huge numbers of machines.

          • Possibly linux@lemmy.zip
            link
            fedilink
            English
            arrow-up
            1
            ·
            edit-2
            13 days ago

            I was more referring to foreign countries and cyberwarfare. Like it or not counties have now realized cyberattacks can be very devastating. A compromised server may very well be used for all sorts of purposes that many are probably not ok with.

        • PlexSheep@infosec.pub
          link
          fedilink
          arrow-up
          1
          arrow-down
          1
          ·
          13 days ago

          As a private person, defending against nation threat actors is impossible. And not only as a private person, but even as a medium sized company.

          • Possibly linux@lemmy.zip
            link
            fedilink
            English
            arrow-up
            3
            ·
            13 days ago

            You just need to not be the easy target. You don’t need outrun the bear you just need to be ahead of whatever Joe is doing