Sat 16 Aug 2003 11:26:49 AM UTC, original submission:
Scott Parish <sRp@aspen.srparish.net> wrote:
> On Fri, Feb 07, 2003 at 06:45:36PM +0100, Karel Gardas wrote:
>
> > Ah, that's another problem! Sorry...
> >
> > BTW: AFAIK, when you type passwd in larch commands when using sftp
> > transport, then you type it directly into invoked ssh, so arch or arch's
> > transport doesn't know anything about typed passwd... IMHO it'll not be so
> > easy to do what you'd like to have, but anyway I'm not sftp transport
> > author...
>
> You nailed it, arch never sees your ssh password. It would be
> non-trivial to change this, and i certainly would not suggest it.
>
> SFTP is really quite a beautiful little protocol that is agnostic to
> security, or even transports. To impliment sftp, pipes are made, there
> is a fork, and ssh is execed with its stdin and stdout attached to one
> end of the pipe.
>
> sRp
>
> --
> Scott Parish
> http://srparish.net/
Robert Anderson <rwa@alumni.princeton.edu> wrote:
> On Fri, 2003-02-07 at 09:59, Robert Anderson wrote:
> > On Fri, 2003-02-07 at 09:45, Karel Gardas wrote:
> > > > Normally I do, too. It doesn't work in this case, because of the way
> > > > the ssh server is set up. It will not allow a promptless login, period.
> > >
> > > Ah, that's another problem! Sorry...
> > >
> > > BTW: AFAIK, when you type passwd in larch commands when using sftp
> > > transport,
> >
> > You think. :) From an absolutist standpoint, once you type the
> > characters on the keyboard all bets are off.
> >
> > In any case, yeah, storing passwords in arch is not a good idea.
> > Scratch it.
>
> I guess a saner request is to see if larch tag can do all of its work in
> one ftp "go" (whatever that means).
That is something I can agree with. I have the same reservations with
saving passwords that Karel has. I've forwarded this to the bug
tracker.
Walter
|