> The thought that occured to me before was that we might need to take > a bit of a stand in libssh2 here on whether it should provide error > codes that are close to the protocol errors (which I would prefer) or > whether it should try to be smart and cook protocol error codes into > something that could be expected that application writers would > prefer, or just where we think that protocol errors suck.
Which protocol errors are we actually talking about here? According to the spec the only error that all the various authentication methods return is SSH_MSG_USERAUTH_FAILURE. There don't seem to be any method-specific errors. So why does libssh2 have them? If it's just a matter of libssh2 cooking up separate error codes for its different authentication methods, then I think we should revisit the option of making them all return some common LIBSSH2_ERROR_USERAUTH value. After all, that would be the protocol error. Or am I misunderstanding this? Alex _______________________________________________ libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
