2 ms·

Would recommend Tailscale over SSH. Really easy to setup/use and means you don't have to open up ports like 22 which are constantly being port scanned.

imgabe 4y ago
You can move ssh to a different port.
- indigodaddy 4y ago
  Anyone who thinks they need to move ssh to a different port likely doesn’t have their ssh security configuration setup optimally.
  - gnramires 4y ago
    Making it explicit: try to always use keys for ssh, avoid passwords. If you have to use passwords, make it very long (20+ chars) and random. Don't use dictionary words or reuse passwords from anywhere else.
    - indigodaddy 4y ago
      Yep, and I always additionally just disable pw authentication altogether, and set PermitRootLogin to either No or without-password. You can also do things like firewalld off (or with hosts.allow) 22 to just an ssh bastion/jumphost src (or your house IP), but I find that’s usually not necessary (although an excellent further step if you are a bit paranoid) as long you do what was mentioned in first paragraph.
  - komali2 4y ago
    I don't get it, wouldn't you use ssh keys and also just move it to a different port anyway to save the annoyance of random scriptkiddy pokes all the time?
  - piaste 4y ago
    Moving the port away from 22 changed my fail2ban logs from hundreds of lines a day to one every few weeks at most. While you shouldn't skip on other security measures, there's no real downside to changing your SSH port and getting off the target list for a lot of botnets. (As opposed to e.g. port knocking, which is stronger but makes it easy to lock yourself out and may create issues with some SSH clients.)
  - cube00 4y ago
    There's other reasons to use a different port. I move it to cut down on the failed login attempts (yes they'll never succeed given I only allow keys) but they clutter the log so I can't tell if I'm actually being targeted or not. On an obscure port if I do see attempts I know something serious is going on.
saghm 4y ago
I'm not familiar with Tailscale, but you can easily use a different port than 22 for ssh if you want to; put a different port number in `/etc/ssh/sshd_config` on the server, and then set your `~/.ssh/config` to use that port on your clients. If you're going to be opening it up externally, you also can map a different port to the local one (which is necessary if you want to be able to ssh into two different servers with the same ssh port from the outside anyhow).

imgabe 4y ago

You can move ssh to a different port.

indigodaddy 4y ago
Anyone who thinks they need to move ssh to a different port likely doesn’t have their ssh security configuration setup optimally.
- gnramires 4y ago
  Making it explicit: try to always use keys for ssh, avoid passwords. If you have to use passwords, make it very long (20+ chars) and random. Don't use dictionary words or reuse passwords from anywhere else.
  - indigodaddy 4y ago
    Yep, and I always additionally just disable pw authentication altogether, and set PermitRootLogin to either No or without-password. You can also do things like firewalld off (or with hosts.allow) 22 to just an ssh bastion/jumphost src (or your house IP), but I find that’s usually not necessary (although an excellent further step if you are a bit paranoid) as long you do what was mentioned in first paragraph.
- komali2 4y ago
  I don't get it, wouldn't you use ssh keys and also just move it to a different port anyway to save the annoyance of random scriptkiddy pokes all the time?
- piaste 4y ago
  Moving the port away from 22 changed my fail2ban logs from hundreds of lines a day to one every few weeks at most. While you shouldn't skip on other security measures, there's no real downside to changing your SSH port and getting off the target list for a lot of botnets. (As opposed to e.g. port knocking, which is stronger but makes it easy to lock yourself out and may create issues with some SSH clients.)
- cube00 4y ago
  There's other reasons to use a different port. I move it to cut down on the failed login attempts (yes they'll never succeed given I only allow keys) but they clutter the log so I can't tell if I'm actually being targeted or not. On an obscure port if I do see attempts I know something serious is going on.

saghm 4y ago

I'm not familiar with Tailscale, but you can easily use a different port than 22 for ssh if you want to; put a different port number in `/etc/ssh/sshd_config` on the server, and then set your `~/.ssh/config` to use that port on your clients. If you're going to be opening it up externally, you also can map a different port to the local one (which is necessary if you want to be able to ssh into two different servers with the same ssh port from the outside anyhow).