SSH Terminal Password and FTP Problem

[Madcamper]

I have just finished getting my tinycore machine setup. I am using it as an FTP server for myself over the net. I have SSH, and bftpd running on it, but when I try to ssh into the machine from cygwin on my xp laptop it accepts the password, but then comes back with the connection is closed. Along with my the ftp part, when i login and upload a file, then reboot the server, the files are gone once its all loaded up again. I added user=user in the menu.lst for grub and it worked for letting me login, but the host key kept changing. I have the restore=hda1/ in the menu.lst as well.
Any help would be greatly appreciated!

[Lee]

Uploaded files will, by default, land in the logged ftp user's home directory which is, by default, in RAM.  Unless you do a backup before shutting down/rebooting, the files will be gone.

Regarding the changing host key, you can add that to your backup but I don't remember what file(s).  Search the forums - it is probably mentioned somewhere.  In any case, a changing host key should just make your ssh client bitch about it and disconnect but in the process it will also tell you what line to change (delete) in your known hosts file on the client PC (within your cygwin home directory).

If you use openssh instead of dropbear, you can use secure ftp instead of regular ftp, if that would be important to you.  That also allows the mounting of your ftp home directory as a filesystem on a remote computer (see the sshfs-fuse-2.2.tcz extension).

If none of the above helps, come on back.  I have worked through these issues even if I don't remember all the details right away.

[combo3]

The host key locations for:

Dropbear - /etc/dropbear
OpenSSH  - /etc/ssh

To make them persistent across boots add one of the following:

echo etc/dropbear >> /opt/.filetool.lst
echo etc/ssh >> /opt/.filetool.lst

Then save your setting by clicking on Control Panel > Backup/Restore


To aid in troubleshooting your ssh problem:

1. Enable error logging on the host server

sudo touch /var/log/lastlog
sudo syslogd

Error messages will log to /var/log/messages

2. Include the -v debugging option in your ssh command.

3. Verify that can you connect without error:

- via localhost on the server
- from a client on the local network

Assuming that works and the problem is indeed remote:

Have you tried connecting with PuTTY to rule out cygwin as the culprit?
Are you using tcp_wrappers on the host?
Is your client running behind a proxy?