From ietf-ssh-owner-secsh-archive=odin.ietf.org@netbsd.org Tue Dec 3 17:16:40 2002 Received: from mail.netbsd.org (mail.netbsd.org [155.53.1.253]) by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA21956 for ; Tue, 3 Dec 2002 17:16:40 -0500 (EST) Received: (qmail 28308 invoked by uid 605); 3 Dec 2002 22:19:23 -0000 Delivered-To: ietf-ssh@netbsd.org Received: (qmail 28299 invoked from network); 3 Dec 2002 22:19:22 -0000 Received: from nwkea-mail-1.sun.com (192.18.42.13) by mail.netbsd.org with SMTP; 3 Dec 2002 22:19:22 -0000 Received: from centralmail1brm.Central.Sun.COM ([129.147.62.1]) by nwkea-mail-1.sun.com (8.9.3+Sun/8.9.3) with ESMTP id OAA00825 for ; Tue, 3 Dec 2002 14:19:21 -0800 (PST) Received: from binky.central.sun.com (binky.Central.Sun.COM [129.153.128.104]) by centralmail1brm.Central.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id gB3MJLOq028960 for ; Tue, 3 Dec 2002 15:19:21 -0700 (MST) Received: from binky.central.sun.com (localhost [127.0.0.1]) by binky.central.sun.com (8.12.5+Sun/8.12.3) with ESMTP id gB3MIEQx027076 for ; Tue, 3 Dec 2002 14:18:14 -0800 (PST) Received: (from nw141292@localhost) by binky.central.sun.com (8.12.5+Sun/8.12.3/Submit) id gB3MID7p027075 for ietf-ssh@netbsd.org; Tue, 3 Dec 2002 14:18:13 -0800 (PST) Date: Tue, 3 Dec 2002 14:18:13 -0800 From: Nicolas Williams To: ietf-ssh@netbsd.org Subject: Language negotiation clarification requested Message-ID: <20021203141813.D16688@binky.central.sun.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: ietf-ssh-owner@netbsd.org Precedence: list The draft-ietf-secsh-transport-15.txt document is under-specified with respect to how languages are to be negotiated (or even what they are negotiated for). I propose a few clarifications: - The default language for messages that have missing optional language tags should be taken to be the primary language negotiated for the direction of the message or, if none was agreed, the first language in the sender's language support list. - Language tag negotiation during key exchange should be done in such a manner that exact matches are preferred, followed by matches by language tag prefix (language tags have a primary tag and optional sub-tags; "en-GB" has a primary tag "en" and a sub-tag "GB"). Other algorithms are possible, but only one should be specified and allowed. That is, if one side speaks only "en-GB" and the other only "en-US" then the agreed upon language should be "en" and one side should treat "en" as an alias of "en-GB" and the other as an alias of "en-US" (because, Churchill's witty remark(s) to the contrary notwithstanding, the two are close enough for our purposes :) The exact algorithm by which a single language set is derived from two languages_client_to_server or two languages_server_to_client value should be specified because there's currently no other way for each side to determine the other's view of the end result of language negotiation. Alternatively the language negotiation should be extended with additional messages. Either way, at the end of the negotiation both side have to agree exactly on negotiated languages or else we have more trouble defining a default language tag for missing optional language tag fields. ALTERNATIVELY, language range tags should be permitted in the values of languages_client_to_server and languages_server_to_client, but then final agreement on at least one supported language depends on the willingness of one side to include appropriate language range tags in the negotiation. Additionally, the SSHv2 drafts should reference RFC3066, not RFC1766 (the former obsoletes the latter). Neither rfc specifies language tag matching rules such as I describe above. Cheers, Nico -- From ietf-ssh-owner-secsh-archive=odin.ietf.org@netbsd.org Tue Dec 3 17:23:55 2002 Received: from mail.netbsd.org (mail.netbsd.org [155.53.1.253]) by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA22352 for ; Tue, 3 Dec 2002 17:23:55 -0500 (EST) Received: (qmail 2322 invoked by uid 605); 3 Dec 2002 22:26:41 -0000 Delivered-To: ietf-ssh@netbsd.org Received: (qmail 2315 invoked from network); 3 Dec 2002 22:26:40 -0000 Received: from smtp03.mrf.mail.rcn.net (207.172.4.62) by mail.netbsd.org with SMTP; 3 Dec 2002 22:26:40 -0000 Received: from 66-44-102-241.s241.apx2.lnhdc.md.dialup.rcn.com ([66.44.102.241] helo=Moo) by smtp03.mrf.mail.rcn.net with esmtp (Exim 3.35 #4) id 18JLV1-0007fk-00 for ietf-ssh@netbsd.org; Tue, 03 Dec 2002 17:26:39 -0500 From: "Paul Swartz" To: ietf-ssh@netbsd.org Date: Tue, 03 Dec 2002 17:26:37 -0500 MIME-Version: 1.0 Subject: SSH2 server/client supporting PGP keys? Message-ID: <3DECE94D.31016.9E40E0@localhost> X-mailer: Pegasus Mail for Windows (v4.02) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body Sender: ietf-ssh-owner@netbsd.org Precedence: list Content-Transfer-Encoding: 7BIT I sent this originally to c.s.ssh, but I thought I'd try here too. The SSH2 spec supports PGP keys in OpenPGP format for host keys and for user authentication. I plan on adding support for this to my SSH2 server and client and was wondering if there are other servers and clients that support this that I could test against? -p -- Paul Swartz (o_ http://twistedmatrix.com/users/z3p.twistd/ //\ z3p@twistedmatrix.com V_/_ AIM: Z3Penguin From ietf-ssh-owner-secsh-archive=odin.ietf.org@netbsd.org Tue Dec 3 17:54:58 2002 Received: from mail.netbsd.org (mail.netbsd.org [155.53.1.253]) by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA23607 for ; Tue, 3 Dec 2002 17:54:58 -0500 (EST) Received: (qmail 24613 invoked by uid 605); 3 Dec 2002 22:57:42 -0000 Delivered-To: ietf-ssh@netbsd.org Received: (qmail 24598 invoked from network); 3 Dec 2002 22:57:41 -0000 Received: from pheriche.sun.com (192.18.98.34) by mail.netbsd.org with SMTP; 3 Dec 2002 22:57:41 -0000 Received: from eastmail1bur.East.Sun.COM ([129.148.9.49]) by pheriche.sun.com (8.9.3+Sun/8.9.3) with ESMTP id PAA10197 for ; Tue, 3 Dec 2002 15:57:41 -0700 (MST) Received: from thunk.east.sun.com (thunk.East.Sun.COM [129.148.174.66]) by eastmail1bur.East.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id gB3Mve9x023837; Tue, 3 Dec 2002 17:57:40 -0500 (EST) Received: from thunk (localhost [127.0.0.1]) by thunk.east.sun.com (8.12.6+Sun/8.12.3) with ESMTP id gB3MveMf001925; Tue, 3 Dec 2002 17:57:40 -0500 (EST) Message-Id: <200212032257.gB3MveMf001925@thunk.east.sun.com> From: Bill Sommerfeld To: Nicolas Williams cc: ietf-ssh@netbsd.org Subject: Re: Language negotiation clarification requested In-Reply-To: Your message of "Tue, 03 Dec 2002 14:18:13 PST." <20021203141813.D16688@binky.central.sun.com> Reply-to: sommerfeld@east.sun.com Date: Tue, 03 Dec 2002 17:57:40 -0500 Sender: ietf-ssh-owner@netbsd.org Precedence: list the core drafts are currently "frozen" except for process nits. i'm taking this as yet another "defer until we come back to draft standard" issue. - Bill From ietf-ssh-owner-secsh-archive=odin.ietf.org@netbsd.org Tue Dec 3 19:24:02 2002 Received: from mail.netbsd.org (mail.netbsd.org [155.53.1.253]) by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA26713 for ; Tue, 3 Dec 2002 19:24:01 -0500 (EST) Received: (qmail 15425 invoked by uid 605); 4 Dec 2002 00:26:47 -0000 Delivered-To: ietf-ssh@netbsd.org Received: (qmail 15400 invoked from network); 4 Dec 2002 00:26:45 -0000 Received: from pheriche.sun.com (192.18.98.34) by mail.netbsd.org with SMTP; 4 Dec 2002 00:26:45 -0000 Received: from esunmail ([129.147.58.121]) by pheriche.sun.com (8.9.3+Sun/8.9.3) with ESMTP id RAA01829 for ; Tue, 3 Dec 2002 17:26:44 -0700 (MST) Received: from xpa-fe2 ([129.147.58.121]) by edgemail1.Central.Sun.COM (iPlanet Messaging Server 5.2 HotFix 0.8 (built Jul 12 2002)) with ESMTP id <0H6K00FY1JWKIR@edgemail1.Central.Sun.COM> for ietf-ssh@netbsd.org; Tue, 03 Dec 2002 17:26:44 -0700 (MST) Received: from nifty-jr.west.sun.com ([129.153.12.95]) by mail.sun.net (iPlanet Messaging Server 5.2 HotFix 0.2 (built Apr 26 2002)) with ESMTPSA id <0H6K006SLJWB2E@mail.sun.net> for ietf-ssh@netbsd.org; Tue, 03 Dec 2002 17:26:44 -0700 (MST) Date: Tue, 03 Dec 2002 16:22:14 -0800 From: Chris Newman Subject: Re: Language negotiation clarification requested In-reply-to: <20021203141813.D16688@binky.central.sun.com> <200212032257.gB3MveMf001925@thunk.east.sun.com> To: sommerfeld@east.sun.com, ietf-ssh@netbsd.org Message-id: <2147483647.1038932534@nifty-jr.west.sun.com> MIME-version: 1.0 X-Mailer: Mulberry/3.0.0 (Mac OS X) Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT Content-disposition: inline X-message-flag: Outlook: the best virus distribution system around References: <20021203141813.D16688@binky.central.sun.com> Sender: ietf-ssh-owner@netbsd.org Precedence: list Content-Transfer-Encoding: 7BIT begin quotation by Nicolas Williams on 2002/12/3 14:18 -0800: > Additionally, the SSHv2 drafts should reference RFC3066, not RFC1766 > (the former obsoletes the latter). begin quotation by Bill Sommerfeld on 2002/12/3 17:57 -0500: > the core drafts are currently "frozen" except for process nits. > > i'm taking this as yet another "defer until we come back to draft > standard" issue. A normative reference to an obsolete RFC is a process nit. If the ADs notice, they will tell you to update the reference before publication (although fixing it in RFC editor 48-hour last call is probably fine). The other points are valid, but I concur with the decision to defer them. - Chris From ietf-ssh-owner-secsh-archive=odin.ietf.org@netbsd.org Wed Dec 4 09:06:45 2002 Received: from mail.netbsd.org (mail.netbsd.org [155.53.1.253]) by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA11640 for ; Wed, 4 Dec 2002 09:06:44 -0500 (EST) Received: (qmail 20697 invoked by uid 605); 4 Dec 2002 14:09:30 -0000 Delivered-To: ietf-ssh@netbsd.org Received: (qmail 20690 invoked from network); 4 Dec 2002 14:09:29 -0000 Received: from lespaul.process.com (192.42.95.27) by mail.netbsd.org with SMTP; 4 Dec 2002 14:09:29 -0000 Received: by lespaul.process.com with Internet Mail Service (5.5.2653.19) id ; Wed, 4 Dec 2002 09:09:28 -0500 Message-ID: <63D30D6E10CFD11190A90000F805FE86040AA892@lespaul.process.com> From: Richard Whalen To: ietf-ssh@netbsd.org Subject: RE: New draft-draft of sftp... Date: Wed, 4 Dec 2002 09:09:27 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: ietf-ssh-owner@netbsd.org Precedence: list I don't recall seeing any discussion on the proposed "file is hidden" flag. I have no problems with it, though it will not be used in a VMS implementation. No problems with the rest of the changes below either. -----Original Message----- From: Joseph Galbraith [mailto:galb-list@vandyke.com] Sent: Monday, November 25, 2002 4:40 PM To: ietf-ssh@netbsd.org Subject: New draft-draft of sftp... Greetings, Here, is a new draft-draft of the sftp draft. Changes are a little bit more extensive than I remembered at the meeting: o Copied more NFS to clarify ACLs and reserved identifiers for the ACL who field. Thanks Richard. (I may need to do one more round of this-- in the context of normative vs. non-normative, I would prefer our NFS references to be non-normative, which means we have to included sufficient information to stand alone. Probably a good idea anyway.) o Change times to be 64 bit + 32 bit nanosecond field (as per decision at meeting and NFS.) o Added additional optional extension to allow the server to tell the client that it compares files in a case insensitive way, or that files are stored in a case insensitive way. Since globbing is done on the client, the client needs this information to "get it right". In the absence of the extension, client is to assume 'case sensitive'. I would like to make one more change that I know of: o add a bit to the type field to flag whether the file should be hidden. Under most unixes files beginning with a '.' should be hidden. Windows represents this with an attribute bit. So, only the server can really tell whether a given file should be hidden (by default) or not. If people are okay with this I will make this change and submit. We are in a hurry here because we want to get this out before we have implementers so that we don't have to rev the version field again. Are any of the unix implementers out there looking at this revision any time soon? As I mentioned at the working group meeting, I would like to have a unix implementation to make sure we have made things onerous for unix / posixish systems. Thanks, Joseph From ietf-ssh-owner-secsh-archive=odin.ietf.org@netbsd.org Wed Dec 4 18:46:45 2002 Received: from mail.netbsd.org (mail.netbsd.org [155.53.1.253]) by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA10803 for ; Wed, 4 Dec 2002 18:46:45 -0500 (EST) Received: (qmail 13125 invoked by uid 605); 4 Dec 2002 23:49:30 -0000 Delivered-To: ietf-ssh@netbsd.org Received: (qmail 13118 invoked from network); 4 Dec 2002 23:49:29 -0000 Received: from kathmandu.sun.com (192.18.98.36) by mail.netbsd.org with SMTP; 4 Dec 2002 23:49:29 -0000 Received: from centralmail1brm.Central.Sun.COM ([129.147.62.1]) by kathmandu.sun.com (8.9.3+Sun/8.9.3) with ESMTP id QAA18304; Wed, 4 Dec 2002 16:49:10 -0700 (MST) Received: from binky.central.sun.com (binky.Central.Sun.COM [129.153.128.104]) by centralmail1brm.Central.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id gB4Nn9Oq007565; Wed, 4 Dec 2002 16:49:10 -0700 (MST) Received: from binky.central.sun.com (localhost [127.0.0.1]) by binky.central.sun.com (8.12.5+Sun/8.12.3) with ESMTP id gB4Nm2Qx028024; Wed, 4 Dec 2002 15:48:02 -0800 (PST) Received: (from nw141292@localhost) by binky.central.sun.com (8.12.5+Sun/8.12.3/Submit) id gB4Nm0KC028023; Wed, 4 Dec 2002 15:48:00 -0800 (PST) Date: Wed, 4 Dec 2002 15:48:00 -0800 From: Nicolas Williams To: ietf-ssh@netbsd.org Cc: putty@projects.tartarus.org, openssh-unix-dev@mindrot.org Subject: Connectathon 2003 reminder Message-ID: <20021204154800.F16688@binky.central.sun.com> Mail-Followup-To: ietf-ssh@netbsd.org, putty@projects.tartarus.org, openssh-unix-dev@mindrot.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: ietf-ssh-owner@netbsd.org Precedence: list [Reminder: The early registration for Connectathon closes at the end of this month.] Get ready for Connectathon 2003! The 17th annual interoperability testing event for engineers only will be held Feb. 27-March 6, 2003 in San Jose, California. For the past 2 years, Connectathon booth space has sold out! Get your registration forms and fees in early and take advantage of registration discounts available through December 31st. Connectathon, sponsored by Sun Microsystems, Inc., hosts over 50 companies annually in an effort to test and debug source code which utilize the following technologies and protocols: NFS versions 2, 3 and 4 NFS over RDMA NFSv4 replication and migration Lock Manager Kerberos Automounter IPv6 IPsec NDMP Mobile IPv6 Secure Shell CIFS Based on demand, in addition we are considering to offer: Diameter/AAA SCTP LDAP DHCPv6 If you are interested in testing any of the above 4 protocols, please send a note to Cthon@sun.com and we'll gauge interest. Or if you have a suggestion for another technology, feel free to contact us as well. Testing continues 24 hours per day. Technology testing coordinators will organize testing procedures and test suite material. In addition, there will be seminars and speakers addressing various topics. The registration deadline is February 7, 2003. But don't wait that long! And Early Bird Discount on booth fees is available to those who register and pay by December 31, 2002. For the past 2 years, Connectathon has sold out of booth space. Please get your registration materials in quickly to avoid disappointment. Go to http://www.connectathon.org to download all forms and information. If you have any questions, please feel free to contact Audrey Van Belleghem at audrey@vanb.com or (408) 358-9598. We look forward to seeing you at the 17th annual Connectathon event! Audrey Van Belleghem Nicolas Williams Connectathon Manager Secure Shell Connectathon Coordinator From ietf-ssh-owner-secsh-archive=odin.ietf.org@netbsd.org Thu Dec 5 21:28:35 2002 Received: from mail.netbsd.org (mail.netbsd.org [155.53.1.253]) by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA10201 for ; Thu, 5 Dec 2002 21:28:34 -0500 (EST) Received: (qmail 23936 invoked by uid 605); 6 Dec 2002 02:31:19 -0000 Delivered-To: ietf-ssh@netbsd.org Received: (qmail 23927 invoked from network); 6 Dec 2002 02:31:18 -0000 Received: from patan.sun.com (192.18.98.43) by mail.netbsd.org with SMTP; 6 Dec 2002 02:31:18 -0000 Received: from eastmail2bur.East.Sun.COM ([129.148.13.40]) by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id TAA28347; Thu, 5 Dec 2002 19:31:16 -0700 (MST) Received: from thunk.east.sun.com (thunk.East.Sun.COM [129.148.174.66]) by eastmail2bur.East.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id gB62VFig028237; Thu, 5 Dec 2002 21:31:15 -0500 (EST) Received: from thunk (localhost [127.0.0.1]) by thunk.east.sun.com (8.12.6+Sun/8.12.3) with ESMTP id gB62VFMf028785; Thu, 5 Dec 2002 21:31:15 -0500 (EST) Message-Id: <200212060231.gB62VFMf028785@thunk.east.sun.com> From: Bill Sommerfeld To: "Paul Swartz" cc: ietf-ssh@netbsd.org Subject: Re: SSH2 server/client supporting PGP keys? In-Reply-To: Your message of "Tue, 03 Dec 2002 17:26:37 EST." <3DECE94D.31016.9E40E0@localhost> Reply-to: sommerfeld@east.sun.com Date: Thu, 05 Dec 2002 21:31:15 -0500 Sender: ietf-ssh-owner@netbsd.org Precedence: list > I sent this originally to c.s.ssh, but I thought > I'd try here too. > The SSH2 spec supports PGP keys in OpenPGP format > for host keys and for user authentication. I plan > on adding support for this to my SSH2 server and > client and was wondering if there are other > servers and clients that support this that I could > test against? I'm personally unaware of any implementation which does this but i'm not omniscient. (this isn't fatal at proposed standard status). If you find the spec ambiguous/underspecified, you owe us an I-D fleshing out the details ;-) - Bill From ietf-ssh-owner-secsh-archive=odin.ietf.org@netbsd.org Thu Dec 5 23:23:26 2002 Received: from mail.netbsd.org (mail.netbsd.org [155.53.1.253]) by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA13406 for ; Thu, 5 Dec 2002 23:23:25 -0500 (EST) Received: (qmail 28877 invoked by uid 605); 6 Dec 2002 04:26:14 -0000 Delivered-To: ietf-ssh@netbsd.org Received: (qmail 28868 invoked from network); 6 Dec 2002 04:26:13 -0000 Received: from syrinx.oankali.net (209.225.172.154) by mail.netbsd.org with SMTP; 6 Dec 2002 04:26:13 -0000 Received: (from res@localhost) by syrinx.oankali.net (8.11.6/8.11.6) id gB64QBi08824; Thu, 5 Dec 2002 23:26:11 -0500 Date: Thu, 5 Dec 2002 23:26:11 -0500 (EST) From: Richard Silverman X-X-Sender: res@syrinx.oankali.net To: SECSH Discussion List Subject: Re: SSH2 server/client supporting PGP keys? In-Reply-To: <200212060231.gB62VFMf028785@thunk.east.sun.com> Message-ID: References: <200212060231.gB62VFMf028785@thunk.east.sun.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: ietf-ssh-owner@netbsd.org Precedence: list On Thu, 5 Dec 2002, Bill Sommerfeld wrote: > > I sent this originally to c.s.ssh, but I thought > > I'd try here too. > > The SSH2 spec supports PGP keys in OpenPGP format > > for host keys and for user authentication. I plan > > on adding support for this to my SSH2 server and > > client and was wondering if there are other > > servers and clients that support this that I could > > test against? > > I'm personally unaware of any implementation which does this but i'm > not omniscient. (this isn't fatal at proposed standard status)... The ssh.com Unix implementation can use OpenPGP keys for public-key authentication. -- Richard Silverman slade@shore.net From ietf-ssh-owner-secsh-archive=odin.ietf.org@netbsd.org Thu Dec 5 23:25:30 2002 Received: from mail.netbsd.org (mail.netbsd.org [155.53.1.253]) by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA13469 for ; Thu, 5 Dec 2002 23:25:29 -0500 (EST) Received: (qmail 29926 invoked by uid 605); 6 Dec 2002 04:28:18 -0000 Delivered-To: ietf-ssh@netbsd.org Received: (qmail 29912 invoked from network); 6 Dec 2002 04:28:18 -0000 Received: from nwkea-mail-1.sun.com (192.18.42.13) by mail.netbsd.org with SMTP; 6 Dec 2002 04:28:18 -0000 Received: from eastmail1bur.East.Sun.COM ([129.148.9.49]) by nwkea-mail-1.sun.com (8.9.3+Sun/8.9.3) with ESMTP id UAA08140; Thu, 5 Dec 2002 20:28:13 -0800 (PST) Received: from thunk.east.sun.com (thunk.East.Sun.COM [129.148.174.66]) by eastmail1bur.East.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id gB64SC9x009808; Thu, 5 Dec 2002 23:28:12 -0500 (EST) Received: from thunk (localhost [127.0.0.1]) by thunk.east.sun.com (8.12.6+Sun/8.12.3) with ESMTP id gB64SCMf029722; Thu, 5 Dec 2002 23:28:12 -0500 (EST) Message-Id: <200212060428.gB64SCMf029722@thunk.east.sun.com> From: Bill Sommerfeld To: Simon Tatham cc: jaltman@columbia.edu, Darren J Moffat , ietf-ssh@netbsd.org Subject: Re: New draft-draft of sftp... In-Reply-To: Your message of "Tue, 26 Nov 2002 17:06:33 GMT." Reply-to: sommerfeld@east.sun.com Date: Thu, 05 Dec 2002 23:28:12 -0500 Sender: ietf-ssh-owner@netbsd.org Precedence: list > There are certainly undeniable reasons why client-side globbing > causes problems. Unfortunately, I consider this to be an undeniable > reason why server-side globbing can _also_ cause problems. Where > does that leave us? On the one hand, we have potentially inaccurate > results; on the other, we have a potential security hazard (although > as far as I know I'm the only SCP implementor who considers it > remotely important). (WG chair hat off) yes, I agree that seems like something to worry about. Trusting that the server won't feed you bogus pathnames as the result of a glob request seems unwise. - Bill From ietf-ssh-owner-secsh-archive=odin.ietf.org@netbsd.org Wed Dec 11 18:28:46 2002 Received: from mail.netbsd.org (mail.netbsd.org [155.53.1.253]) by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA25229 for ; Wed, 11 Dec 2002 18:28:46 -0500 (EST) Received: (qmail 3807 invoked by uid 605); 11 Dec 2002 23:31:35 -0000 Delivered-To: ietf-ssh@netbsd.org Received: (qmail 3799 invoked from network); 11 Dec 2002 23:31:33 -0000 Received: from nbwww.isc.org (HELO narn.netbsd.org) (204.152.184.198) by mail.netbsd.org with SMTP; 11 Dec 2002 23:31:33 -0000 Received: from hotmail.com (unknown [200.71.8.154]) by narn.netbsd.org (Postfix) with SMTP id 2EBE311122 for ; Wed, 11 Dec 2002 15:31:29 -0800 (PST) From: "La Sociedad Digital / A Sociedade Digital" To: (La Sociedad Digital) Subject: Comunicacion cientifica a la comunidad de Internet y de la Sociedad de la Informacion Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Date: Thu, 12 Dec 2002 08:34:17 -0300 Reply-To: "La Sociedad Digital / A Sociedade Digital" Content-Transfer-Encoding: 8bit Message-Id: <20021211233130.2EBE311122@narn.netbsd.org> Sender: ietf-ssh-owner@netbsd.org Precedence: list Content-Transfer-Encoding: 8bit Versión español al frente, versión portuguesa a continuación, versión inglesa al final. ---------------------------------------------------------------------- ------------ Comunicación científica a la comunidad de Internet y a la comunidad de la Sociedad de la Información. La Sociedad Digital – www.sociedaddigital.org / www.asociedadedigital.org La presente comunicación tiene como objetivo informar a la comunidad de Internet y a la comunidad de la Sociedad de la Información las novedades de los últimos meses del Proyecto La Sociedad Digital. La Sociedad Digital es un proyecto abierto a la comunidad de Internet y de la Sociedad de la Información en el ámbito iberoamericano principalmente, pero no restringido exclusivamente a él. Se trata de la creación del primer espacio de convergencia para los especialistas de habla castellana y portuguesa, bajo la forma de un Portal de la Sociedad de la Información (www.sociedaddigital.org / www.asociedadedigital.org). La estructuración de este espacio comprende, en primer lugar, una subdivisión por áreas temáticas consideradas trascendentes para el desarrollo de la Sociedad de la Información, tales como lengua, brecha digital, gobierno digital, estudios especiales, legislación, situación por países, etc. Una segunda subdivisión apunta a elementos de interactividad como noticias, proyectos, observatorios de información, etc. que apuntan a generar un espacio de intercambio y sinergia entre los especialistas de la región, en la búsqueda de modelos de aplicación y resultados de investigaciones, para que todos sus participantes puedan beneficiarse, construyendo, entre todos, el espacio de la Sociedad de la Información en su tránsito hacia la Sociedad del Conocimiento. Invitamos, en consecuencia, a todos, a visitar el Portal, integrarse, enviar sus aportes intelectuales y usar todos los recursos en él disponibles, los que son, por supuesto, de uso libre y gratuito. (www.sociedaddigital.org / www.asociedadedigital.org). Pueden comunicarse a info@sociedaddigital.org. Todos los comentarios, aportes y observaciones serán bienvenidos. Muy cordialmente, El Presidente del Consejo de Directores de La Sociedad Digital, Prof. Dr. Ricardo Petrissans de Aguilar ricardo@sociedaddigital.org La presente comunicación se realiza por única vez. Se trata de una comunicación científica destinada a los miembros de la Comunidad Científica Iberoamericana. En caso que este mensaje sea considerado por su receptor como carente de interés, rogamos se sirva deletear el mismo. Muchas gracias. __________________________________________________ Comunicação Científica à comunidade da Internet e à Comunidade da Sociedade da Informação. La Sociedad Digital comunica aos usuários da Internet e à comunidade da Sociedade da Informação La Sociedad Digital - www.sociedaddigital.org / www.asociedadedigital.org A presente comunicação tem como objetivo informar à comunidade da Internet e à Comunidade da Sociedade da Informação as novidades dos últimos meses do Projeto da Sociedade Digital. La Sociedad Digital é um projeto aberto à comunidade da Internet e à Sociedade da Informação no âmbito ibero-americano, principalmente, porém não restrito exclusivamente a ele. Trata-se da criação do primeiro espaço de convergência para os especialistas de idioma castelhano e português, sob a forma de um Portal da Sociedade da Informação (www.sociedaddigital.org / www.asociedadedigital.org). A estruturação deste espaço compreende, em primeiro lugar, uma subdivisão por áreas temáticas, consideradas transcendentes para o desenvolvimento da Sociedade da Informação, tais como idioma, brecha digital, governo digital, estudos especiais, legislação, situação por país, etc. Uma segunda subdivisão aponta para elementos de interatividade como notícias, projetos, observatórios de informação, etc., no sentido de gerar um espaço de intercâmbio e sinergia entre os especialistas da região, na busca de modelos de aplicação e resultados de investigações, para que todos seus participantes possam se beneficiar, construindo entre todos o espaço da Sociedade da Informação em seu trânsito até a Sociedade do Conhecimento. Convidamos, então, a todos para uma visita ao Portal, para se integrarem, enviar suas contribuições intelectuais e usar todos os recursos nele disponíveis, que são de uso livre e gratuito. (www.sociedaddigital.org / www.asociedadedigital.org). Para se comunicarem, utilizem info@sociedaddigital.org Todos os comentários, contribuições e observações serão bem-vindos. Cordialmente Prof. Dr. Ricardo Petrissans de Aguilar Presidente do Conselho de Diretores de La Sociedad Digital ricardo@sociedaddigital.org A presente comunicação se realiza uma única vez. Trata-se de comunicação científica destinada aos membros da Comunidade Científica Ibero-americana. Caso esta mensagem seja considerada pelo receptor como carente de interesse, pedimos que seja deletada. Muito obrigado. ________________________________________________________________ Scientific message to the Internet Community and to the Information Society Community. The Digital Society – www.sociedaddigital.org / www.asociedadedigital.org This message has the objective of informing the Internet Community and the Information Society Community the latest news about The Digital Society Project. The Digital Society is a project open mainly to the Internet Community and the Information Society Community in Latin American, however without restrictions to any other countries or regions in the world. It is about the creation of the first forum to portuguese and spanish speaking specialists, under the structure of an internet gate (www.sociedaddigital.org / www.asociedadedigital.org). The structure of this space is divided, in its first level, into areas considered of extreme importance to the development of the Information Society, such as language, (brechas digitais), e-Government, special studies, legislation and country information. On a second level, there are interactive elements such as news, special projects and information centres designed to promote interchanges and synergy between regional specialists, always searching for new models, applications and research results, benefiting all users and paving the road between the Information Society and the Knowledge Society. Therefore, we invite everyone to visit the Internet site, integrate yourself in the community, contribute with your knowledge and use all free available resources. Our address : (www.sociedaddigital.org / www.asociedadedigital.org). Please send any queries and comments to info@sociedaddigital.org. All comments, queries and contributions are welcome. Cordially, President of the Digital Society Board of Directors Ricardo Petrissans de Aguilar, MSc, PhD. ricardo@sociedaddigital.org This message will only be sent once, since it is intended to be directed to the members of the Latin America Scientific Community. If it is not of your interest, please delete it. Thank you for your time and attention. From ietf-ssh-owner-secsh-archive=odin.ietf.org@netbsd.org Wed Dec 18 19:00:34 2002 Received: from mail.netbsd.org (mail.netbsd.org [155.53.1.253]) by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA22567 for ; Wed, 18 Dec 2002 19:00:33 -0500 (EST) Received: (qmail 24504 invoked by uid 605); 19 Dec 2002 00:03:30 -0000 Delivered-To: ietf-ssh@netbsd.org Received: (qmail 24428 invoked from network); 19 Dec 2002 00:03:29 -0000 Received: from mail.vandyke.com (HELO vandyke.com) (204.134.9.1) by mail.netbsd.org with SMTP; 19 Dec 2002 00:03:29 -0000 Received: from [127.0.0.1] (HELO CHAOS) by vandyke.com (CommuniGate Pro SMTP 3.4.7) with SMTP id 1071678 for ietf-ssh@netbsd.org; Wed, 18 Dec 2002 17:03:27 -0700 Message-ID: <011e01c2a6f1$b487c100$4d00a8c0@galb.vandyke.com> From: "Joseph Galbraith" To: Subject: New version of sftp document submitted... Date: Wed, 18 Dec 2002 17:00:56 -0700 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 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Sender: ietf-ssh-owner@netbsd.org Precedence: list Content-Transfer-Encoding: 7bit I've submitted a new version of the sftp draft. Changes vs. last draft-draft are: - clarify handling of large read requests by the server. (As implied by section on packets, server may not handle packets larger than 34K). - clarify usage of stderr by server. (In practice, servers already either intentionaly or unintentionally send errors / warnings / debug information over stderr.) - Add SSH_FX_NO_MEDIA error. - Remove the case extension until we can find consensus. Joseph From ietf-ssh-owner-secsh-archive=odin.ietf.org@netbsd.org Wed Dec 18 19:01:12 2002 Received: from mail.netbsd.org (mail.netbsd.org [155.53.1.253]) by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA22590 for ; Wed, 18 Dec 2002 19:01:11 -0500 (EST) Received: (qmail 25133 invoked by uid 605); 19 Dec 2002 00:04:09 -0000 Delivered-To: ietf-ssh@netbsd.org Received: (qmail 25126 invoked from network); 19 Dec 2002 00:04:08 -0000 Received: from mail.vandyke.com (HELO vandyke.com) (204.134.9.1) by mail.netbsd.org with SMTP; 19 Dec 2002 00:04:08 -0000 Received: from [127.0.0.1] (HELO CHAOS) by vandyke.com (CommuniGate Pro SMTP 3.4.7) with SMTP id 1071679 for ietf-ssh@netbsd.org; Wed, 18 Dec 2002 17:04:07 -0700 Message-ID: <012401c2a6f1$cc36ae60$4d00a8c0@galb.vandyke.com> From: "Joseph Galbraith" To: Subject: Meeting notes... Date: Wed, 18 Dec 2002 17:01:35 -0700 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 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Sender: ietf-ssh-owner@netbsd.org Precedence: list Content-Transfer-Encoding: 7bit Are meeting notes from the Atlanta meeting going to be posted? Thanks, - Joseph From ietf-ssh-owner-secsh-archive=odin.ietf.org@netbsd.org Sat Dec 21 05:56:18 2002 Received: from mail.netbsd.org (mail.netbsd.org [155.53.1.253]) by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA04812 for ; Sat, 21 Dec 2002 05:56:17 -0500 (EST) Received: (qmail 14709 invoked by uid 605); 21 Dec 2002 10:59:13 -0000 Delivered-To: ietf-ssh@netbsd.org Received: (qmail 14702 invoked from network); 21 Dec 2002 10:59:12 -0000 Received: from nic.crt.se (193.12.107.10) by mail.netbsd.org with SMTP; 21 Dec 2002 10:59:12 -0000 Received: from mail.crt.se (postiljon.crt.se [172.16.1.14]) by nic.crt.se (Postfix) with ESMTP id 1075952AD for ; Sat, 21 Dec 2002 11:59:11 +0100 (MET) Received: from crt.se (stargate.crt.se [172.16.0.11]) by mail.crt.se (Postfix) with ESMTP id F0C2F1DFB for ; Sat, 21 Dec 2002 11:59:08 +0100 (MET) Date: Sat, 21 Dec 2002 11:58:53 +0100 (CET) From: Jakob Schlyter To: IETF Secure Shell WG Subject: sshfp and multiple ports Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: ietf-ssh-owner@netbsd.org Precedence: list the sshfp draft describes a method that involves looking up a ssh host key in the dns using a domain name. however, it does not specify how to handle the case where one host listen to multiple port and uses different host keys for some or all of these ports. here are some alternatives on how we could move forward with this issue: a) specifiy a ssh dns srv lookup method that maps a dns domain name for a service (i.e. not a hostname) to one or more hostnames:ports. the sshfp information could be stored at either the srv name or at the resulting hostname. example: _ssh._tcp.login.example.com. IN SRV 0 0 22 host.example.com. _ssh._tcp.login.example.com. IN SSHFP ... _ssh._tcp.cvs.example.com. IN SRV 0 0 1022 host.example.com. _ssh._tcp.cvs.example.com. IN SSHFP ... host.example.com. IN A 10.0.0.1 IN SSHFP ... note that the same result could also be acomplished by using different hostnames and require the client to specify a port number. what fails is if someone would do 'ssh -p 1022 host.example.com' in the example about. b) add a port field to the sshfp resource record. this would be accused of being dns resource record subtyping, something the dns community usually does not like since you cannot lookup a key for a single hostname:port in one query - all keys for that hostname would always be returned. my suggestion is to leave sshfp as it is, write a document describing (a) above and not try to solve the single name and multiple ports problem. happy holidays, jakob From ietf-ssh-owner-secsh-archive=odin.ietf.org@netbsd.org Mon Dec 23 07:56:18 2002 Received: from mail.netbsd.org (mail.netbsd.org [155.53.1.253]) by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA27833 for ; Mon, 23 Dec 2002 07:56:18 -0500 (EST) Received: (qmail 4913 invoked by uid 605); 23 Dec 2002 12:59:17 -0000 Delivered-To: ietf-ssh@netbsd.org Received: (qmail 4906 invoked from network); 23 Dec 2002 12:59:16 -0000 Received: from odin.ietf.org (HELO ietf.org) (132.151.1.176) by mail.netbsd.org with SMTP; 23 Dec 2002 12:59:16 -0000 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA27803; Mon, 23 Dec 2002 07:56:12 -0500 (EST) Message-Id: <200212231256.HAA27803@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-filexfer-04.txt Date: Mon, 23 Dec 2002 07:56:12 -0500 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, T. Ylonen, S. Lehtinen Filename : draft-ietf-secsh-filexfer-04.txt Pages : 38 Date : 2002-12-20 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-04.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. 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-04.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-04.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: <2002-12-20130152.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-secsh-filexfer-04.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-secsh-filexfer-04.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2002-12-20130152.I-D@ietf.org> --OtherAccess-- --NextPart-- From ietf-ssh-owner-secsh-archive=odin.ietf.org@netbsd.org Mon Dec 23 08:55:06 2002 Received: from mail.netbsd.org (mail.netbsd.org [155.53.1.253]) by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA01985 for ; Mon, 23 Dec 2002 08:55:06 -0500 (EST) Received: (qmail 1691 invoked by uid 605); 23 Dec 2002 13:58:05 -0000 Delivered-To: ietf-ssh@netbsd.org Received: (qmail 1681 invoked from network); 23 Dec 2002 13:58:00 -0000 Received: from unknown (HELO jupiter.jmi.co.kr) (211.45.79.102) by mail.netbsd.org with SMTP; 23 Dec 2002 13:58:00 -0000 Received: (qmail 13917 invoked by uid 525); 23 Dec 2002 22:59:03 +0900 Received: (qmail 13839 invoked from network); 23 Dec 2002 22:58:47 +0900 Received: from unknown (HELO polo.jmi.co.kr) (211.45.79.31) by 0 with SMTP; 23 Dec 2002 22:58:47 +0900 Received: from ran.ietf.org (ran.ietf.org [132.151.6.60]) by polo.jmi.co.kr (8.9.0/8.9.0) with ESMTP id XAA29434 for ; Mon, 23 Dec 2002 23:01:55 +0900 (KST) Received: from majordomo by ran.ietf.org with local (Exim 4.10) id 18QSEj-0003lY-00 for ietf-announce-list@ran.ietf.org; Mon, 23 Dec 2002 08:03:13 -0500 Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org) by ran.ietf.org with esmtp (Exim 4.10) id 18QSCS-0003ft-00 for all-ietf@ran.ietf.org; Mon, 23 Dec 2002 08:00:52 -0500 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA27803; Mon, 23 Dec 2002 07:56:12 -0500 (EST) Message-Id: <200212231256.HAA27803@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: hangsang@dreamwiz.com Cc: ietf-ssh@netbsd.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-secsh-filexfer-04.txt Date: Mon, 23 Dec 2002 07:56:12 -0500 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, T. Ylonen, S. Lehtinen Filename : draft-ietf-secsh-filexfer-04.txt Pages : 38 Date : 2002-12-20 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-04.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. 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-04.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-04.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: <2002-12-20130152.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-secsh-filexfer-04.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-secsh-filexfer-04.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2002-12-20130152.I-D@ietf.org> --OtherAccess-- --NextPart-- From ietf-ssh-owner-secsh-archive=odin.ietf.org@netbsd.org Fri Dec 27 10:07:55 2002 Received: from mail.netbsd.org (mail.netbsd.org [155.53.1.253]) by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA09276 for ; Fri, 27 Dec 2002 10:07:54 -0500 (EST) Received: (qmail 9272 invoked by uid 605); 27 Dec 2002 15:10:25 -0000 Delivered-To: ietf-ssh@netbsd.org Received: (qmail 8800 invoked from network); 27 Dec 2002 15:10:04 -0000 Received: from 203.12.33.65.cfl.rr.com (HELO hotmail.com) (65.33.12.203) by mail.netbsd.org with SMTP; 27 Dec 2002 15:10:04 -0000 Reply-To: Message-ID: <008d78c76d5b$8226e7a1$2bc63dc3@nngrpy> From: To: kara_520_smith@hotmail.com Subject: Let's talk ? Date: Fri, 27 Dec 2002 15:56:49 -0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal Sender: ietf-ssh-owner@netbsd.org Precedence: list Content-Transfer-Encoding: 8bit Hi. My name is Kara, I saw your profile on the internet and was wondering if you were interested in maybe going out and doing something some time. I'm new to the area so I really don't know any of the hot spots around town, so if you're interested e-mail me at smith_783@hotmail.com and I will send you a picture of myself. I hope to hear from you soon. -Kara 8611Qhss3-515bbkz7541qJhN6-576Iczc5107xznI7-496AvGv5l49