Closed myeong closed 8 years ago
Hi @myeong, and thank you for using Flintrock.
Unfortunately, detecting when the provided username is incorrect is surprisingly difficult.
If you have any suggestions on how better to handle this situation I'm all ears!
Thanks for the quick response. For a quick and dirty solution, how about changing the error message something like "your AWS key or username has a problem"? I will keep exploring for the issue meanwhile :)
When I put in an incorrect username, I get this error:
paramiko.ssh_exception.SSHException: Error reading SSH protocol banner[Errno 54] Connection reset by peer
So it's different from the error you see, which goes to my earlier comment about this being difficult to catch and report on properly without potentially confusing the user if the problem is actually something else.
I'm going to close this for now, but I am still interested in nudging the user in the right direction if it can be done without risking further confusion.
Maybe catching certain SSH exceptions and offering a hint of what might be wrong is the right thing to do. I'm not sure, but I would consider a PR that added this.
When I put a wrong user name for an AMI (the correct user name was "root", but I put my AWS user name) and I got this error.
Just reporting that this error message needs to be fixed -- since it's not a key problem. Thanks!