From bounces-ietf-ssh-owner-secsh-archive=odin.ietf.org@NetBSD.org Mon Jun 6 17:09:39 2005 Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18540 for ; Mon, 6 Jun 2005 17:09:38 -0400 (EDT) Received: by mail.netbsd.org (Postfix, from userid 0) id D89A83A503; Mon, 6 Jun 2005 21:09:30 +0000 (UTC) X-Original-To: ietf-ssh@netbsd.org Delivered-To: ietf-ssh@netbsd.org Received: from vandyke.com (mail.vandyke.com [204.134.9.1]) by mail.netbsd.org (Postfix) with ESMTP id 34E513A3A6 for ; Mon, 6 Jun 2005 21:09:29 +0000 (UTC) Received: from [127.0.0.1] (HELO [0.0.0.0]) by vandyke.com (CommuniGate Pro SMTP 3.4.7) with ESMTP id 7522427 for ietf-ssh@netbsd.org; Mon, 06 Jun 2005 15:09:27 -0600 Message-ID: <42A4BC73.1080600@vandyke.com> Date: Mon, 06 Jun 2005 15:13:23 -0600 From: Joseph Galbraith User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "ietf-ssh@netbsd.org" Subject: Sftp v6... Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: ietf-ssh-owner@NetBSD.org Precedence: list Content-Transfer-Encoding: 7bit Is anyone shipping SFTP v6 yet? I've realized we have the following bugs in the specification: + I removed the valid access mask from the "supported2" extension because when opening a file, masking off unsupported access just results in requesting no access-- so the server has to responisble for doing the mapping. However, we still need this information for setting ACLs. + We need a way to differentiate between systems that don't support ACLs, a file w/o an ACL (all access) and a file with an empty ACL (no access) So if we don't have any one shipping yet, I'll definitely slip the first one into a quick fix. I'm still thinking about the correct fix for the second one, but I think I can get it out pretty quick to. If we do having shipping code, I'll have to go for plan b. Thanks, Joseph From bounces-ietf-ssh-owner-secsh-archive=odin.ietf.org@NetBSD.org Tue Jun 7 03:38:27 2005 Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA24699 for ; Tue, 7 Jun 2005 03:38:24 -0400 (EDT) Received: by mail.netbsd.org (Postfix, from userid 0) id 509553A4E2; Tue, 7 Jun 2005 07:38:17 +0000 (UTC) X-Original-To: ietf-ssh@netbsd.org Delivered-To: ietf-ssh@netbsd.org Received: from Sparkle.Rodents.Montreal.QC.CA (Sparkle.Rodents.Montreal.QC.CA [216.46.5.7]) by mail.netbsd.org (Postfix) with ESMTP id 9AED43A4DB for ; Tue, 7 Jun 2005 07:38:14 +0000 (UTC) Received: (from mouse@localhost) by Sparkle.Rodents.Montreal.QC.CA (8.8.8/8.8.8) id DAA05194; Tue, 7 Jun 2005 03:38:13 -0400 (EDT) From: der Mouse Message-Id: <200506070738.DAA05194@Sparkle.Rodents.Montreal.QC.CA> 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 zombie armies. Date: Tue, 7 Jun 2005 03:30:28 -0400 (EDT) To: ietf-ssh@NetBSD.org Subject: OPEN_FAILURE reason codes Sender: ietf-ssh-owner@NetBSD.org Precedence: list Content-Transfer-Encoding: 8bit I'm working on my ssh implementation (big surprise) and have run into a problem (even bigger surprise). Specifically, I'm working on connection sharing. In the circumstance where the server has sent a CHANNEL_OPEN (eg, for a forwarded TCP connection) and we've sent it on to the client, but our own connection to the client drops before we get either success or failure back, I more or less have to synthesize a failure to send back to the server. But the problem is, what reason code should I use? Only four are defined SSH_OPEN_ADMINISTRATIVELY_PROHIBITED SSH_OPEN_CONNECT_FAILED SSH_OPEN_UNKNOWN_CHANNEL_TYPE SSH_OPEN_RESOURCE_SHORTAGE and none of them really fit. CONNECT_FAILED is perhaps the closest, but gives the wrong impression, especially for forwarded TCP connections. What do you people think is best? Should I just use CONNECT_FAILED, or should I use one of the 0xf[ef]* codes and put something explanatory in the reason string, or campaign to get a new reason code assigned from the standardized space, or what? I can see arguments for each, and am interested in any thoughts any of you may have on the matter. /~\ The ASCII der Mouse \ / Ribbon Campaign X Against HTML mouse@rodents.montreal.qc.ca / \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B From bounces-ietf-ssh-owner-secsh-archive=odin.ietf.org@NetBSD.org Tue Jun 7 12:53:52 2005 Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10588 for ; Tue, 7 Jun 2005 12:53:51 -0400 (EDT) Received: by mail.netbsd.org (Postfix, from userid 0) id C99033A39B; Tue, 7 Jun 2005 16:53:44 +0000 (UTC) X-Original-To: ietf-ssh@netbsd.org Delivered-To: ietf-ssh@netbsd.org Received: from hosting.revelstone.com (sls-ce10p21.dca2.superb.net [66.36.242.103]) by mail.netbsd.org (Postfix) with ESMTP id 043D53A46A for ; Tue, 7 Jun 2005 16:53:42 +0000 (UTC) Received: from localhost ([127.0.0.1] helo=aud) by hosting.revelstone.com with smtp (Exim 4.50) id 1DfhKf-00076C-6k for ietf-ssh@netbsd.org; Tue, 07 Jun 2005 12:53:41 -0400 Date: Tue, 7 Jun 2005 12:53:40 -0400 From: Robert Story To: ietf-ssh@NetBSD.org Subject: archive? Message-ID: <20050607125340.46b852ea@aud> X-Mailer: Sylpheed-Claws 0.9.12b (GTK+ 1.2.10; powerpc-unknown-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - hosting.revelstone.com X-AntiAbuse: Original Domain - netbsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - 2005.revelstone.com Sender: ietf-ssh-owner@NetBSD.org Precedence: list Content-Transfer-Encoding: 7bit The archive for this list on the ietf server seems to stop on 4/14. I thought maybe the list had been silent since then, but I've gotten two messages on the list today and the date on the 'current' file hasn't changed. Is there another archive somewhere? From bounces-ietf-ssh-owner-secsh-archive=odin.ietf.org@NetBSD.org Tue Jun 7 16:25:53 2005 Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07467 for ; Tue, 7 Jun 2005 16:25:52 -0400 (EDT) Received: by mail.netbsd.org (Postfix, from userid 0) id 32E1E3A44F; Tue, 7 Jun 2005 20:25:44 +0000 (UTC) X-Original-To: ietf-ssh@netbsd.org Delivered-To: ietf-ssh@netbsd.org Received: from mail.lysator.liu.se (mail.lysator.liu.se [130.236.254.3]) by mail.netbsd.org (Postfix) with ESMTP id EFD443A3F0 for ; Tue, 7 Jun 2005 20:25:41 +0000 (UTC) Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.lysator.liu.se (Postfix) with ESMTP id EAE5B1B8011; Tue, 7 Jun 2005 22:04:10 +0200 (CEST) Received: from mail.lysator.liu.se ([127.0.0.1]) by localhost (lenin [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 25363-01-10; Tue, 7 Jun 2005 22:04:10 +0200 (CEST) Received: from adriana.lysator.liu.se (adriana.lysator.liu.se [130.236.254.28]) by mail.lysator.liu.se (Postfix) with ESMTP id 6631D1B8002; Tue, 7 Jun 2005 22:04:10 +0200 (CEST) Received: (from nisse@localhost) by adriana.lysator.liu.se (8.12.10/8.12.8) id j57K44vZ007954; Tue, 7 Jun 2005 22:04:04 +0200 (MEST) X-Authentication-Warning: adriana.lysator.liu.se: nisse set sender to nisse@lysator.liu.se using -f To: der Mouse Cc: ietf-ssh@NetBSD.org Subject: Re: OPEN_FAILURE reason codes References: <200506070738.DAA05194@Sparkle.Rodents.Montreal.QC.CA> Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 8bit From: nisse@lysator.liu.se (Niels =?iso-8859-1?q?M=F6ller?=) Date: 07 Jun 2005 22:04:04 +0200 In-Reply-To: <200506070738.DAA05194@Sparkle.Rodents.Montreal.QC.CA> Message-ID: Lines: 26 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at lysator.liu.se Sender: ietf-ssh-owner@NetBSD.org Precedence: list Content-Transfer-Encoding: 8bit der Mouse writes: > But the problem is, what reason code should I use? Only four are > defined > > SSH_OPEN_ADMINISTRATIVELY_PROHIBITED > SSH_OPEN_CONNECT_FAILED > SSH_OPEN_UNKNOWN_CHANNEL_TYPE > SSH_OPEN_RESOURCE_SHORTAGE > > and none of them really fit. CONNECT_FAILED is perhaps the closest, > but gives the wrong impression, especially for forwarded TCP > connections. I'd say use CONNECT_FAILED, and put some reasonable message in the explanation string. Feel free to propose additional standard error codes (perhaps we should have a kitchen sink code for failures not matching any other?), but I don't think these numeric codes are terribly important. In your scenario, no matter which code you use, the only reasonable action on the server's side is to close the connection it tried to forward, with no error message of any kind propagated. Regards, /Niels From bounces-ietf-ssh-owner-secsh-archive=odin.ietf.org@NetBSD.org Tue Jun 7 17:39:15 2005 Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15889 for ; Tue, 7 Jun 2005 17:39:15 -0400 (EDT) Received: by mail.netbsd.org (Postfix, from userid 0) id 3C2F73A3FC; Tue, 7 Jun 2005 21:39:13 +0000 (UTC) X-Original-To: ietf-ssh@netbsd.org Delivered-To: ietf-ssh@netbsd.org Received: from chiark.greenend.org.uk (chiark.greenend.org.uk [193.201.200.170]) by mail.netbsd.org (Postfix) with ESMTP id A7EA23A398 for ; Tue, 7 Jun 2005 21:39:11 +0000 (UTC) Received: by chiark.greenend.org.uk (Debian Exim 3.35 #1) with local (return-path bjharris@chiark.greenend.org.uk) id 1Dflmw-00049T-00; Tue, 07 Jun 2005 22:39:10 +0100 From: Ben Harris To: rstory-l@2005.revelstone.com, ietf-ssh@NetBSD.org Subject: Re: archive? In-Reply-To: <20050607125340.46b852ea@aud> References: <20050607125340.46b852ea@aud> Organization: Linux Unlimited Message-Id: Date: Tue, 07 Jun 2005 22:39:10 +0100 Sender: ietf-ssh-owner@NetBSD.org Precedence: list In article <20050607125340.46b852ea@aud> you write: >The archive for this list on the ietf server seems to stop on 4/14. I thought >maybe the list had been silent since then, but I've gotten two messages on the >list today and the date on the 'current' file hasn't changed. Is there another >archive somewhere? Theres one on mail.netbsd.org, but it's not publicly accessible, so it's only likely to be useful to fill in the gaps once the IETF archive is revived. -- Ben Harris From bounces-ietf-ssh-owner-secsh-archive=odin.ietf.org@NetBSD.org Wed Jun 8 03:26:03 2005 Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02545 for ; Wed, 8 Jun 2005 03:26:03 -0400 (EDT) Received: by mail.netbsd.org (Postfix, from userid 0) id 984693A549; Wed, 8 Jun 2005 07:25:59 +0000 (UTC) X-Original-To: ietf-ssh@netbsd.org Delivered-To: ietf-ssh@netbsd.org Received: from Sparkle.Rodents.Montreal.QC.CA (Sparkle.Rodents.Montreal.QC.CA [216.46.5.7]) by mail.netbsd.org (Postfix) with ESMTP id 9439E3A4C1 for ; Wed, 8 Jun 2005 07:25:57 +0000 (UTC) Received: (from mouse@localhost) by Sparkle.Rodents.Montreal.QC.CA (8.8.8/8.8.8) id DAA22837; Wed, 8 Jun 2005 03:25:52 -0400 (EDT) From: der Mouse Message-Id: <200506080725.DAA22837@Sparkle.Rodents.Montreal.QC.CA> 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 zombie armies. Date: Wed, 8 Jun 2005 03:20:03 -0400 (EDT) To: ietf-ssh@NetBSD.org Subject: FORWARDING_NOTICE: IP-specific Sender: ietf-ssh-owner@NetBSD.org Precedence: list Content-Transfer-Encoding: 8bit I notice that the FORWARDING_NOTICE agent message (see agent-01) is inextricably entangled with the assumption that ssh is running over IP. What is the thinking on what will happen to it when someone implements what we're doing over something else, like (say) DECnet? While (as mentioned when I brought up the same issue with connection forwarding) we cannot be expected to standardize hwo to handle arbitrary underlying protocols, it does seem rather short-sighted to me to build a protocol that is unnecessarily difficult to extend. With connection forwarding the issue could be finessed by noting that the connection forwarding request is implicitly IP-specific; connection forwarding for some other protocol would use other request and channel type strings. But there is nothing similar available for agent FORWARDING_NOTICE messages, as far as I can see. Thoughts? /~\ The ASCII der Mouse \ / Ribbon Campaign X Against HTML mouse@rodents.montreal.qc.ca / \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B From bounces-ietf-ssh-owner-secsh-archive=odin.ietf.org@NetBSD.org Wed Jun 8 13:00:53 2005 Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17230 for ; Wed, 8 Jun 2005 13:00:53 -0400 (EDT) Received: by mail.netbsd.org (Postfix, from userid 0) id 8B3913A5E3; Wed, 8 Jun 2005 17:00:47 +0000 (UTC) X-Original-To: ietf-ssh@NetBSD.org Delivered-To: ietf-ssh@NetBSD.org Received: from minbar.fac.cs.cmu.edu (MINBAR.FAC.CS.CMU.EDU [128.2.185.161]) by mail.netbsd.org (Postfix) with SMTP id 2E8D53A56E for ; Wed, 8 Jun 2005 17:00:45 +0000 (UTC) Received: from SIRIUS.FAC.CS.CMU.EDU ([128.2.209.170]) by minbar.fac.cs.cmu.edu id aa07621; 8 Jun 2005 13:00 EDT Date: Wed, 08 Jun 2005 13:00:18 -0400 From: Jeffrey Hutzelman To: der Mouse , ietf-ssh@NetBSD.org Subject: Re: FORWARDING_NOTICE: IP-specific Message-ID: In-Reply-To: <200506080725.DAA22837@Sparkle.Rodents.Montreal.QC.CA> References: <200506080725.DAA22837@Sparkle.Rodents.Montreal.QC.CA> Originator-Info: login-token=Mulberry:01WwsaJ8Vzj5unVpKojolKlvJ9UVLiP5PIgEiMkYs=; token_authority=postmaster@andrew.cmu.edu X-Mailer: Mulberry/3.1.6 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: ietf-ssh-owner@NetBSD.org Precedence: list Content-Transfer-Encoding: 7bit On Wednesday, June 08, 2005 03:20:03 AM -0400 der Mouse wrote: > I notice that the FORWARDING_NOTICE agent message (see agent-01) is > inextricably entangled with the assumption that ssh is running over IP. > What is the thinking on what will happen to it when someone implements > what we're doing over something else, like (say) DECnet? While (as > mentioned when I brought up the same issue with connection forwarding) > we cannot be expected to standardize hwo to handle arbitrary underlying > protocols, it does seem rather short-sighted to me to build a protocol > that is unnecessarily difficult to extend. With connection forwarding > the issue could be finessed by noting that the connection forwarding > request is implicitly IP-specific; connection forwarding for some other > protocol would use other request and channel type strings. But there > is nothing similar available for agent FORWARDING_NOTICE messages, as > far as I can see. > > Thoughts? First of all, the most recent agent draft appears to be -02, which was published over a year ago. It's unfortunate that there doesn't seem to have been any more recent work on this; I'd very much like to see an extensible, interoperable agent protocol. Second, it looks like it actually needs a fair bit of work before it will really be ready. In addition to the problem you point out, there's also another issue with forwarding. The normal case is that an SSH server receives an agent connection on a UNIX-domain socket, forwards over a channel to an SSH client, which establishes a UNIX-domain connection to an agent (or another SSH server). Now, who is supposed to insert the forwarding notice? The ssh server? The ssh client? Both? This does not appear to be well-specified. There's also a significant problem with the extension mechanism. According to section 1.1, SSH_AGENT_EXTENSION is packet type 301. The problem is, that value doesn't fit in a byte! I understand the motiviation for representing packet types in a single byte and for avoiding the first 30 or so message numbers. But can we allocate the rest of the space more intelligently? -- Jeff From bounces-ietf-ssh-owner-secsh-archive=odin.ietf.org@NetBSD.org Wed Jun 8 13:30:42 2005 Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19257 for ; Wed, 8 Jun 2005 13:30:42 -0400 (EDT) Received: by mail.netbsd.org (Postfix, from userid 0) id 3617C3A56E; Wed, 8 Jun 2005 17:30:40 +0000 (UTC) X-Original-To: ietf-ssh@NetBSD.org Delivered-To: ietf-ssh@NetBSD.org Received: from Sparkle.Rodents.Montreal.QC.CA (Sparkle.Rodents.Montreal.QC.CA [216.46.5.7]) by mail.netbsd.org (Postfix) with ESMTP id 1DC0D3A5FF for ; Wed, 8 Jun 2005 17:30:36 +0000 (UTC) Received: (from mouse@localhost) by Sparkle.Rodents.Montreal.QC.CA (8.8.8/8.8.8) id NAA27275; Wed, 8 Jun 2005 13:30:36 -0400 (EDT) From: der Mouse Message-Id: <200506081730.NAA27275@Sparkle.Rodents.Montreal.QC.CA> 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 zombie armies. Date: Wed, 8 Jun 2005 13:26:36 -0400 (EDT) To: ietf-ssh@NetBSD.org Subject: Re: FORWARDING_NOTICE: IP-specific In-Reply-To: References: <200506080725.DAA22837@Sparkle.Rodents.Montreal.QC.CA> Sender: ietf-ssh-owner@NetBSD.org Precedence: list Content-Transfer-Encoding: 8bit > First of all, the most recent agent draft appears to be -02, which > was published over a year ago. It's unfortunate that there doesn't > seem to have been any more recent work on this; I'd very much like to > see an extensible, interoperable agent protocol. Well, you could always adopt it, since Ylonen/Rinne/Lehtinen seem to have abandoned it. :-) > Second, it looks like it actually needs a fair bit of work before it > will really be ready. In addition to the problem you point out, > there's also another issue with forwarding. The normal case is that > [...]. Now, who is supposed to insert the forwarding notice? The > ssh server? The ssh client? Both? This does not appear to be > well-specified. | 1.2. Forwarding Notices | | If the agent connection is forwarded through intermediate hosts (using | the SSH Connection Protocol agent forwarding feature (described in | Section ``Agent Forwarding With Secure Shell'' of this document), or | some other means), each intermediate node (Secure Shell client) should | insert the following message into the agent channel before forwarding | any other messages. Note that "(Secure Shell client)" parenthesis. > There's also a significant problem with the extension mechanism. > According to section 1.1, SSH_AGENT_EXTENSION is packet type 301. !! That provision is obviously dead in the water, yes. :-) /~\ The ASCII der Mouse \ / Ribbon Campaign X Against HTML mouse@rodents.montreal.qc.ca / \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B From bounces-ietf-ssh-owner-secsh-archive=odin.ietf.org@NetBSD.org Wed Jun 8 13:49:46 2005 Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20910 for ; Wed, 8 Jun 2005 13:49:44 -0400 (EDT) Received: by mail.netbsd.org (Postfix, from userid 0) id 2A1DF3A5FA; Wed, 8 Jun 2005 17:49:41 +0000 (UTC) X-Original-To: ietf-ssh@NetBSD.org Delivered-To: ietf-ssh@NetBSD.org Received: from minbar.fac.cs.cmu.edu (MINBAR.FAC.CS.CMU.EDU [128.2.185.161]) by mail.netbsd.org (Postfix) with SMTP id 367023A4A1 for ; Wed, 8 Jun 2005 17:49:39 +0000 (UTC) Received: from SIRIUS.FAC.CS.CMU.EDU ([128.2.209.170]) by minbar.fac.cs.cmu.edu id aa07653; 8 Jun 2005 13:49 EDT Date: Wed, 08 Jun 2005 13:48:58 -0400 From: Jeffrey Hutzelman To: der Mouse , ietf-ssh@NetBSD.org Subject: Re: FORWARDING_NOTICE: IP-specific Message-ID: <90A9BDFD5133387170ADFF82@sirius.fac.cs.cmu.edu> In-Reply-To: <200506081730.NAA27275@Sparkle.Rodents.Montreal.QC.CA> References: <200506080725.DAA22837@Sparkle.Rodents.Montreal.QC.CA> <200506081730.NAA27275@Sparkle.Rodents.Montreal.QC.CA> Originator-Info: login-token=Mulberry:01ROgyNK5Qp6iQM6q1d2Zio9taaV/LHKuxXWCZemg=; token_authority=postmaster@andrew.cmu.edu X-Mailer: Mulberry/3.1.6 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: ietf-ssh-owner@NetBSD.org Precedence: list Content-Transfer-Encoding: 7bit On Wednesday, June 08, 2005 01:26:36 PM -0400 der Mouse wrote: >> Second, it looks like it actually needs a fair bit of work before it >> will really be ready. In addition to the problem you point out, >> there's also another issue with forwarding. The normal case is that >> [...]. Now, who is supposed to insert the forwarding notice? The >> ssh server? The ssh client? Both? This does not appear to be >> well-specified. > >| 1.2. Forwarding Notices >| >| If the agent connection is forwarded through intermediate hosts (using >| the SSH Connection Protocol agent forwarding feature (described in >| Section ``Agent Forwarding With Secure Shell'' of this document), or >| some other means), each intermediate node (Secure Shell client) should >| insert the following message into the agent channel before forwarding >| any other messages. > > Note that "(Secure Shell client)" parenthesis. Hm. I wonder how I missed that. From bounces-ietf-ssh-owner-secsh-archive=odin.ietf.org@NetBSD.org Thu Jun 9 06:30:46 2005 Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11061 for ; Thu, 9 Jun 2005 06:30:46 -0400 (EDT) Received: by mail.netbsd.org (Postfix, from userid 0) id 0F9B73A3F9; Thu, 9 Jun 2005 10:30:40 +0000 (UTC) X-Original-To: ietf-ssh@netbsd.org Delivered-To: ietf-ssh@netbsd.org Received: from chiark.greenend.org.uk (chiark.greenend.org.uk [193.201.200.170]) by mail.netbsd.org (Postfix) with ESMTP id 6A5FB3A3DE for ; Thu, 9 Jun 2005 10:30:38 +0000 (UTC) Received: by chiark.greenend.org.uk (Debian Exim 3.35 #1) with local (return-path jacobn@chiark.greenend.org.uk) id 1DgKJ3-0003u9-00; Thu, 09 Jun 2005 11:30:37 +0100 Date: Thu, 9 Jun 2005 11:30:37 +0100 From: Jacob Nevins To: ietf-action@ietf.org Cc: ietf-ssh@NetBSD.org Subject: IETF mailing list archive for SECSH WG not being updated Message-ID: <20050609103037.GA8907@chiark.greenend.org.uk> Reply-To: ietf-ssh@NetBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.28i Sender: ietf-ssh-owner@NetBSD.org Precedence: list [ Apologies if you've already heard about this, or if I'm the wrong person to have told you; I hadn't seen any evidence of action on the WG mailing list. ] The IETF archive for the SECSH working group mailing list at does not appear to have been updated since April 14. There has been list traffic since then. A WG member has said that NetBSD have an archive which can probably be used to fill in any gaps, if necessary. From bounces-ietf-ssh-owner-secsh-archive=odin.ietf.org@NetBSD.org Thu Jun 9 08:35:30 2005 Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA22464 for ; Thu, 9 Jun 2005 08:35:30 -0400 (EDT) Received: by mail.netbsd.org (Postfix, from userid 0) id B78053A3CD; Thu, 9 Jun 2005 12:35:23 +0000 (UTC) X-Original-To: ietf-ssh@netbsd.org Delivered-To: ietf-ssh@netbsd.org Received: from ticket.ietf.org (unknown [132.151.6.18]) by mail.netbsd.org (Postfix) with ESMTP id C06943A43E for ; Thu, 9 Jun 2005 12:35:19 +0000 (UTC) Received: from apache by ticket.ietf.org with local (Exim 4.33) id 1DgLHv-00031Q-R1 for ietf-ssh@netbsd.org; Thu, 09 Jun 2005 07:33:31 -0400 Subject: Re: [Inquiry #66622] IETF mailing list archive for SECSH WG not being updated From: "Scott Blomquist via RT" Reply-To: ietf-action@ietf.org In-Reply-To: Message-ID: X-RT-Loop-Prevention: Inquiry RT-Ticket: Inquiry #66622 Managed-by: RT 3.2.1 (http://www.bestpractical.com/rt/) RT-Originator: ietf-admin@techsquare.com To: ietf-ssh@NetBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" X-RT-Original-Encoding: utf-8 Date: Thu, 09 Jun 2005 07:33:31 -0400 Sender: ietf-ssh-owner@NetBSD.org Precedence: list Thanks. I will migrate this list over to the new mailling list archive asap (the archive is ok just not getting rsync'd to ftp). sb. Scott Blomquist for ietf-admin@techsquare.com From: "ietf-ssh@netbsd.org via RT" Date: Thu, 09 Jun 2005 06:33:06 -0400 Thu Jun 09 06:33:05 2005: Request 66622 was acted upon. Transaction: Ticket created by ietf-ssh@netbsd.org Queue: IETF-TechSupport Subject: IETF mailing list archive for SECSH WG not being updated Owner: Nobody Requestors: ietf-ssh@netbsd.org Status: new Ticket [ Apologies if you've already heard about this, or if I'm the wrong person to have told you; I hadn't seen any evidence of action on the WG mailing list. ] The IETF archive for the SECSH working group mailing list at does not appear to have been updated since April 14. There has been list traffic since then. A WG member has said that NetBSD have an archive which can probably be used to fill in any gaps, if necessary. From bounces-ietf-ssh-owner-secsh-archive=odin.ietf.org@NetBSD.org Mon Jun 13 12:42:56 2005 Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28714 for ; Mon, 13 Jun 2005 12:42:55 -0400 (EDT) Received: by mail.netbsd.org (Postfix, from userid 0) id B74B73A7EF; Mon, 13 Jun 2005 16:42:50 +0000 (UTC) X-Original-To: ietf-ssh@netbsd.org Delivered-To: ietf-ssh@netbsd.org Received: from s11.myhostcenter.com (s11.myhostcenter.com [72.36.156.13]) by mail.netbsd.org (Postfix) with ESMTP id EB52B3A3E1 for ; Mon, 13 Jun 2005 16:42:47 +0000 (UTC) Received: from nobody by s11.myhostcenter.com with local (Exim 4.44) id 1Dhod3-0007jC-JO for ietf-ssh@netbsd.org; Mon, 13 Jun 2005 06:05:25 -0700 To: ietf-ssh@NetBSD.org Subject: Re:Autoroll Fix Members Update Now From: MIME-Version: 1.0 X-Mailer: PHPBulkEmailer 1.1 http://www.nukedweb.com/ Content-Type: text/plain Content-Transfer-Encoding: 8bit Message-Id: Date: Mon, 13 Jun 2005 06:05:25 -0700 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - s11.myhostcenter.com X-AntiAbuse: Original Domain - netbsd.org X-AntiAbuse: Originator/Caller UID/GID - [99 99] / [47 12] X-AntiAbuse: Sender Address Domain - s11.myhostcenter.com Sender: ietf-ssh-owner@NetBSD.org Precedence: list Content-Transfer-Encoding: 8bit Attn Satellite tv tester,http://www.nagra2ready.com It is very urgent that you change your keys on your cards and fta units. The current keys are as follows. KEY0 02 7E A9 9B E5 07 A0 EA Active KEY1 D5 66 C4 72 AE D0 60 B7 It is also very important to note that if you are using an fta that you flash it with the latest version 4.2 of our nagra2ready bin. We provide support for all brands of fta units. Login now to update your receiver with the ecm-proof bin that we have compiled. http://www.nagra2ready.com If you are using rom cards or other card based fixes, it is important that you are protected from the ecm slated in the stream within the next 24 hours. This rare type of damaging ecm will bypass all current blockers and will cause permanant dammage to your hardware. Update your equipment now, do not wait for the worst to happen. We only have 72 slots open for new members, so if you fail to join in time, we will lock down the members section to new members. We do this to preserve the integrity of our ultra-private scripts and keep the code secure on a limited platform. http://www.nagra2ready.com From bounces-ietf-ssh-owner-secsh-archive=odin.ietf.org@NetBSD.org Mon Jun 13 13:41:36 2005 Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02831 for ; Mon, 13 Jun 2005 13:41:35 -0400 (EDT) Received: by mail.netbsd.org (Postfix, from userid 0) id BF6493A5E7; Mon, 13 Jun 2005 17:41:30 +0000 (UTC) X-Original-To: ietf-ssh@netbsd.org Delivered-To: ietf-ssh@netbsd.org Received: from nwkea-mail-2.sun.com (nwkea-mail-2.sun.com [192.18.42.14]) by mail.netbsd.org (Postfix) with ESMTP id 28F403A56E for ; Mon, 13 Jun 2005 17:41:29 +0000 (UTC) Received: from eastmail1bur.East.Sun.COM ([129.148.9.49]) by nwkea-mail-2.sun.com (8.12.10/8.12.9) with ESMTP id j5DHfSFF015282 for ; Mon, 13 Jun 2005 10:41:28 -0700 (PDT) Received: from thunk.east.sun.com (thunk.East.Sun.COM [129.148.174.66]) by eastmail1bur.East.Sun.COM (8.12.10+Sun/8.12.10/ENSMAIL,v2.2) with ESMTP id j5DHfSFt016772; Mon, 13 Jun 2005 13:41:28 -0400 (EDT) Received: from 127.0.0.1 (localhost [127.0.0.1]) by thunk.east.sun.com (8.13.3+Sun/8.13.3) with ESMTP id j5DHfRhP026527; Mon, 13 Jun 2005 13:41:27 -0400 (EDT) Subject: IANA protocol registry for secure shell protocol parameters now exists. From: Bill Sommerfeld To: ietf-ssh@NetBSD.org Content-Type: text/plain; charset=ISO-8859-1 Message-Id: <1118684487.26495.3.camel@thunk> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6.309 Date: Mon, 13 Jun 2005 13:41:27 -0400 Content-Transfer-Encoding: 7bit Sender: ietf-ssh-owner@NetBSD.org Precedence: list Content-Transfer-Encoding: 7bit FYI, the IANA registry for Secure Shell protocol parameters has been created: http://www.iana.org/assignments/ssh-parameters - Bill From bounces-ietf-ssh-owner-secsh-archive=odin.ietf.org@NetBSD.org Mon Jun 13 15:43:27 2005 Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16810 for ; Mon, 13 Jun 2005 15:43:27 -0400 (EDT) Received: by mail.netbsd.org (Postfix, from userid 0) id 98B253A4F1; Mon, 13 Jun 2005 19:43:19 +0000 (UTC) X-Original-To: ietf-ssh@netbsd.org Delivered-To: ietf-ssh@netbsd.org Received: from ietf.org (odin.ietf.org [132.151.1.176]) by mail.netbsd.org (Postfix) with ESMTP id 671BB3A4A5 for ; Mon, 13 Jun 2005 19:43:16 +0000 (UTC) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16736; Mon, 13 Jun 2005 15:43:14 -0400 (EDT) Message-Id: <200506131943.PAA16736@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: i-d-announce@ietf.org Cc: ietf-ssh@NetBSD.org From: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-secsh-filexfer-09.txt Date: Mon, 13 Jun 2005 15:43:14 -0400 Sender: ietf-ssh-owner@NetBSD.org Precedence: list --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Secure Shell Working Group of the IETF. Title : SSH File Transfer Protocol Author(s) : J. Galbraith, et al. Filename : draft-ietf-secsh-filexfer-09.txt Pages : 65 Date : 2005-6-13 The SSH File Transfer Protocol provides secure file transfer functionality over any reliable data stream. It is the standard file transfer protocol for use with the SSH2 protocol. This document describes the file transfer protocol and its interface to the SSH2 protocol suite. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-secsh-filexfer-09.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-secsh-filexfer-09.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-secsh-filexfer-09.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2005-6-13160901.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-secsh-filexfer-09.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-secsh-filexfer-09.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-6-13160901.I-D@ietf.org> --OtherAccess-- --NextPart-- From bounces-ietf-ssh-owner-secsh-archive=odin.ietf.org@NetBSD.org Mon Jun 13 16:13:00 2005 Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00610 for ; Mon, 13 Jun 2005 16:13:00 -0400 (EDT) Received: by mail.netbsd.org (Postfix, from userid 0) id B1FD33A5AA; Mon, 13 Jun 2005 20:12:01 +0000 (UTC) X-Original-To: ietf-ssh@NetBSD.org Delivered-To: ietf-ssh@NetBSD.org Received: from Sparkle.Rodents.Montreal.QC.CA (Sparkle.Rodents.Montreal.QC.CA [216.46.5.7]) by mail.netbsd.org (Postfix) with ESMTP id 185383A5E3 for ; Mon, 13 Jun 2005 20:11:54 +0000 (UTC) Received: (from mouse@localhost) by Sparkle.Rodents.Montreal.QC.CA (8.8.8/8.8.8) id QAA29683; Mon, 13 Jun 2005 16:11:53 -0400 (EDT) From: der Mouse Message-Id: <200506132011.QAA29683@Sparkle.Rodents.Montreal.QC.CA> 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 zombie armies. Date: Mon, 13 Jun 2005 15:49:25 -0400 (EDT) To: ietf-ssh@NetBSD.org Subject: filexfer-09.txt In-Reply-To: <200506131943.PAA16736@ietf.org> References: <200506131943.PAA16736@ietf.org> Sender: ietf-ssh-owner@NetBSD.org Precedence: list Content-Transfer-Encoding: 8bit > A New Internet-Draft is available [...] > Filename : draft-ietf-secsh-filexfer-09.txt Most of these are copy-edit suggestions, but there's one semantic question. from the server to the client the client MUST not used unless the protocol version is changed or the client has negotiated to received s/received/receive/. I'd suggest s/MUST not/MUST NOT/, too. Note that some server MAY return SSH_FX_OP_UNSUPPORTED if the (line 2256). I'd s/server/&s/ here, or perhaps s/some/the/ instead. SSH_FXP_UNBLOCK removes a previously aquired byte-range lock on the (line 2270). s/aqu/acqu/ In the description of SSH_FXP_UNBLOCK, at line 2281, I see handle 'handle' on which a SSH_FXP_BLOCK request has previously been issued. This seems to imply that an UNBLOCK is needed for every BLOCK. Is this true, or is it needed only for *successful* BLOCKs? If (as I'd expect) the latter, I'd suggest s/been issued/succeeded/. In 9.1.2, results are undefined file types other than (line 3015) s/file/for &/ There is also a blank line missing a few lines later, before hash-algorithm-list. The trailing end-of-sentence . is missing at the end of hash-algorithm-list's description (line 3043). /~\ The ASCII der Mouse \ / Ribbon Campaign X Against HTML mouse@rodents.montreal.qc.ca / \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B From bounces-ietf-ssh-owner-secsh-archive=odin.ietf.org@NetBSD.org Tue Jun 14 03:59:10 2005 Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA19375 for ; Tue, 14 Jun 2005 03:59:10 -0400 (EDT) Received: by mail.netbsd.org (Postfix, from userid 0) id A8F443A6D6; Tue, 14 Jun 2005 07:58:27 +0000 (UTC) X-Original-To: ietf-ssh@NetBSD.org Delivered-To: ietf-ssh@NetBSD.org Received: from outbound1.sopragroup.com (outbound1.z-ptx-11.fr.sopragroup.com [81.80.239.198]) by mail.netbsd.org (Postfix) with ESMTP id D645E3A6DB for ; Tue, 14 Jun 2005 07:58:24 +0000 (UTC) Received: by outbound1.sopragroup.com (8.12.10/8.12.10/outbound-A02) with ESMTP id j5E7wJN6000750 for ; Tue, 14 Jun 2005 09:58:22 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: filexfer-09.txt Date: Tue, 14 Jun 2005 09:58:19 +0200 Message-ID: Thread-Topic: filexfer-09.txt Thread-Index: AcVwtpRssO/9YFWLSvSNy1+kp/D4rg== From: "Ouadah Farid" To: X-OriginalArrivalTime: 14 Jun 2005 08:02:48.0656 (UTC) FILETIME=[748B9D00:01C570B7] X-Scanned-By: MIMEDefang 2.38 Sender: ietf-ssh-owner@NetBSD.org Precedence: list Content-Transfer-Encoding: quoted-printable Hello, I suggest those modifications: 3.1 A client MUST be prepared to recieve responses to multiple overlapped requests out of order. recieve =3D> receive 4.5 extension-count Count of extension names in the attrib-extension array. The definition is the same as attrib-extension-count. Farid. From bounces-ietf-ssh-owner-secsh-archive=odin.ietf.org@NetBSD.org Tue Jun 14 06:27:13 2005 Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA00501 for ; Tue, 14 Jun 2005 06:27:12 -0400 (EDT) Received: by mail.netbsd.org (Postfix, from userid 0) id 010773A410; Tue, 14 Jun 2005 10:27:06 +0000 (UTC) X-Original-To: ietf-ssh@netbsd.org Delivered-To: ietf-ssh@netbsd.org Received: from chiark.greenend.org.uk (chiark.greenend.org.uk [193.201.200.170]) by mail.netbsd.org (Postfix) with ESMTP id EC30C3A3B3 for ; Tue, 14 Jun 2005 10:27:04 +0000 (UTC) Received: by chiark.greenend.org.uk (Debian Exim 3.35 #1) with local (return-path bjharris@chiark.greenend.org.uk) id 1Di8dL-0005Pl-00; Tue, 14 Jun 2005 11:27:03 +0100 From: Ben Harris To: ietf-ssh@NetBSD.org, sommerfeld@sun.com Subject: Re: IANA protocol registry for secure shell protocol parameters now exists. In-Reply-To: <1118684487.26495.3.camel@thunk> References: <1118684487.26495.3.camel@thunk> Organization: Linux Unlimited Message-Id: Date: Tue, 14 Jun 2005 11:27:03 +0100 Sender: ietf-ssh-owner@NetBSD.org Precedence: list In article <1118684487.26495.3.camel@thunk> you write: >FYI, the IANA registry for Secure Shell protocol parameters has been >created: > >http://www.iana.org/assignments/ssh-parameters Oh dear. This reveals several errors in the core drafts that somehow slipped through (though I'm sure I noticed most of them and even got acks from the editor). I'll mail IANA and ask what's to be done. For reference, here's the list I'm sending them: The following entries in the Message Numbers table shouldn't have been listed in draft-ietf-secsh-assignednumbers-12, since they're in the method-specific space: 30 SSH_MSG_KEXDH_INIT [SSH-TRANS] 31 SSH_MSG_KEXDH_REPLY [SSH-TRANS] The following entries in the Message Numbers table shouldn't have been registered by draft-ietf-secsh-auth-kbdinteract-07 because they're in the method-specific space: 60 SSH_MSG_USERAUTH_INFO_REQUEST [RFC-ietf-secsh-auth-kbdinteract-07.txt] 61 SSH_MSG_USERAUTH_INFO_RESPONSE The following entry for the Pseudo-Terminal Encoded Terminal Modes table provides the correct reference: 0 TTY_OP_END Indicates end of options. [SSH-CONNECT, section 8] The following entry is missing from the Authentication Method Names table, despite being defined by draft-ietf-secsh-auth-kbdinteract-07: keyboard-interactive [RFC-ietf-secsh-auth-kbdinteract-07.txt] The following entries in the Public Key Algorithm Names table shouldn't have been mentioned in draft-ietf-secsh-assignednumbers-12, since they're not mentioned in draft-ietf-secsh-transport-24: pgp-sign-rsa [SSH-TRANS, Section 6.6] pgp-sign-dss [SSH-TRANS, Section 6.6] -- Ben Harris From bounces-ietf-ssh-owner-secsh-archive=odin.ietf.org@NetBSD.org Tue Jun 14 13:52:17 2005 Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08814 for ; Tue, 14 Jun 2005 13:52:17 -0400 (EDT) Received: by mail.netbsd.org (Postfix, from userid 0) id CC1A53A4AE; Tue, 14 Jun 2005 17:52:08 +0000 (UTC) X-Original-To: ietf-ssh@netbsd.org Delivered-To: ietf-ssh@netbsd.org Received: from carter-zimmerman.mit.edu (CARTER-ZIMMERMAN.MIT.EDU [18.18.3.197]) by mail.netbsd.org (Postfix) with ESMTP id 5BA133A48C for ; Tue, 14 Jun 2005 17:52:07 +0000 (UTC) Received: by carter-zimmerman.mit.edu (Postfix, from userid 8042) id 53E4EE0063; Tue, 14 Jun 2005 13:51:27 -0400 (EDT) To: Ben Harris Cc: sommerfeld@sun.com, ietf-ssh@NetBSD.org Subject: Re: draft-ietf-secsh-newmodes-04: ready to go forward. References: <1113508171.20584.1058.camel@unknown.hamachi.org> From: Sam Hartman Date: Tue, 14 Jun 2005 13:51:27 -0400 In-Reply-To: (Ben Harris's message of "Thu, 14 Apr 2005 22:42:27 +0100") Message-ID: User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: ietf-ssh-owner@NetBSD.org Precedence: list >>>>> "Ben" == Ben Harris writes: Ben> The abstract mentions [ACM CCS 2002], which doesn't appear Ben> in the references. Abstracts cannot have references. From bounces-ietf-ssh-owner-secsh-archive=odin.ietf.org@NetBSD.org Tue Jun 14 13:55:03 2005 Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09180 for ; Tue, 14 Jun 2005 13:55:02 -0400 (EDT) Received: by mail.netbsd.org (Postfix, from userid 0) id 081E73A4FD; Tue, 14 Jun 2005 17:55:00 +0000 (UTC) X-Original-To: ietf-ssh@netbsd.org Delivered-To: ietf-ssh@netbsd.org Received: from carter-zimmerman.mit.edu (CARTER-ZIMMERMAN.MIT.EDU [18.18.3.197]) by mail.netbsd.org (Postfix) with ESMTP id 81E783A4C6 for ; Tue, 14 Jun 2005 17:54:58 +0000 (UTC) Received: by carter-zimmerman.mit.edu (Postfix, from userid 8042) id 030E9E0063; Tue, 14 Jun 2005 13:54:22 -0400 (EDT) To: ietf-ssh@NetBSD.org Subject: newmodes draft and draft-harris-ssh-arcfour-fixes From: Sam Hartman Date: Tue, 14 Jun 2005 13:54:22 -0400 Message-ID: User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: ietf-ssh-owner@NetBSD.org Precedence: list Hi. I'm considering the ongoing last call for the arcfour-fixes draft. One thing I'm considering doing is blocking arcfour-fixes on draft-ietf-secsh-newmodes and having a statement in arcfour-fixes that points out the conditions under which rc4 is the right cipher to use but that refers to the newmodes ciphers as a more secure alternative. If I'm going to do that, the newmodes draft needs to be ready relatively soon. I don't think that should be problematic based on comments on the list in April. This is just a prod that I'd like to see that on my plate before end of June if possible. From bounces-ietf-ssh-owner-secsh-archive=odin.ietf.org@NetBSD.org Wed Jun 15 17:21:29 2005 Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07613 for ; Wed, 15 Jun 2005 17:21:29 -0400 (EDT) Received: by mail.netbsd.org (Postfix, from userid 0) id 5BABC3A69C; Wed, 15 Jun 2005 21:21:20 +0000 (UTC) X-Original-To: ietf-ssh@netbsd.org Delivered-To: ietf-ssh@netbsd.org Received: from newodin.ietf.org (unknown [132.151.6.50]) by mail.netbsd.org (Postfix) with ESMTP id C50A43A69A for ; Wed, 15 Jun 2005 21:21:17 +0000 (UTC) Received: from mlee by newodin.ietf.org with local (Exim 4.43) id 1DieGN-0006xs-An; Wed, 15 Jun 2005 16:13:27 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org Cc: ietf-ssh@NetBSD.org From: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-secsh-scp-sftp-ssh-uri-02.txt Message-Id: Date: Wed, 15 Jun 2005 16:13:27 -0400 Sender: ietf-ssh-owner@NetBSD.org Precedence: list --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Secure Shell Working Group of the IETF. Title : SCP/SFTP/SSH URI Format Author(s) : S. Suehring, J. Salowey Filename : draft-ietf-secsh-scp-sftp-ssh-uri-02.txt Pages : 8 Date : 2005-6-15 This document describes the Uniform Resource Identifiers used to locate resources for the SCP, SFTP, and SSH protocols. The document describes the generic syntax involved in URI definitions as well as specific definitions for each protocol. These specific definitions may include user credentials such as username and password and also may include other parameters such as fingerprint. In addition, security considerations and examples are also provided within this document. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-secsh-scp-sftp-ssh-uri-02.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-secsh-scp-sftp-ssh-uri-02.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-secsh-scp-sftp-ssh-uri-02.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2005-6-15154205.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-secsh-scp-sftp-ssh-uri-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-secsh-scp-sftp-ssh-uri-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-6-15154205.I-D@ietf.org> --OtherAccess-- --NextPart-- From bounces-ietf-ssh-owner-secsh-archive=odin.ietf.org@NetBSD.org Wed Jun 15 17:42:24 2005 Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA08734 for ; Wed, 15 Jun 2005 17:42:24 -0400 (EDT) Received: by mail.netbsd.org (Postfix, from userid 0) id A2E4C3A69A; Wed, 15 Jun 2005 21:42:20 +0000 (UTC) X-Original-To: ietf-ssh@netbsd.org Delivered-To: ietf-ssh@netbsd.org Received: from chiark.greenend.org.uk (chiark.greenend.org.uk [193.201.200.170]) by mail.netbsd.org (Postfix) with ESMTP id A43233A638 for ; Wed, 15 Jun 2005 21:42:18 +0000 (UTC) Received: by chiark.greenend.org.uk (Debian Exim 3.35 #1) with local (return-path jacobn@chiark.greenend.org.uk) id 1DifeL-00016G-00 for ietf-ssh@netbsd.org; Wed, 15 Jun 2005 22:42:17 +0100 Date: Wed, 15 Jun 2005 22:42:17 +0100 From: Jacob Nevins To: ietf-ssh@NetBSD.org Subject: SCP URIs (draft-ietf-secsh-scp-sftp-ssh-uri-02) Message-ID: <20050615214217.GA2219@chiark.greenend.org.uk> Reply-To: ietf-ssh@NetBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.28i Sender: ietf-ssh-owner@NetBSD.org Precedence: list I still think it's a mistake to attempt to standardise a URI scheme for SCP. Apart from the fact that it's not a documented protocol, my objection from 2003 still holds: =-=-=-=-=- How should filenames containing spaces be represented in scp: URLs? Backslashes? The scp "protocol" requires that such filenames be quoted in some unspecified way (often using Unix shell quoting, but presumably server-dependent). IME, with many current clients it's up to the user to know the quoting convention on the particular server. Either the quoting will have to be embedded in URLs (and hence specified), or quoting becomes the client's responsibility and the standardisation of the URL format will not do much to achieve interoperability. From bounces-ietf-ssh-owner-secsh-archive=odin.ietf.org@NetBSD.org Wed Jun 15 19:47:54 2005 Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17270 for ; Wed, 15 Jun 2005 19:47:53 -0400 (EDT) Received: by mail.netbsd.org (Postfix, from userid 0) id 55F673A668; Wed, 15 Jun 2005 23:47:50 +0000 (UTC) X-Original-To: ietf-ssh@netbsd.org Delivered-To: ietf-ssh@netbsd.org Received: from chiark.greenend.org.uk (chiark.greenend.org.uk [193.201.200.170]) by mail.netbsd.org (Postfix) with ESMTP id 51AC73A599 for ; Wed, 15 Jun 2005 23:47:48 +0000 (UTC) Received: by chiark.greenend.org.uk (Debian Exim 3.35 #1) with local (return-path bjharris@chiark.greenend.org.uk) id 1Dihbn-0004XB-00 for ietf-ssh@netbsd.org; Thu, 16 Jun 2005 00:47:47 +0100 From: Ben Harris To: ietf-ssh@NetBSD.org Subject: Re: I-D ACTION:draft-ietf-secsh-scp-sftp-ssh-uri-02.txt In-Reply-To: References: Organization: Linux Unlimited Message-Id: Date: Thu, 16 Jun 2005 00:47:47 +0100 Sender: ietf-ssh-owner@NetBSD.org Precedence: list In article you write: > Title : SCP/SFTP/SSH URI Format > Author(s) : S. Suehring, J. Salowey > Filename : draft-ietf-secsh-scp-sftp-ssh-uri-02.txt > Pages : 8 > Date : 2005-6-15 I'd really like to see this draft finished, but there are various dull things that need to be fixed: The secsh-architecture and secsh-filexfer drafts should be cited in the introduction when the protocols are first mentioned. "SSH", "SFTP" and "SCP" all need to be expanded on their first use in each of the title, abstract, and body text. The syntax notation used isn't defined. This should probably be done by reference to RFC 2234. Assuming that the syntax notation is intended to be RFC-2234 ABNF, many of the rules are invalid (having '_' and '=' in rule names, not leaving spaces between concatenated elements). The various URI formats seem to allow a userinfo and host not separated by "@". The rules conn-parameter=value, sftp-parameter=value, and abs_path aren't defined. The translation from the octets specified by the URI into filenames sent over SFTP isn't specified. In particular, the state of the filename-translation-control extension isn't defined. The meaning of "typecode=a" isn't clear to me, since "text file" doesn't tell me what character set to expect. The examples should come with prose descriptions of their meanings. Using unqualified hostnames in examples is probably a bad idea. The sixth example is incorrect, since it puts an SFTP parameter in the conn-parameter=value field. There's no IANA Considerations section. -- Ben Harris From bounces-ietf-ssh-owner-secsh-archive=odin.ietf.org@NetBSD.org Wed Jun 15 20:16:35 2005 Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA19831 for ; Wed, 15 Jun 2005 20:16:34 -0400 (EDT) Received: by mail.netbsd.org (Postfix, from userid 0) id 36FE93A6D0; Thu, 16 Jun 2005 00:16:29 +0000 (UTC) X-Original-To: ietf-ssh@netbsd.org Delivered-To: ietf-ssh@netbsd.org Received: from dfw0.icgmedia.com (dfw0.icgmedia.com [69.93.3.2]) by mail.netbsd.org (Postfix) with ESMTP id 3D0353A599 for ; Thu, 16 Jun 2005 00:16:27 +0000 (UTC) Received: from netserver.braingia.org (c24.197.255.185.spt.wi.charter.com [24.197.255.185]) by dfw0.icgmedia.com (Postfix) with ESMTP id C6ED1170CE for ; Wed, 15 Jun 2005 18:51:52 -0500 (CDT) Received: from netserver.braingia.org (netserver.braingia.org [192.168.1.10]) by netserver.braingia.org (8.13.4/8.13.4/Debian-3) with ESMTP id j5FNpoNS009039 for ; Wed, 15 Jun 2005 18:51:50 -0500 Received: (from suehring@localhost) by netserver.braingia.org (8.13.4/8.13.4/Submit) id j5FNpobe009038 for ietf-ssh@netbsd.org; Wed, 15 Jun 2005 18:51:50 -0500 Date: Wed, 15 Jun 2005 18:51:50 -0500 From: Steve Suehring To: ietf-ssh@NetBSD.org Subject: Re: SCP URIs (draft-ietf-secsh-scp-sftp-ssh-uri-02) Message-ID: <20050615235150.GA8931@mail.braingia.org> Mail-Followup-To: Steve Suehring , ietf-ssh@netbsd.org References: <20050615214217.GA2219@chiark.greenend.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050615214217.GA2219@chiark.greenend.org.uk> User-Agent: Mutt/1.5.9i Sender: ietf-ssh-owner@NetBSD.org Precedence: list Joe and I had discussed this and we wanted to leave it to the consensus of the group as to whether SCP should remain in the spec. My problem with including it is that there's no current draft for SCP but I'm open to input. If we can get a quick consensus, I'll submit a new version of the draft without the SCP bits (and with other fixes as I just noticed an e-mail from Ben Harris.) Steve On Wed, Jun 15, 2005 at 10:42:17PM +0100, Jacob Nevins wrote: > I still think it's a mistake to attempt to standardise a URI scheme for > SCP. Apart from the fact that it's not a documented protocol, my > objection from 2003 still holds: > > =-=-=-=-=- > How should filenames containing spaces be represented in scp: URLs? > Backslashes? > > The scp "protocol" requires that such filenames be quoted in some > unspecified way (often using Unix shell quoting, but presumably > server-dependent). > IME, with many current clients it's up to the user to know the quoting > convention on the particular server. Either the quoting will have to > be embedded in URLs (and hence specified), or quoting becomes the > client's responsibility and the standardisation of the URL format will > not do much to achieve interoperability. From bounces-ietf-ssh-owner-secsh-archive=odin.ietf.org@NetBSD.org Wed Jun 15 21:09:04 2005 Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA23892 for ; Wed, 15 Jun 2005 21:09:04 -0400 (EDT) Received: by mail.netbsd.org (Postfix, from userid 0) id A3BE33A475; Thu, 16 Jun 2005 01:08:57 +0000 (UTC) X-Original-To: ietf-ssh@netbsd.org Delivered-To: ietf-ssh@netbsd.org Received: from vandyke.com (mail.vandyke.com [204.134.9.1]) by mail.netbsd.org (Postfix) with ESMTP id AD6D73A39F for ; Thu, 16 Jun 2005 01:08:55 +0000 (UTC) Received: from [127.0.0.1] (HELO [127.0.0.3]) by vandyke.com (CommuniGate Pro SMTP 3.4.7) with ESMTP id 7557988; Wed, 15 Jun 2005 19:08:54 -0600 Message-ID: <42B0D132.20709@vandyke.com> Date: Wed, 15 Jun 2005 19:09:06 -0600 From: Joseph Galbraith User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Steve Suehring Cc: ietf-ssh@NetBSD.org Subject: Re: SCP URIs (draft-ietf-secsh-scp-sftp-ssh-uri-02) References: <20050615214217.GA2219@chiark.greenend.org.uk> <20050615235150.GA8931@mail.braingia.org> In-Reply-To: <20050615235150.GA8931@mail.braingia.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: ietf-ssh-owner@NetBSD.org Precedence: list Content-Transfer-Encoding: 7bit I would vote to give SCP the ax. Thanks, Joseph Steve Suehring wrote: > Joe and I had discussed this and we wanted to leave it to the consensus > of the group as to whether SCP should remain in the spec. My problem > with including it is that there's no current draft for SCP but I'm open > to input. > > If we can get a quick consensus, I'll submit a new version of the draft > without the SCP bits (and with other fixes as I just noticed an e-mail > from Ben Harris.) > > Steve > > On Wed, Jun 15, 2005 at 10:42:17PM +0100, Jacob Nevins wrote: > >>I still think it's a mistake to attempt to standardise a URI scheme for >>SCP. Apart from the fact that it's not a documented protocol, my >>objection from 2003 still holds: >> >>=-=-=-=-=- >>How should filenames containing spaces be represented in scp: URLs? >>Backslashes? >> >>The scp "protocol" requires that such filenames be quoted in some >>unspecified way (often using Unix shell quoting, but presumably >>server-dependent). >>IME, with many current clients it's up to the user to know the quoting >>convention on the particular server. Either the quoting will have to >>be embedded in URLs (and hence specified), or quoting becomes the >>client's responsibility and the standardisation of the URL format will >>not do much to achieve interoperability. > > From bounces-ietf-ssh-owner-secsh-archive=odin.ietf.org@NetBSD.org Thu Jun 16 11:29:41 2005 Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01697 for ; Thu, 16 Jun 2005 11:29:40 -0400 (EDT) Received: by mail.netbsd.org (Postfix, from userid 0) id 256033A7D6; Thu, 16 Jun 2005 15:29:37 +0000 (UTC) X-Original-To: ietf-ssh@netbsd.org Delivered-To: ietf-ssh@netbsd.org Received: from chiark.greenend.org.uk (chiark.greenend.org.uk [193.201.200.170]) by mail.netbsd.org (Postfix) with ESMTP id 57F273A7D3 for ; Thu, 16 Jun 2005 15:29:35 +0000 (UTC) Received: by chiark.greenend.org.uk (Debian Exim 3.35 #1) with local (return-path bjharris@chiark.greenend.org.uk) id 1DiwJC-00035o-00 for ietf-ssh@netbsd.org; Thu, 16 Jun 2005 16:29:34 +0100 From: Ben Harris To: ietf-ssh@NetBSD.org Subject: Re: I-D ACTION:draft-ietf-secsh-scp-sftp-ssh-uri-02.txt In-Reply-To: References: Organization: Linux Unlimited Message-Id: Date: Thu, 16 Jun 2005 16:29:34 +0100 Sender: ietf-ssh-owner@NetBSD.org Precedence: list In article you write: > Title : SCP/SFTP/SSH URI Format > Author(s) : S. Suehring, J. Salowey > Filename : draft-ietf-secsh-scp-sftp-ssh-uri-02.txt > Pages : 8 > Date : 2005-6-15 Some more substantive comments (these might need discussion): SCP URIs should go, since there's no standard definition of SCP. I'm a little worried that this draft will get stuck in the RFC-Editor queue waiting for its normative reference to SFTP to be fulfilled. It would be a pity if SSH URIs got held up because of this. The interpretation of the password part of userinfo isn't specified. In particular, it's not clear whether it only applies to "password" athentication, or also to "keyboard-interactive". Regarding the various kinds of parameters, the draft says that "Additional parameters MAY be used", but doesn't specify how such parameters should be named or what an implementation should do upon receiving such an unrecognised parameter. -- Ben Harris From bounces-ietf-ssh-owner-secsh-archive=odin.ietf.org@NetBSD.org Fri Jun 17 14:50:16 2005 Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12447 for ; Fri, 17 Jun 2005 14:50:15 -0400 (EDT) Received: by mail.netbsd.org (Postfix, from userid 0) id 598F43A834; Fri, 17 Jun 2005 18:50:10 +0000 (UTC) X-Original-To: ietf-ssh@NetBSD.org Delivered-To: ietf-ssh@NetBSD.org Received: from pigeon.alphaweb.net (69-12-155-130.dsl.static.sonic.net [69.12.155.130]) by mail.netbsd.org (Postfix) with ESMTP id C12A33A833 for ; Fri, 17 Jun 2005 18:50:08 +0000 (UTC) Received: from localhost ([127.0.0.1] helo=peiscg33m) by pigeon.alphaweb.net with smtp (Exim 4.10) id 1DjLP8-00026F-00 for ietf-ssh@NetBSD.org; Fri, 17 Jun 2005 11:17:22 -0700 Message-ID: <00a501c5736d$623ecec0$5c8be5a9@ohr.berkeley.edu> From: "Sara Golemon" To: Subject: draft-ietf-secsh-filexfer Change to rename op in version 5 Date: Fri, 17 Jun 2005 11:50:08 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1478 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478 Sender: ietf-ssh-owner@NetBSD.org Precedence: list Content-Transfer-Encoding: 7bit I got tripped up by some vague wording in the changelog covering differences between version 4 and version 5, specifically: o Add support for better control of the rename operation. After looking through implementation sources, I found that this refers to the addition of the flags parameter to FXP_RENAME. byte SSH_FXP_RENAME uint32 request-id string oldpath [UTF-8] string newpath [UTF-8] uint32 flags To avoid others being confused by this I'd like to propose a change to the changelog entry's wording: o Add flags parameter to the rename operation to control rename behavior. Thank you, -Sara From bounces-ietf-ssh-owner-secsh-archive=odin.ietf.org@NetBSD.org Wed Jun 22 14:04:45 2005 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dl9af-0005rv-Bu for secsh-archive@megatron.ietf.org; Wed, 22 Jun 2005 14:04:45 -0400 Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07807 for ; Wed, 22 Jun 2005 14:04:43 -0400 (EDT) Received: by mail.netbsd.org (Postfix, from userid 0) id 11A213A682; Wed, 22 Jun 2005 18:04:35 +0000 (UTC) X-Original-To: ietf-ssh@netbsd.org Delivered-To: ietf-ssh@netbsd.org Received: from ticket.ietf.org (ticket.ietf.org [132.151.6.18]) by mail.netbsd.org (Postfix) with ESMTP id 270E03A667 for ; Wed, 22 Jun 2005 18:04:32 +0000 (UTC) Received: from apache by ticket.ietf.org with local (Exim 4.33) id 1Dl9eP-0001Tp-18 for ietf-ssh@netbsd.org; Wed, 22 Jun 2005 14:08:37 -0400 Subject: [Inquiry #66622] Resolved: IETF mailing list archive for SECSH WG not being updated From: "Scott Blomquist via RT" Reply-To: ietf-action@ietf.org In-Reply-To: Message-ID: X-RT-Loop-Prevention: Inquiry RT-Ticket: Inquiry #66622 Managed-by: RT 3.2.1 (http://www.bestpractical.com/rt/) RT-Originator: ietf-admin@techsquare.com To: ietf-ssh@NetBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" X-RT-Original-Encoding: utf-8 Date: Wed, 22 Jun 2005 14:08:37 -0400 Sender: ietf-ssh-owner@NetBSD.org Precedence: list According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. From bounces-ietf-ssh-owner-secsh-archive=odin.ietf.org@NetBSD.org Wed Jun 22 14:04:57 2005 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dl9ar-0005s8-6d for secsh-archive@megatron.ietf.org; Wed, 22 Jun 2005 14:04:57 -0400 Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07858 for ; Wed, 22 Jun 2005 14:04:55 -0400 (EDT) Received: by mail.netbsd.org (Postfix, from userid 0) id F21EF3A683; Wed, 22 Jun 2005 18:04:35 +0000 (UTC) X-Original-To: ietf-ssh@netbsd.org Delivered-To: ietf-ssh@netbsd.org Received: from ticket.ietf.org (ticket.ietf.org [132.151.6.18]) by mail.netbsd.org (Postfix) with ESMTP id 289AE3A61A for ; Wed, 22 Jun 2005 18:04:32 +0000 (UTC) Received: from apache by ticket.ietf.org with local (Exim 4.33) id 1Dl9eO-0001Tn-OF for ietf-ssh@netbsd.org; Wed, 22 Jun 2005 14:08:36 -0400 Subject: [Inquiry #66622] IETF mailing list archive for SECSH WG not being updated From: "Scott Blomquist via RT" Reply-To: ietf-action@ietf.org In-Reply-To: Message-ID: X-RT-Loop-Prevention: Inquiry RT-Ticket: Inquiry #66622 Managed-by: RT 3.2.1 (http://www.bestpractical.com/rt/) RT-Originator: ietf-admin@techsquare.com To: ietf-ssh@NetBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" X-RT-Original-Encoding: utf-8 Date: Wed, 22 Jun 2005 14:08:36 -0400 Sender: ietf-ssh-owner@NetBSD.org Precedence: list secsh has been migrated and the ftp site updated. sb. scott blomquist From bounces-ietf-ssh-owner-secsh-archive=odin.ietf.org@NetBSD.org Wed Jun 29 10:45:20 2005 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DndoW-00082q-Q9 for secsh-archive@megatron.ietf.org; Wed, 29 Jun 2005 10:45:20 -0400 Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27687 for ; Wed, 29 Jun 2005 10:45:18 -0400 (EDT) Received: by mail.netbsd.org (Postfix, from userid 0) id 0D3473A60A; Wed, 29 Jun 2005 14:44:32 +0000 (UTC) X-Original-To: ietf-ssh@netbsd.org Delivered-To: ietf-ssh@netbsd.org Received: from carter-zimmerman.mit.edu (CARTER-ZIMMERMAN.MIT.EDU [18.18.3.197]) by mail.netbsd.org (Postfix) with ESMTP id CDE6E3A3E2 for ; Wed, 29 Jun 2005 14:44:28 +0000 (UTC) Received: by carter-zimmerman.mit.edu (Postfix, from userid 8042) id B4D82E0063; Wed, 29 Jun 2005 10:44:03 -0400 (EDT) To: bjh21@bjh21.me.uk Cc: ietf@ietf.org, ietf-ssh@NetBSD.org mail-followups-to: ietf-ssh@netbsd.org mail-copies-to: hartmans-ietf@mit.edu, bjh21@bjh21.me.uk Subject: Resolution of last call comments for draft-harris-ssh-arcfour-fixes-02.txt From: Sam Hartman Date: Wed, 29 Jun 2005 10:44:03 -0400 Message-ID: User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: ietf-ssh-owner@NetBSD.org Precedence: list Hi. The last call period on your draft has expired. As you are no doubt aware there was a significant discussion of the suitability of rc4 for use as a standards-track ssh cipher . The community consensus supports publishing this draft on the standards track. However we need to clearly indicate the applicability of this proposal. Please add an applicability statement discussing the performance advantages of RC4 against the known security weaknesses. You may end up reusing text from your security considerations text. Your applicability statement needs to suggest to the reader that they consider the ssh newmodes draft as an alternative to your rc4 ciphers. This alternative should be chosen in environments where the advantages of RC4 do not make it attractive. The reference to the newmodes draft needs to be normative. I believe that the decision to implement this standard requires evaluation of that draft as well. In addition, procedurally the reference to newmodes needs to block publication of this draft so it is not removed. In addition, I'm still waiting to hear back from you on the questions raised in the security directorate review. While these points are minor, they should be addressed. Thanks for all the hard work. Awaiting your revisions, --Sam From bounces-ietf-ssh-owner-secsh-archive=odin.ietf.org@NetBSD.org Wed Jun 29 11:00:50 2005 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dne3W-0006Ql-5n for secsh-archive@megatron.ietf.org; Wed, 29 Jun 2005 11:00:50 -0400 Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29206 for ; Wed, 29 Jun 2005 11:00:47 -0400 (EDT) Received: by mail.netbsd.org (Postfix, from userid 0) id 5F0323A633; Wed, 29 Jun 2005 15:00:41 +0000 (UTC) X-Original-To: ietf-ssh@netbsd.org Delivered-To: ietf-ssh@netbsd.org Received: from ppsw-1.csi.cam.ac.uk (ppsw-1.csi.cam.ac.uk [131.111.8.131]) by mail.netbsd.org (Postfix) with ESMTP id 2C37A3A3E2 for ; Wed, 29 Jun 2005 15:00:39 +0000 (UTC) X-Cam-SpamDetails: Not scanned X-Cam-AntiVirus: No virus found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from draco.cus.cam.ac.uk ([131.111.8.18]:59221) by ppsw-1.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.131]:25) with esmtp id 1Dne3C-0008Qg-5A (Exim 4.51) for ietf-ssh@netbsd.org (return-path ); Wed, 29 Jun 2005 16:00:30 +0100 Received: from bjh21 (helo=localhost) by draco.cus.cam.ac.uk with local-esmtp (Exim 4.51) id 1Dne3C-0000dz-3T; Wed, 29 Jun 2005 16:00:30 +0100 Date: Wed, 29 Jun 2005 16:00:30 +0100 (BST) From: Ben Harris To: Sam Hartman Cc: ietf@ietf.org, ietf-ssh@NetBSD.org Subject: Re: Resolution of last call comments for draft-harris-ssh-arcfour-fixes-02.txt In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: ietf-ssh-owner@NetBSD.org Precedence: list On Wed, 29 Jun 2005, Sam Hartman wrote: > Please add an applicability statement discussing the performance > advantages of RC4 against the known security weaknesses. You may end > up reusing text from your security considerations text. Your > applicability statement needs to suggest to the reader that they > consider the ssh newmodes draft as an alternative to your rc4 ciphers. > This alternative should be chosen in environments where the advantages > of RC4 do not make it attractive. OK. > In addition, I'm still waiting to hear back from you on the questions > raised in the security directorate review. While these points are > minor, they should be addressed. Um, I don't think I've seen these questions, and a quick grep through my mailbox doesn't turn up the word "directorate" anywhere. Should I have been watching somewhere I wasn't? -- Ben Harris From bounces-ietf-ssh-owner-secsh-archive=odin.ietf.org@NetBSD.org Thu Jun 30 16:26:48 2005 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Do5cW-0002aW-45 for secsh-archive@megatron.ietf.org; Thu, 30 Jun 2005 16:26:48 -0400 Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20377 for ; Thu, 30 Jun 2005 16:26:45 -0400 (EDT) Received: by mail.netbsd.org (Postfix, from userid 0) id C60A93A50F; Thu, 30 Jun 2005 20:26:34 +0000 (UTC) X-Original-To: ietf-ssh@netbsd.org Delivered-To: ietf-ssh@netbsd.org Received: from carter-zimmerman.mit.edu (CARTER-ZIMMERMAN.MIT.EDU [18.18.3.197]) by mail.netbsd.org (Postfix) with ESMTP id 526B23A5C7 for ; Thu, 30 Jun 2005 20:26:28 +0000 (UTC) Received: by carter-zimmerman.mit.edu (Postfix, from userid 8042) id CAF9FE0063; Thu, 30 Jun 2005 16:26:01 -0400 (EDT) To: ietf-ssh@NetBSD.org Subject: What's up with last calls? From: Sam Hartman Date: Thu, 30 Jun 2005 16:26:01 -0400 Message-ID: User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: ietf-ssh-owner@NetBSD.org Precedence: list Speaking as an AD I'd like to know the status of the newmodes draft. I would like to see it soon if possible. Speaking as an individual, I'd like to know what is the status of the gssapi-keyex draft. I believe that it's ready for last call; the editor has requested a last call and there has been nothing sense. Thanks, --Sam