Re: SSH File Transfer Protocol - draft-moonesamy-secsh-filexfer-00
"Mark D. Baushke" <mdb@juniper.net> Sat, 13 July 2013 17:05 UTC
Return-Path: <bounces-ietf-ssh-owner-secsh-tyoxbijeg7-archive=lists.ietf.org@NetBSD.org>
X-Original-To: ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com
Delivered-To: ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F70421F9ED4 for <ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com>; Sat, 13 Jul 2013 10:05:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.299
X-Spam-Level:
X-Spam-Status: No, score=-0.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MANGLED_OFF=2.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aM2kiQfXwh+0 for <ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com>; Sat, 13 Jul 2013 10:05:06 -0700 (PDT)
Received: from mail.netbsd.org (mail.NetBSD.org [IPv6:2001:4f8:3:7::25]) by ietfa.amsl.com (Postfix) with ESMTP id 04F4E21F9ED3 for <secsh-tyoxbijeg7-archive@lists.ietf.org>; Sat, 13 Jul 2013 10:05:05 -0700 (PDT)
Received: by mail.netbsd.org (Postfix, from userid 605) id 9436A14A27E; Sat, 13 Jul 2013 17:05:01 +0000 (UTC)
Delivered-To: ietf-ssh@NetBSD.org
Received: from localhost (localhost [127.0.0.1]) by mail.netbsd.org (Postfix) with ESMTP id E969B14A191 for <ietf-ssh@NetBSD.org>; Sat, 13 Jul 2013 17:04:56 +0000 (UTC)
X-Virus-Scanned: amavisd-new at NetBSD.org
Received: from mail.netbsd.org ([127.0.0.1]) by localhost (mail.NetBSD.org [127.0.0.1]) (amavisd-new, port 10025) with ESMTP id eX4lR93VRWTk for <ietf-ssh@NetBSD.org>; Sat, 13 Jul 2013 17:04:56 +0000 (UTC)
Received: from db9outboundpool.messaging.microsoft.com (mail-db9lp0250.outbound.messaging.microsoft.com [213.199.154.250]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.netbsd.org (Postfix) with ESMTPS id 9000F14A16D for <ietf-ssh@NetBSD.org>; Sat, 13 Jul 2013 17:04:55 +0000 (UTC)
Received: from mail110-db9-R.bigfish.com (10.174.16.236) by DB9EHSOBE035.bigfish.com (10.174.14.98) with Microsoft SMTP Server id 14.1.225.22; Sat, 13 Jul 2013 15:34:28 +0000
Received: from mail110-db9 (localhost [127.0.0.1]) by mail110-db9-R.bigfish.com (Postfix) with ESMTP id 2374180836; Sat, 13 Jul 2013 15:34:28 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:66.129.224.51; KIP:(null); UIP:(null); IPV:NLI; H:P-EMHUB02-HQ.jnpr.net; RD:none; EFVD:NLI
X-SpamScore: -18
X-BigFish: VPS-18(z54eehz1432Izz1f42h1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6h1082kzz1033IL17326ah8275bh8275dhz2fh2a8h668h839hf0ah1288h12a5h12a9h12bdh12e5h137ah139eh13b6h1441h14ddh1504h1537h162dh1631h1758h1898h18e1h1946h19b5h1ad9h1b0ah1d0ch1d2eh1d3fh1de2h1dfeh1dffh1e23h1155h)
Received-SPF: pass (mail110-db9: domain of juniper.net designates 66.129.224.51 as permitted sender) client-ip=66.129.224.51; envelope-from=mdb@juniper.net; helo=P-EMHUB02-HQ.jnpr.net ; -HQ.jnpr.net ;
Received: from mail110-db9 (localhost.localdomain [127.0.0.1]) by mail110-db9 (MessageSwitch) id 1373729666362776_3540; Sat, 13 Jul 2013 15:34:26 +0000 (UTC)
Received: from DB9EHSMHS020.bigfish.com (unknown [10.174.16.234]) by mail110-db9.bigfish.com (Postfix) with ESMTP id 49D6F2E0046; Sat, 13 Jul 2013 15:34:26 +0000 (UTC)
Received: from P-EMHUB02-HQ.jnpr.net (66.129.224.51) by DB9EHSMHS020.bigfish.com (10.174.14.30) with Microsoft SMTP Server (TLS) id 14.16.227.3; Sat, 13 Jul 2013 15:34:26 +0000
Received: from magenta.juniper.net (172.17.27.123) by P-EMHUB02-HQ.jnpr.net (172.24.192.33) with Microsoft SMTP Server (TLS) id 8.3.213.0; Sat, 13 Jul 2013 08:34:24 -0700
Received: from eng-mail01.juniper.net (eng-mail01.juniper.net [172.17.28.114]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id r6DFYDL68473; Sat, 13 Jul 2013 08:34:13 -0700 (PDT) (envelope-from mdb@juniper.net)
Received: from eng-mail01.juniper.net (localhost [127.0.0.1]) by eng-mail01.juniper.net (Postfix) with ESMTP id 8F5CA1148A; Sat, 13 Jul 2013 08:34:12 -0700 (PDT)
To: Mouse <mouse@Rodents-Montreal.ORG>
CC: ietf-ssh@NetBSD.org
Subject: Re: SSH File Transfer Protocol - draft-moonesamy-secsh-filexfer-00
In-Reply-To: <201307131259.IAA02778@Chip.Rodents-Montreal.ORG>
References: <9A043F3CF02CD34C8E74AC1594475C734470C9DE@uxcn10-6.UoA.auckland.ac.nz> <6.2.5.6.2.20130712050150.0cd0f7e8@elandnews.com> <A433CD8982A340C09BFBF0E5D4911A71@Dragonborn> <201307131259.IAA02778@Chip.Rodents-Montreal.ORG>
Comments: In-Reply-To Mouse <mouse@Rodents-Montreal.ORG> message dated "Sat, 13 Jul 2013 08:59:06 -0400."
From: "Mark D. Baushke" <mdb@juniper.net>
X-Phone: +1 408 745-2952 (Office)
X-Mailer: MH-E 8.2; nmh 1.2; GNU Emacs 22.1.1
X-Face: #8D_6URD2G%vC.hzU<dI&#Y9szHj$'mGtUq&d=rXy^L$-=G_-LmZ^5!Fszk:yXZp$k\nTF? 8Up0!v/%1Q[(d?ES0mQW8dRCXi18gK)luJu)loHk, }4{Vi`yX?p?crF5o:LL{6#eiO:(E:YMxLXULB k|'a*EjN.B&L+[J!PhJ*aX0n:5/
Date: Sat, 13 Jul 2013 08:34:12 -0700
Message-ID: <89500.1373729652@eng-mail01.juniper.net>
MIME-Version: 1.0
Content-Type: text/plain
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Sender: ietf-ssh-owner@NetBSD.org
List-Id: ietf-ssh.NetBSD.org
Precedence: list
Mouse <mouse@Rodents-Montreal.ORG> writes: > > [...], as specified in: > > > draft-ietf-secsh-filexfer-13.txt This one lives here: http://tools.ietf.org/id/draft-ietf-secsh-filexfer-13.txt but a history of the changes may be found here: http://datatracker.ietf.org/doc/draft-ietf-secsh-filexfer/ last updated 2006-07-18. > > as well as extensions specified in: > > > draft-galb-filexfer-extensions-00.txt This one lives here: http://tools.ietf.org/html/draft-galb-filexfer-extensions-00 last updated 2005-10-05. > Where can one find those? ftp.ietf.org doesn't seem to have them; the > Moonesamy draft is the only one I get asking for *filexfer*. fwiw: Both drafts were authored by Joseph Galbraith of VanDyke Software and Oskari Saarenmaa of F-Secure. The draft-ietf-secsh-filexfer originally had co-authors Tatu Ylonen and Sami Lehtinen, but they dropped out around version 10 of the draft in June 2005. As near as I can figure, versions of the SFTP protocol are spread out over different iterations of the draft-ietf-secsh-filexfer document. Version 3 was enumerated first in the -02 draft. Version 2: Added SSH_FXP_RENAME Version 3: Added SSH_FXP_READLINK, SSH_FXP_SYMLINK SSH_FXP_EXTENDED, SSH_FXP_EXTENDED_REPLY, and SSH_FXP_STATUS Drafts -03 and -04 bumped the STFP version to 4 Draft -05 bumped the SFTP version to 5 Drafts -06 thru -13 all played with the SFTP version 6 Given that draft-ietf-secsh-filexfer-13.txt had the latest description of version 6 of the SFTP protocol and none of the drafts ever were published as an RFC, there is already a fair amount of confusion with regard to SFTP versions. I am actually in favor of some form of the draft-moonesamy-secsh-filexfer as an informational RFC to document the packet types being used by SFTP as a way of getting them put into the http://www.iana.org/assignments/ssh-paramters/ssh-parameters.xhtml document so that everyone who implements some fraction of them uses the same packet type definitions. If this means that the SFTP version needs to be at some other version than 3 or 4 or 6, then so be it. OpenSSH has said that it implements draft-ietf-secsh-filexfer-02.txt and provides a copy of it in http://www.openssh.com/txt/ What are the differences between draft-ietf-secsh-filexfer-13 and draft-moonesamy-secsh-filexfer-00 ? Well, packet 20 is not listed in the draft-ietf-secsh-filexfer-13, but is named SSH_FXP_SYMLINK in moonesamy. Also moonesamy does not define packets 21 (SSH_FXP_LINK, 22 (SSH_FXP_BLOCK), 23 (SSH_FXP_UNBLOCK). So, did anyone ever implement packet types 21, 22, and 23? If so, what SFTP version did you call it and what do they do? -- Mark
- SSH File Transfer Protocol - draft-moonesamy-secs… S Moonesamy
- Re: SSH File Transfer Protocol - draft-moonesamy-… Peter Gutmann
- Re: SSH File Transfer Protocol - draft-moonesamy-… S Moonesamy
- Re: SSH File Transfer Protocol - draft-moonesamy-… denis bider (Bitvise)
- Re: SSH File Transfer Protocol - draft-moonesamy-… Mouse
- Re: SSH File Transfer Protocol - draft-moonesamy-… Mouse
- Re: SSH File Transfer Protocol - draft-moonesamy-… Mark D. Baushke
- Re: SSH File Transfer Protocol - draft-moonesamy-… Peter Gutmann
- RE: SSH File Transfer Protocol - draft-moonesamy-… S Moonesamy
- Re: SSH File Transfer Protocol - draft-moonesamy-… S Moonesamy
- Re: SSH File Transfer Protocol - draft-moonesamy-… S Moonesamy
- RE: SSH File Transfer Protocol - draft-moonesamy-… Rich Whalen
- Re: SSH File Transfer Protocol - draft-moonesamy-… Albert Lunde
- Re: SSH File Transfer Protocol - draft-moonesamy-… Mark D. Baushke
- Re: SSH File Transfer Protocol - draft-moonesamy-… Jeffrey Hutzelman
- Re: SSH File Transfer Protocol - draft-moonesamy-… Damien Miller
- Re: SSH File Transfer Protocol - draft-moonesamy-… Joseph Galbriath
- Re: SSH File Transfer Protocol - draft-moonesamy-… Joseph Galbriath
- Re: SSH File Transfer Protocol - draft-moonesamy-… Joseph Galbriath
- Re: SSH File Transfer Protocol - draft-moonesamy-… Joseph Galbriath
- Re: SSH File Transfer Protocol - draft-moonesamy-… S Moonesamy
- Re: SSH File Transfer Protocol - draft-moonesamy-… Peter Gutmann
- Re: SSH File Transfer Protocol - draft-moonesamy-… Damien Miller
- Re: SSH File Transfer Protocol - draft-moonesamy-… Richard Kettlewell