Get the "Authentication Error" as soon as possbile #290
-
Hi,
or
But when I try the incorrect usernames&passwords (root/r00t, admin/admin, root/root1, ...), it would use about 2s to respond an AuthenticationError. It's too slow to scan over 100K servers. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
@pkittenis, Can you help me, pls? |
Beta Was this translation helpful? Give feedback.
-
Thank you for the reply. @pkittenis I'm trying to find a way to let the client know that it has used the wrong username/password as soon as posssible. As we know, the SSH connection steps are as follows: 1, Client: creates a TCP socket (denoted by TCP-S) connected to Server on port 22; Then, they exchange and share a session key (denoted by SK) to each other. 2, Client: encryptes "root/root" (or encryptes "root/r00t") with SK, and sends the cyphertext to Server. 3, Server: decryptes the cyphertext with SK, verifies the plaintext, and then tells Client: "yes, root/root is correct and you can access me", or "root/r00t is wrong ...". 4, Client: knows root/root is correct (or root/r00t is wrong). 5, Some followup steps ... Is there a method satisfied that: when the client knows root/r00t is wrong, it will do nothing with the followup steps but continues to use TCP-S to loggin with "root/123456", "root/1111111", "admin/admin", and so on? 1, Clients: TCP-S = socket(host = 192.168.1.5, port = 22) Thank you so much. |
Beta Was this translation helpful? Give feedback.
@pkittenis, Can you help me, pls?
Thank you.