Timeline for What are possible implications of ignoring the ssh host key warning?
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 7, 2022 at 16:41 | history | edited | Manfred Kaiser | CC BY-SA 4.0 |
updated commands to SSH-MITM 1.0.0
|
| Nov 11, 2021 at 21:25 | vote | accept | x-yuri | ||
| Nov 9, 2021 at 16:20 | comment | added | x-yuri | So, is this only part of the truth? My guess is, the article is only considering the case where an attacker wants to just listen in on the communication. And with pubkey auth that will fail. But an attacker can be smarter then that. He can authenticate the client, then authenticate on the server (if he's able to employ a possibly forwarded agent), and after that he can retransmit the packets as is. Or just present the user with a fake server (a honeypot), if he can't exploit the client's agent. Is that so? | |
| Nov 9, 2021 at 11:17 | history | edited | Manfred Kaiser | CC BY-SA 4.0 |
added poc how to do a mitm attack on publickey authentication
|
| Nov 9, 2021 at 10:19 | history | edited | Manfred Kaiser | CC BY-SA 4.0 |
added 61 characters in body
|
| Nov 9, 2021 at 10:12 | history | edited | Manfred Kaiser | CC BY-SA 4.0 |
added 61 characters in body
|
| Nov 9, 2021 at 10:06 | history | edited | Manfred Kaiser | CC BY-SA 4.0 |
added 141 characters in body
|
| Nov 9, 2021 at 9:27 | history | edited | Manfred Kaiser | CC BY-SA 4.0 |
added 70 characters in body
|
| Nov 9, 2021 at 9:19 | history | answered | Manfred Kaiser | CC BY-SA 4.0 |