Re: SSH File Transfer Protocol - draft-moonesamy-secsh-filexfer-00
Mouse <mouse@Rodents-Montreal.ORG> Sat, 13 July 2013 12:56 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 EB6B021F9B4D for <ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com>; Sat, 13 Jul 2013 05:56:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.195
X-Spam-Level:
X-Spam-Status: No, score=-0.195 tagged_above=-999 required=5 tests=[AWL=1.793, BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611]
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 7gQTEspGhcCm for <ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com>; Sat, 13 Jul 2013 05:56:39 -0700 (PDT)
Received: from mail.netbsd.org (mail.NetBSD.org [IPv6:2001:4f8:3:7::25]) by ietfa.amsl.com (Postfix) with ESMTP id D004521F9B40 for <secsh-tyoxbijeg7-archive@lists.ietf.org>; Sat, 13 Jul 2013 05:56:39 -0700 (PDT)
Received: by mail.netbsd.org (Postfix, from userid 605) id 6483114A216; Sat, 13 Jul 2013 12:56:35 +0000 (UTC)
Delivered-To: ietf-ssh@NetBSD.org
Received: from localhost (localhost [127.0.0.1]) by mail.netbsd.org (Postfix) with ESMTP id C1CE014A214 for <ietf-ssh@NetBSD.org>; Sat, 13 Jul 2013 12:56:33 +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 P9iHdFI5XGGl for <ietf-ssh@NetBSD.org>; Sat, 13 Jul 2013 12:56:33 +0000 (UTC)
Received: from Chip.Rodents-Montreal.ORG (Chip.Rodents-Montreal.ORG [216.46.0.66]) by mail.netbsd.org (Postfix) with ESMTP id CF0FB14A20F for <ietf-ssh@NetBSD.org>; Sat, 13 Jul 2013 12:56:32 +0000 (UTC)
Received: (from mouse@localhost) by Chip.Rodents-Montreal.ORG (8.8.8/8.8.8) id IAA29783; Sat, 13 Jul 2013 08:56:27 -0400 (EDT)
Date: Sat, 13 Jul 2013 08:56:27 -0400
From: Mouse <mouse@Rodents-Montreal.ORG>
Message-Id: <201307131256.IAA29783@Chip.Rodents-Montreal.ORG>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Erik-Conspiracy: There is no Conspiracy - and if there were I wouldn't be part of it anyway.
X-Message-Flag: Microsoft: the company who gave us the botnet zombies.
X-Composition-Start-Date: Sat, 13 Jul 2013 08:44:45 -0400 (EDT)
To: ietf-ssh@NetBSD.org
Subject: Re: SSH File Transfer Protocol - draft-moonesamy-secsh-filexfer-00
In-Reply-To: <6.2.5.6.2.20130712030130.0beda980@elandnews.com>
References: <6.2.5.6.2.20130712030130.0beda980@elandnews.com>
Sender: ietf-ssh-owner@NetBSD.org
List-Id: ietf-ssh.NetBSD.org
Precedence: list
> The SSH File Transfer Protocol provides secure file transfer > functionality over any reliable data stream. Well...it, combined with the rest of ssh, does; sftp itself doesn't provide any significant level of security, depending on lower layers for that. But, really, it provides a lot more than file transfer; it's really a remote filesystem access protocol, misnamed as a file transfer protocol. If you really want a file transfer protocol, I'd suggest using a slight mutation of FTP (using ssh channels rather than TCP connections). But, apparently, people prefer a remote filesystem access protocol, even a misnamed one. My reaction upon looking at the draft is "what's the motivation?". That is, what does this draft offer beyond the existing spec? (Besides the version-number regression others have already pointed out.) If it really is just the things listed in appendix A, it strikes me as not worth the version-number confusion. /~\ The ASCII Mouse \ / Ribbon Campaign X Against HTML mouse@rodents-montreal.org / \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
- 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