On Thu, Apr 19, 2018 at 03:03:20PM -0700, Stephen Casner wrote:
Thanks for the debug outputs. For the buster case where the connection immediately closes, there must be something about the DH handshake that the server can't handle, but the client-side debug output doesn't indicate what that might be. You can enable some logging by the server on the USB/async console with the command:
log level debug wolfssh
This causes a lot of blathering that won't be useful, but there may be a useful hint near the end of it. Maybe that will tell us something for the squeeze case as well.
The log output was very brief: E (43385740) ssh: Error in reception: -20 I tried a few more times, and got: E (43507430) ssh: Error in reception: -20 E (43516610) ssh: Error in reception: -20 E (43647420) ssh: Error in reception: -20
You can install your RSA public key as follows, ...
Will do, thanks.