I’ve been playing around with the Erlang SSH application lately and I’ve noticed some weird behaviours which I decided to report here for future reference.
The general impression that I got from the application - and from its coursins such as crypto, public_key and ssh - is that it does not reflect the usual OTP quality standards and that it should be used with care.
Misleading error message on ssh_sftp:start_channel/1 in case of missing shell
When starting a SFTP channel towards a system where user does not have
a shell (i.e. it has
/bin/false or equilvalent assigned in the
/etc/passwd a misleading error message is returned to the user:
This has been experienced in both R16B03 and R15B03.
Crash on SSH connect
On R16B03, when connecting via SSH on OS X Mavericks I get:
Internal Crash is not real when using the key_cb option
When using the key_cb option on
ssh:connect/3 the user should
implement a series of callback functions. Not implementing them and
trying to connect results in an “internal error” which invites the
user to send a bug report. The undef callback function should be
catched and reported as a normal error, not an internal one.