From ietf-ssh-owner-secsh-archive=odin.ietf.org@netbsd.org Thu Jun 21 01:06:18 2001 Received: from mail.netbsd.org (mail.netbsd.org [155.53.1.253]) by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA04437 for ; Thu, 21 Jun 2001 01:06:17 -0400 (EDT) Received: (qmail 2742 invoked by uid 605); 21 Jun 2001 05:04:16 -0000 Delivered-To: ietf-ssh@netbsd.org Received: (qmail 2734 invoked from network); 21 Jun 2001 05:04:15 -0000 Received: from mail.vandyke.com (204.134.9.1) by mail.netbsd.org with SMTP; 21 Jun 2001 05:04:15 -0000 Received: from bhag2 ([127.0.0.1]) by mail.vandyke.com (Netscape Messaging Server 3.62) with SMTP id 537 for ; Wed, 20 Jun 2001 23:09:25 -0600 Message-ID: <000b01c0fa10$0a996660$0201a8c0@bhag2> From: "Jeff P. Van Dyke" To: References: <200104182258.f3IMwU915088@thunk.east.sun.com> Subject: Re: New draft editor. Date: Wed, 20 Jun 2001 23:06:45 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: ietf-ssh-owner@netbsd.org Precedence: list Content-Transfer-Encoding: 7bit From: "Bill Sommerfeld" > I'm pleased to announce that Darren Moffat > will be taking over as editor of the four core SSH drafts. > > He's promised to have new revisions out soon (especially now that I've > identified him publically :-) ). Bill, It has been a while since you sent this note out. The drafts posted on the IETF web site are dated 9 January, 2001. Is Darren Moffat still working on sending out new drafts? Are you planning on scheduling a working group meeting for the IETF meeting in London? Jeff P. Van Dyke jpv@vandyke.com From ietf-ssh-owner-secsh-archive=odin.ietf.org@netbsd.org Thu Jun 21 11:16:53 2001 Received: from mail.netbsd.org (mail.netbsd.org [155.53.1.253]) by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA02036 for ; Thu, 21 Jun 2001 11:16:52 -0400 (EDT) Received: (qmail 15474 invoked by uid 605); 21 Jun 2001 15:14:31 -0000 Delivered-To: ietf-ssh@netbsd.org Received: (qmail 15467 invoked from network); 21 Jun 2001 15:14:30 -0000 Received: from mail.vandyke.com (204.134.9.1) by mail.netbsd.org with SMTP; 21 Jun 2001 15:14:30 -0000 Received: from oldviper ([192.168.0.16]) by mail.vandyke.com (Netscape Messaging Server 3.62) with SMTP id 457; Thu, 21 Jun 2001 09:19:42 -0600 Message-ID: <002601c0fa64$d9843e10$1000a8c0@oldviper> From: "Jeff P. Van Dyke" To: Cc: Subject: GSSAPI authentication Date: Thu, 21 Jun 2001 09:14:10 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: ietf-ssh-owner@netbsd.org Precedence: list Content-Transfer-Encoding: 7bit I believe at the last IETF meeting in Minnesota there was some discussion about combining the following two drafts: http://www.ietf.org/internet-drafts/draft-ietf-secsh-gsskeyex-01.txt http://www.ietf.org/internet-drafts/draft-galb-secsh-gssapi-01.txt Is that correct? If so, what is the status of this work? Jeff P. Van Dyke jpv@vandyke.com From ietf-ssh-owner-secsh-archive=odin.ietf.org@netbsd.org Thu Jun 21 12:19:28 2001 Received: from mail.netbsd.org (mail.netbsd.org [155.53.1.253]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA04672 for ; Thu, 21 Jun 2001 12:19:27 -0400 (EDT) Received: (qmail 3644 invoked by uid 605); 21 Jun 2001 16:17:11 -0000 Delivered-To: ietf-ssh@netbsd.org Received: (qmail 3182 invoked from network); 21 Jun 2001 16:16:25 -0000 Received: from mercury.sun.com (192.9.25.1) by mail.netbsd.org with SMTP; 21 Jun 2001 16:16:25 -0000 Received: from sunmail1.Sun.COM ([129.145.1.2]) by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA19107; Thu, 21 Jun 2001 09:18:53 -0700 (PDT) Received: from jurassic.eng.sun.com (jurassic.Eng.Sun.COM [129.146.82.166]) by sunmail1.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1-Sun.COM.mod.2) with ESMTP id JAA13575; Thu, 21 Jun 2001 09:20:04 -0700 (PDT) Received: from Eng.Sun.COM (dsl-192-32.Eng.Sun.COM [129.146.192.32]) by jurassic.eng.sun.com (8.11.4+Sun/8.11.4) with ESMTP id f5LGIgG197155; Thu, 21 Jun 2001 09:18:42 -0700 (PDT) Message-ID: <3B321E74.C4F576BD@Eng.Sun.COM> Date: Thu, 21 Jun 2001 09:19:00 -0700 From: Darren Moffat X-Mailer: Mozilla 4.61 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: "Jeff P. Van Dyke" CC: ietf-ssh@netbsd.org Subject: Re: New draft editor. References: <200104182258.f3IMwU915088@thunk.east.sun.com> <000b01c0fa10$0a996660$0201a8c0@bhag2> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: ietf-ssh-owner@netbsd.org Precedence: list Content-Transfer-Encoding: 7bit "Jeff P. Van Dyke" wrote: > > From: "Bill Sommerfeld" > > I'm pleased to announce that Darren Moffat > > will be taking over as editor of the four core SSH drafts. > > > > He's promised to have new revisions out soon (especially now that I've > > identified him publically :-) ). > > Bill, > > It has been a while since you sent this note out. The drafts > posted on the IETF web site are dated 9 January, 2001. Is > Darren Moffat still working on sending out new drafts? I am, and they are pretty much finished and I hope to get them posted out pretty soon. -- Darren J Moffat From ietf-ssh-owner-secsh-archive=odin.ietf.org@netbsd.org Thu Jun 21 13:49:21 2001 Received: from mail.netbsd.org (mail.netbsd.org [155.53.1.253]) by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA10003 for ; Thu, 21 Jun 2001 13:49:20 -0400 (EDT) Received: (qmail 27806 invoked by uid 605); 21 Jun 2001 17:47:19 -0000 Delivered-To: ietf-ssh@netbsd.org Received: (qmail 27799 invoked from network); 21 Jun 2001 17:47:17 -0000 Received: from minbar.fac.cs.cmu.edu (128.2.185.161) by mail.netbsd.org with SMTP; 21 Jun 2001 17:47:17 -0000 Received: from minbar.fac.cs.cmu.edu by minbar.fac.cs.cmu.edu id aa21990; 21 Jun 2001 13:49 EDT Date: Thu, 21 Jun 2001 13:49:37 -0400 (EDT) From: Jeffrey Hutzelman X-Sender: jhutz@minbar.fac.cs.cmu.edu To: "Jeff P. Van Dyke" cc: ietf-ssh@netbsd.org Subject: Re: GSSAPI authentication In-Reply-To: <002601c0fa64$d9843e10$1000a8c0@oldviper> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: ietf-ssh-owner@netbsd.org Precedence: list On Thu, 21 Jun 2001, Jeff P. Van Dyke wrote: > I believe at the last IETF meeting in Minnesota there > was some discussion about combining the following two drafts: > > http://www.ietf.org/internet-drafts/draft-ietf-secsh-gsskeyex-01.txt > http://www.ietf.org/internet-drafts/draft-galb-secsh-gssapi-01.txt > > Is that correct? > > If so, what is the status of this work? Would you believe you're the second person to ask about this _today_ ? I wish I could say I was working on this, but the truth is I've been rather busy and haven't gotten to updating the draft as soon as I'd like. Joe Galbraith is one of the authors of the user auth draft mentioned above, and he indicated he might have some time to work on the changes involved in the merger. I've sent him a brief description of what I had in mind, as well as information about a couple of protocol changes we discussed at the WG meeting in Minneapolis (particularly, signing the host key during key exchange so that sessions don't have to die when the GSSAPI creds used for the initial key exchange expire). My goal is to get another version of this draft out soon enough that we can take into account comments from implementors and this list, and get any corrections out before the London IETF meeting. -- Jeffrey T. Hutzelman (N3NHS) Sr. Research Systems Programmer School of Computer Science - Research Computing Facility Carnegie Mellon University - Pittsburgh, PA From ietf-ssh-owner-secsh-archive=odin.ietf.org@netbsd.org Fri Jun 22 07:14:21 2001 Received: from mail.netbsd.org (mail.netbsd.org [155.53.1.253]) by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA16269 for ; Fri, 22 Jun 2001 07:14:20 -0400 (EDT) Received: (qmail 25914 invoked by uid 605); 22 Jun 2001 11:12:20 -0000 Delivered-To: ietf-ssh@netbsd.org Received: (qmail 25907 invoked from network); 22 Jun 2001 11:12:17 -0000 Received: from odin.ietf.org (HELO ietf.org) (132.151.1.176) by mail.netbsd.org with SMTP; 22 Jun 2001 11:12:17 -0000 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA16166; Fri, 22 Jun 2001 07:13:56 -0400 (EDT) Message-Id: <200106221113.HAA16166@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: ietf-ssh@netbsd.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-secsh-publickeyfile-02.txt Date: Fri, 22 Jun 2001 07:13:56 -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 : SECSH Public Key File Format Author(s) : J. Galbraith, R. Thayer Filename : draft-ietf-secsh-publickeyfile-02.txt Pages : 5 Date : 21-Jun-01 This document formally documents the existing public key file format in use for exchanging public keys between different SECSH implementations. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-secsh-publickeyfile-02.txt 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-publickeyfile-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-publickeyfile-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: <20010621134613.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-secsh-publickeyfile-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-secsh-publickeyfile-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20010621134614.I-D@ietf.org> --OtherAccess-- --NextPart-- From ietf-ssh-owner-secsh-archive=odin.ietf.org@netbsd.org Fri Jun 22 14:41:06 2001 Received: from mail.netbsd.org (mail.netbsd.org [155.53.1.253]) by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA04113 for ; Fri, 22 Jun 2001 14:41:06 -0400 (EDT) Received: (qmail 3874 invoked by uid 605); 22 Jun 2001 18:39:00 -0000 Delivered-To: ietf-ssh@netbsd.org Received: (qmail 3867 invoked from network); 22 Jun 2001 18:38:59 -0000 Received: from patan.sun.com (192.18.98.43) by mail.netbsd.org with SMTP; 22 Jun 2001 18:38:59 -0000 Received: from sunmail1.Sun.COM ([129.145.1.2]) by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id MAA15971 for ; Fri, 22 Jun 2001 12:41:30 -0600 (MDT) Received: from jurassic.eng.sun.com (jurassic.Eng.Sun.COM [129.146.83.130]) by sunmail1.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1-Sun.COM.mod.2) with ESMTP id LAA19608 for ; Fri, 22 Jun 2001 11:42:47 -0700 (PDT) Received: from spica1 (spica1.Eng.Sun.COM [129.146.81.114]) by jurassic.eng.sun.com (8.11.4+Sun/8.11.4) with ESMTP id f5MIfNG467262 for ; Fri, 22 Jun 2001 11:41:23 -0700 (PDT) Date: Fri, 22 Jun 2001 11:39:10 -0700 (PDT) From: Alok Aggarwal X-X-Sender: To: Subject: sftp draft clarification Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: ietf-ssh-owner@netbsd.org Precedence: list Section 3 (General Packet Format) para 4 of draft-ietf-secsh-filexfer-01.txt says: "The maximum size of a packet is in practise determined by the client (the maximum size of read or write requests that it sends, plus a few bytes of packet overhead). All servers SHOULD support packets of at least 34000 bytes (where the packet size refers to the full length, including the header above). This should allow for reads and writes of at most 32768 bytes." The header in question looks like this: uint32 length byte type byte[length - 1] data payload How should the above para be interpreted? I'm a little confused with the part that says all servers should support packets of *at least* 34000 bytes and then says this should allow for reads and writes of *at most* 32768 bytes. Also, why can't the server allow for reads and writes say ~64k bytes? -Alok From ietf-ssh-owner-secsh-archive=odin.ietf.org@netbsd.org Mon Jun 25 05:01:13 2001 Received: from mail.netbsd.org (mail.netbsd.org [155.53.1.253]) by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA09102 for ; Mon, 25 Jun 2001 05:01:11 -0400 (EDT) Received: (qmail 29785 invoked by uid 605); 25 Jun 2001 08:59:02 -0000 Delivered-To: ietf-ssh@netbsd.org Received: (qmail 29775 invoked from network); 25 Jun 2001 08:58:59 -0000 Received: from mail.lysator.liu.se (130.236.254.3) by mail.netbsd.org with SMTP; 25 Jun 2001 08:58:59 -0000 Received: from sture.lysator.liu.se (sture.lysator.liu.se [130.236.254.21]) by mail.lysator.liu.se (Postfix) with ESMTP id 4911282F525; Mon, 25 Jun 2001 11:01:36 +0200 (MET DST) Received: (from nisse@localhost) by sture.lysator.liu.se (8.9.0/8.8.7) id LAA12640; Mon, 25 Jun 2001 11:01:35 +0200 (MET DST) To: Alok Aggarwal Cc: Subject: Re: sftp draft clarification References: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit From: nisse@lysator.liu.se (Niels Möller) Date: 25 Jun 2001 11:01:35 +0200 In-Reply-To: Alok Aggarwal's message of "Fri, 22 Jun 2001 11:39:10 -0700 (PDT)" Message-ID: Lines: 25 X-Mailer: Gnus v5.7/Emacs 20.7 Sender: ietf-ssh-owner@netbsd.org Precedence: list Content-Transfer-Encoding: 7bit Alok Aggarwal writes: > How should the above para be interpreted? I'm a little confused with the part > that says all servers should support packets of *at least* 34000 bytes and then > says this should allow for reads and writes of *at most* 32768 bytes. My interpretation is that 1. A server can choose to not support packets larger than 34000 octets, and still be conforming (say, using a fixed size packet buffer). When such a server receives a packet larger than 34000 octets, it is allowed to simply disconnect the client, or try to recover by sending some reasonable err message back. I.e. if a server implementation has a limit on packet size, that limit must be 34000 octets or larger. 2. A client can rely on being able to send read and write requests for up to 32768K of data; a conforming server has to support that. > Also, why can't the server allow for reads and writes say ~64k bytes? It can, but a client can't expect a random conforming servers to do that. /Niels From ietf-ssh-owner-secsh-archive=odin.ietf.org@netbsd.org Mon Jun 25 11:52:11 2001 Received: from mail.netbsd.org (mail.netbsd.org [155.53.1.253]) by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA19130 for ; Mon, 25 Jun 2001 11:52:10 -0400 (EDT) Received: (qmail 18170 invoked by uid 605); 25 Jun 2001 15:50:05 -0000 Delivered-To: ietf-ssh@netbsd.org Received: (qmail 18157 invoked from network); 25 Jun 2001 15:50:03 -0000 Received: from patan.sun.com (192.18.98.43) by mail.netbsd.org with SMTP; 25 Jun 2001 15:50:03 -0000 Received: from sunmail1.Sun.COM ([129.145.1.2]) by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id JAA09171; Mon, 25 Jun 2001 09:52:37 -0600 (MDT) Received: from jurassic.eng.sun.com (jurassic.Eng.Sun.COM [129.146.83.130]) by sunmail1.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1-Sun.COM.mod.2) with ESMTP id IAA26122; Mon, 25 Jun 2001 08:53:57 -0700 (PDT) Received: from Eng.Sun.COM (dsl-192-32.Eng.Sun.COM [129.146.192.32]) by jurassic.eng.sun.com (8.11.4+Sun/8.11.4) with ESMTP id f5PFqTG845071; Mon, 25 Jun 2001 08:52:29 -0700 (PDT) Message-ID: <3B375E60.3D015455@Eng.Sun.COM> Date: Mon, 25 Jun 2001 08:53:04 -0700 From: Darren Moffat X-Mailer: Mozilla 4.61 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: Niels =?iso-8859-1?Q?M=F6ller?= CC: Alok Aggarwal , ietf-ssh@netbsd.org Subject: Re: sftp draft clarification References: Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: ietf-ssh-owner@netbsd.org Precedence: list Content-Transfer-Encoding: 8bit "Niels Möller" wrote: > > Also, why can't the server allow for reads and writes say ~64k bytes? > > It can, but a client can't expect a random conforming servers to do that. Maybe the protocol needs a packet size negotiation step, otherwise it is going to be very hard for clients and servers that want to have larger packets to be able to make the correct assumptions about what is going on. -- Darren J Moffat From ietf-ssh-owner-secsh-archive=odin.ietf.org@netbsd.org Mon Jun 25 12:08:02 2001 Received: from mail.netbsd.org (mail.netbsd.org [155.53.1.253]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA19566 for ; Mon, 25 Jun 2001 12:08:01 -0400 (EDT) Received: (qmail 21557 invoked by uid 605); 25 Jun 2001 16:02:58 -0000 Delivered-To: ietf-ssh@netbsd.org Received: (qmail 21180 invoked from network); 25 Jun 2001 16:01:41 -0000 Received: from mail.lysator.liu.se (130.236.254.3) by mail.netbsd.org with SMTP; 25 Jun 2001 16:01:41 -0000 Received: from sture.lysator.liu.se (sture.lysator.liu.se [130.236.254.21]) by mail.lysator.liu.se (Postfix) with ESMTP id 0249582F521; Mon, 25 Jun 2001 18:04:19 +0200 (MET DST) Received: (from nisse@localhost) by sture.lysator.liu.se (8.9.0/8.8.7) id SAA00977; Mon, 25 Jun 2001 18:04:18 +0200 (MET DST) To: Darren Moffat Cc: Alok Aggarwal , ietf-ssh@netbsd.org Subject: Re: sftp draft clarification References: <3B375E60.3D015455@Eng.Sun.COM> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit From: nisse@lysator.liu.se (Niels Möller) Date: 25 Jun 2001 18:04:18 +0200 In-Reply-To: Darren Moffat's message of "Mon, 25 Jun 2001 08:53:04 -0700" Message-ID: Lines: 13 X-Mailer: Gnus v5.7/Emacs 20.7 Sender: ietf-ssh-owner@netbsd.org Precedence: list Content-Transfer-Encoding: 7bit Darren Moffat writes: > Maybe the protocol needs a packet size negotiation step, otherwise > it is going to be very hard for clients and servers that want to have > larger packets to be able to make the correct assumptions about what is > going on. I don't think any real negotiation is needed. If large packets are important, we should just invent an extension, and let the server send the extension and its max packet size (or "unlimited") with its SSH_FXP_VERSION packet. /Niels