On Wed, 1 Jan 2003 02:33:13 -0800 Ben Rosenberg wrote:

If the machine has sshd running then why not use sftp to pull your files? If you want plain old ftp then your gonna have to run an ftpd and in most cases it's a bigger security risk then nessassary. You can even get the kio_fish plugin for KDE and use Konqueror to sftp to the server you want to transfer files to or from. I would suggest doing this because it's much more secure then plain ftp. If you need a Windows client for a user that you have then push them into the direction of WinSCP which resembles CuteFTP but does it's transfers over ssh.

A good idea to use sftp, as I have the sshd running. Now I have installed the kio_fish too. I opened the Konqueror, and wrote sftp://192.168.1.5, and in the login area, I entered root, and the password. I was logged in on the other machine, but the screen shows: sftp://192.168.1.5/root And I'm in a /bin directory, and cannot see any further directories on the other computer ?.

Regards. -- Ben Rosenberg ---===---===---===--- mailto:ben@whack.org Tell me what you believe.. I'll tell you what you should see.

-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com

-- Erik Jakobsen

Hi Ben. I opened the Konqueror file manager, and it is running now. Thanks for the help, and a Happy New Year 2002.

-- Erik Jakobsen

-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com

-- Erik Jakobsen

On Wed, 01 Jan 2003 18:57:33 +0800 Dennis wrote:

login as user and not root for ftp.

I cannot get in with user: eurit:~ # ftp 192.168.1.5 ftp: connect: Connection refused -- Erik Jakobsen

On Wed, Jan 01, 2003 at 12:39:53PM +0100, Erik Jakobsen beat on the keyboard:

On Wed, 01 Jan 2003 18:57:33 +0800 Dennis wrote:

...

login as user and not root for ftp.

I cannot get in with user:

eurit:~ # ftp 192.168.1.5 ftp: connect: Connection refused

-- Erik Jakobsen

-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com

Look at your inetd.conf and make sure you have the ftpd properly configured, you may need to uncomment the appropriate ftp daemon. -- _ _ __ _____ _____ ___| |_ | '__| / __\ \ /\ / / _ \/ _ \ __| -o) | | _ \__ \\ V V / __/ __/ |_ /\\ |_|(_) |___/ \_/\_/ \___|\___|\__|_\_v rsweet@garagenetworks.net "unix soit qui mal y pense."

On Saturday 04 January 2003 10:07 am, Robert Sweet wrote:

On Wed, Jan 01, 2003 at 11:27:29AM +0100, Erik Jakobsen beat on the keyboard:

...

As root, I can access another machine here with ssh, but I cannot do an ftp connect.

[snip example]

Bad habit. SSH is ill configured to allow root login.

err, no(*) -- the first S stands for SECURE. A "bad habit" would be to login via TELNET "as root" as the entire transmission, including passwords, is "in the clear" [likewise with ftp] many distro's now will disable using "root" for communications like this [anything that invloves a plaintext password] for just this reason. ssh works by establishing a connection to the host, deciding on a "key" for encryption/decryption, and encodes everything from the get-go. It is therefore "safe" to use a "root" logon from machine to machine. In addition to ssh itself, there is the program "scp", which allows for "securely" copying files from one machine to the next -- admittedly, not as convenient as an FTP 'session' where you can navigate around the remote system and copy-at-will, but functionally just as effective [moreso -- you might be a "plain user" here, but could copy a file to a location that "only root can write" remotely -- presuming, of course, you are indeed the root user of the remote site]

You should get used to using a user login and su for root privileges when needed.

That can lead to "false [sense of] security" -- if you use telnet for your "non-root-user-acces", you gain nothing -- when "su" [or sux] prompts for a password, that password again goes "in the clear" -- you might as well have used a "root" logon from the start. Tom (*) what exactly, though, do you mean by "ill configured"? Are you concerned that the [remote] ssh server might somehow be "trojaned", so that logging on "as root" on the remote site might cause difficulties at the remote site?