Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I had a difficult time getting Blogger.com to publish my blog to my host using SFTP. I was receiving the following error message:
"005 Unable to connect to SFTP server: Session.connect: java.net.SocketTimeoutException: Read timed out".
Oddly I was able to connect using my own SFTP client. When I went to run SSHD in debug mode to see if I could find any hints of the problem I had to stop the normal SSHD and XINETD from running. I ran SSHD in debug mode and Blogger.com published without any problem. So I started SSHD and XINETD again and Blogger.com published without any problem too!
I guess the Microsoft Windows method of solving problems (i.e. turn off the car, roll up the windows, start the car again) works in Linux sometimes too.
From the sequence of events, it sounds like sshd wasn't running when you started. Is it set to auto-start on boot? Did it fail in startup for some reason (check your logs). Unlike Windows, you can always get the root cause in Linux if you're willing to work on it. You have everything the software developer has (source code and compiler).
Macemoneta - Thanks for the help. I think sshd had to have been running because otherwise I wouldn't have been able to SFTP to the host from my own SFTP client. It is set to autostart on boot. When I went to shutdown sshd the control panel indicated that it was running. I figured out how to view the log but that was only after I decided to restart the sshd. Anyway it works now!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.