 | 1 | initial version |
Okay, in my case I traced this back to the user account that I was attempting to login with, had an invalid shell setup on the host in /etc/passwd.
Why it was working with most other terminals is a bit of a mystery, but I suspect it's because with those programs you can explicitly set the shell you want to use for that connection (which I had done).
| | 2 | No.2 Revision |
Okay, in my case The other obvious thing to check is that your key doesn't have a passphrase on it. Alternatively, if it does, make sure you are providing the passphrase to wireshark each time you attempt to capture from SSH (it doesn't store the passphrase, it must be provided anew each time).
My situation was different, I traced this back to the user account that I was attempting to login with, had an invalid shell setup on the host in /etc/passwd.
Why it was working with most other terminals is a bit of a mystery, but I suspect it's because with those programs you can explicitly set the shell you want to use for that connection (which I had done).
Copyright Wireshark Foundation, 2017-2023 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
