Timeline for How to correctly secure a ssh session against MITM attack?
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Jul 25, 2020 at 19:32 | history | edited | D.W. | CC BY-SA 4.0 |
While SSH Keys are a good start, to actually be able to prevent MITM attacks the use of SSH certificates is required.
|
| S Jul 25, 2020 at 19:32 | history | suggested | Nibious | CC BY-SA 4.0 |
While SSH Keys are a good start, to actually be able to prevent MITM attacks the use of SSH certificates is required.
|
| Jul 25, 2020 at 14:24 | review | Suggested edits | |||
| S Jul 25, 2020 at 19:32 | |||||
| Jul 31, 2019 at 19:22 | comment | added | michau | "unless you have verified the public key fingerprint somehow". This "somehow" is the key. What are the actual practical ways of handling the scenario of ssh suddenly telling the user that the server's key has changed? Or is it the case that nobody really cares about MITM attacks, and everybody simply adds the new key without doing any verification? | |
| Mar 17, 2017 at 13:21 | history | edited | CommunityBot |
replaced http://security.stackexchange.com/ with https://security.stackexchange.com/
|
|
| Nov 5, 2012 at 6:58 | vote | accept | Paperghost | ||
| Nov 5, 2012 at 6:24 | history | edited | D.W. | CC BY-SA 3.0 |
added 246 characters in body
|
| Nov 5, 2012 at 6:18 | history | answered | D.W. | CC BY-SA 3.0 |