But that's not what we're talking about.  We are talking about going
directly to a Linux system.

Mark

-----Original Message-----
From: Wolfe, Gordon W [mailto:[EMAIL PROTECTED]
Sent: Friday, June 27, 2003 1:34 PM
To: [EMAIL PROTECTED]
Subject: Re: Changing runlevels etc


There are a few cases when you have to use ftp instead of scp.  Like
transferring files to and from an VM/CMS system.  ssh is not implemented on
VM, more's the pity.

"Great Minds discuss ideas.  Average minds discuss events.  Small minds
discuss people."  - Admiral Hyman Rickover
Gordon Wolfe, Ph.D.  (425)856-5940
VM Enterprise Servers, The Boeing Company

> ----------
> From:         Post, Mark K
> Reply To:     Linux on 390 Port
> Sent:         Friday, June 27, 2003 10:11 AM
> To:   [EMAIL PROTECTED]
> Subject:      Re: Changing runlevels etc
>
> Use scp, not ftp.  The ftp protocol is just as insecure as telnet.  There
> are ftp with ssl implementations, but they're not in very wide use yet.
The
> scp command comes with the OpenSSH package, and provides fully encrypted
> data transfer, along with secure and encrypted user authentication.
>
>
> Mark Post
>
> -----Original Message-----
> From: Tom Duerbusch [mailto:[EMAIL PROTECTED]
> Sent: Friday, June 27, 2003 1:06 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Changing runlevels etc
>
>
> Is that also why I can't ftp with root?  If so, then I guess I need to
> set up another ID with full directory/file authority  "777 I think".
> When I ftp something to Linux, I want it to go where I want it to go.
> (too use to logging on as root).
>
> Tom Duerbusch
> THD Consulting
>
>
> If you're *running* sshd, then SSH into the box.  *DON'T* telnet and
> then su!  You're sending the root password over the wire in cleartext
> if
> you do that.  That's WHY you can't telnet in as root!
>
> Adam
>
>

Reply via email to