Kevin, Did you check the sftp subsystem line in your sshd_config file?
You will need to generate the server key pair when you install openssh. I usually build from source on that, and to be honest I'm not real current on the default .rpm install under Trustix 2.2. I would have to think they are taking care of this step during the installation phase of the rpm, but you may want to check the directory where the install files are kept and make sure you have valid host keys set up for RSA and DSA. If you are using password authentication for you connecting client(s) then you don't need to set up key pairs for the connecting user(s). You might want to look into that at some point, but it isn't necessary to connect. I don't have a Trustix system I can connect to at the moment to look at the defaults in sshd_config, but they should be reasonable. Make sure Password Authentication is allowed. Also, make sure you are using SSH version 2 to connect. If you need further assistance, please let me know if you can connect with a direct SSH connection, what protocol you are using to connect. It would help to know what client you are using and it would be helpful to see your sshd_config file. For obvious reasons, you should send that in a private message, and not to the whole group. Let me know if you need further assistance. Paul Mansmann MCSE, CCA, CCNA, CISSP CEH, CWNA, CWSP, CIWSA IT Systems Influencer -----Original Message----- From: Kevin Davis [mailto:[EMAIL PROTECTED] Sent: Monday, January 31, 2005 10:30 AM To: 'Paul Mansmann' Cc: [email protected] Subject: RE: new install TSL 2.2: where's SFTP? Paul, This all seems very straightforward, yet when connecting via WinSCP requesting SFTP connection (port 22), I get the following error: Connection has been unexpectedly closed. Server sent command exit status 127. Cannot initialize SFTP protocol. Is the host running an SFTP server? I can connect successfully with SCP fallback. However to view or edit any files (even within my own home directory) I get the same "status 127" error. All I'm looking for is a way to edit files remotely, without having to use vi at the shell. Apparently the default RPM install of OpenSSH isn't allowing for this? Could this be some kind of authentication issue? Am I supposed to generate keys or something in order to complete OpenSSH setup? I'll keep deciphering the man pages for this, but thanks for any assistance. Kevin Davis _______________________________________________ tsl-discuss mailing list [email protected] http://lists.trustix.org/mailman/listinfo/tsl-discuss
