Re: SSH File Transfer Protocol - draft-moonesamy-secsh-filexfer-00
Joseph Galbriath <galb-list@vandyke.com> Mon, 22 July 2013 17:06 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 2120F21F96A8 for <ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com>; Mon, 22 Jul 2013 10:06:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1
X-Spam-Level:
X-Spam-Status: No, score=-1 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_LOW=-1]
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 LUMckpmUwZfd for <ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com>; Mon, 22 Jul 2013 10:06:05 -0700 (PDT)
Received: from mail.netbsd.org (mail.NetBSD.org [IPv6:2001:4f8:3:7::25]) by ietfa.amsl.com (Postfix) with ESMTP id C216B11E8129 for <secsh-tyoxbijeg7-archive@lists.ietf.org>; Mon, 22 Jul 2013 09:51:52 -0700 (PDT)
Received: by mail.netbsd.org (Postfix, from userid 605) id 799D414A226; Mon, 22 Jul 2013 16:40:31 +0000 (UTC)
Delivered-To: ietf-ssh@netbsd.org
Received: from localhost (localhost [127.0.0.1]) by mail.netbsd.org (Postfix) with ESMTP id 1845914A220 for <ietf-ssh@netbsd.org>; Mon, 22 Jul 2013 16:40:29 +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 3PFX7SQvBLTf for <ietf-ssh@netbsd.org>; Mon, 22 Jul 2013 16:40:28 +0000 (UTC)
Received: from vandyke.com (mail.vandyke.com [216.184.10.33]) by mail.netbsd.org (Postfix) with ESMTP id 5B34614A1D9 for <ietf-ssh@netbsd.org>; Mon, 22 Jul 2013 16:40:28 +0000 (UTC)
Received: from [192.168.1.62] (HELO cw01.nm.cotsware.com) by vandyke.com (CommuniGate Pro SMTP 5.4.4) with ESMTP id 13143312; Mon, 22 Jul 2013 09:38:53 -0600
Message-ID: <51ED5266.1080206@vandyke.com>
Date: Mon, 22 Jul 2013 09:40:22 -0600
From: Joseph Galbriath <galb-list@vandyke.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: "Mark D. Baushke" <mdb@juniper.net>
CC: ietf-ssh@NetBSD.org
Subject: Re: SSH File Transfer Protocol - draft-moonesamy-secsh-filexfer-00
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> <89500.1373729652@eng-mail01.juniper.net>
In-Reply-To: <89500.1373729652@eng-mail01.juniper.net>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Sender: ietf-ssh-owner@NetBSD.org
List-Id: ietf-ssh.NetBSD.org
Precedence: list
On 2013/07/13 9:34, Mark D. Baushke wrote: > [...] > This one lives here: > > http://tools.ietf.org/html/draft-galb-filexfer-extensions-00 > > last updated 2005-10-05. http://tools.ietf.org/id/draft-ietf-secsh-filexfer-extensions-00.txt is more up-to-date (if only slightly) and includes several additional extensions. (Published: January 18, 2006) > [...] > 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. The problem here is that OpenSSH implemented packet 20 backwards from the spec (swapped target and source file). Others implement the spec correctly. And because of backwards compatibility, no one wanted to change. So I dropped packet 20 as basically unimplementable and introduced SSH_FXP_LINK to replace it (and also supported hard links at the same time). > 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? Yes; we've implemented all three in our products. Thanks, Joseph
- 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