Re: chmod sftp command and setgid/setuid bit

----- Original Message -----
From: "Darren Tucker" <dtucker@zip.com.au>
To: "Chris Rapier" <rapier@psc.edu>
Cc: <openssh-unix-dev@mindrot.org>
Sent: Thursday, April 26, 2007 5:32 PM
Subject: Re: chmod sftp command and setgid/setuid bit


> Chris Rapier wrote:
> > Darren Tucker wrote:
> >> It's filexfer draft 3. There's no RFC for sftp.
> >>
> >> http://tools.ietf.org/html/draft-ietf-secsh-filexfer-03
>
> Correction: that draft is sftp protocol version 4. Right now, according to
> "version" OpenSSH supports protocol version 3 which is filexfer-02.
>
>> I had been reading filexfer-13 - this one is much more straightforward.
>
> The other fun thing is that if a client reports that it implements filexfer-13, it
> must also handle 1-12 as well. During protocol initialization, the client tells
> the server what version it's using then the server replies with the lower of
> whatever it and the client support. After that they both must use whatever
> version the server selected.
>
> The upshot is that if the client claims to support v13, it must be prepared to
> process any lower version too; there's no way for the client to say "I support
> 1,2,3 or 13". (Within a single session, that is. In this example the client could
> potentially try 13 then abort if the server selects 4-12 and retry with 3 but
> that's kinda ugly.)

As I recall, there is only v1-v6. the version didn't get bumped for each
draft.

--Jeff

_______________________________________________
openssh-unix-dev mailing list
openssh-unix-dev@mindrot.org
http://lists.mindrot.org/mailman/lis...enssh-unix-dev