no comments (yet)

sorted by: hot top controversial new old
there doesn't seem to be anything here
3 comments in c/privacy@programming.dev view that post
[–] 9 points 2 weeks ago*

If your remote host changes and you don't know why, and login anyway, it's on you.

Dirty trick tho, could definitely have caught me if I was in a lazy mood.

Side note, why ssh over 22 anyway? It's so easy to change just to avoid lazy bots.

  • source
  • [–] 4 points 2 weeks ago (1 child)

    That warning about a modified fingerprint only applies if you’ve sshed to that host before. How many people carefully check the fingerprint if it’s the first time they’ve connected?

  • source
  • hideshow 1 child comment
  • [–] [S] 1 point 2 weeks ago

    That's a good point. If you are using a physical server you own, hopefully you set it up locally first. If you are using a VPS, hopefully you configured it with key authentication from the get go. Otherwise, you'd need to find a way to identify that the box you ssh-ed into is indeed the one you expect. Luckily, if it's your first time logging in, then you probably don't have any data in the server either, so there's nothing to steal if the hackers get your password. So just enter your password, see if it's the right box, and if not then reset it and try from a different tor circuit.

  • source
  • parent
  • 1 comment in c/pulse_of_truth@infosec.pub view that post
    [–] 2 points 2 weeks ago

    reposting what I commented in another thread:

    SSH MitM attacks are very easy to pull off. To secure yourself, use key authentication instead of passwords, and don't ignore the warning that SSH will give you saying "WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED".

    If you are using something like Tails, you will need to make sure to persist the ssh hosts key file (~/.ssh/known_hosts), or else you will not not be warned when a MitM attack is being performed.

    More discussion here: https://news.ycombinator.com/item?id=50166257

  • source