The issue I posted below has apparently been solved. I looked back through the list archive and found someone had responded to a similar question by stating 'do not run sshd from inted'. Well, I was running it from inetd. I took it out and started running as a standalone daemon and all is well. So, in a way this is solved, but in a way it brings up a new question. Why does it not run properly under inetd? The person who responded as above said it had to do with the length of the auth key - why would that matter under inetd but not as a stand-alone daemon? Thoughts? -Keith I'm having a a couple separate issues with ssh2: 1) Can not initiate a client session as a non-root user from a UNIX box (Solaris or DecUNIX). I get the following error: Disconnected; protocol error (Protocol error: packet too long: -645693011.). I've seen postings on this before, but no resolution. I have no problems connecting to the same ssh2 server from Mac or Win clients, it is only when using the UNIX client included with the ssh2 source. One person suggested that it was a debug message being written in plain-text to the encrypted stream. I'm not sure what I am looking for when I do a 'truss' and I'm not sure how to resolve anything if I find an issue. Suggestions? -Keith
