From owner-ietf-sasl Thu Jan 9 06:27:42 2003 Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h09ERgn19998 for ietf-sasl-bks; Thu, 9 Jan 2003 06:27:42 -0800 (PST) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h09ERfo19994 for ; Thu, 9 Jan 2003 06:27:41 -0800 (PST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11022; Thu, 9 Jan 2003 09:24:27 -0500 (EST) Message-Id: <200301091424.JAA11022@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: ietf-sasl@imc.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-sasl-anon-00.txt Date: Thu, 09 Jan 2003 09:24:27 -0500 Sender: owner-ietf-sasl@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Simple Authentication and Security Layer Working Group of the IETF. Title : The Anonymous SASL Mechanism Author(s) : K. Zeilenga Filename : draft-ietf-sasl-anon-00.txt Pages : 8 Date : 2003-1-8 It is common practice on the Internet to permit anonymous access to various services. Traditionally, this has been done with a plain text password mechanism using 'anonymous' as the user name and optional trace information, such as an email address, as the password. As plaintext login commands are not permitted in new IETF protocols, a new way to provide anonymous login is needed within the context of the Simple Authentication and Security Layer (SASL) framework. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-sasl-anon-00.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-sasl-anon-00.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-sasl-anon-00.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: <2003-1-9092500.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-sasl-anon-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-sasl-anon-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-1-9092500.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-ietf-sasl Fri Jan 10 11:53:54 2003 Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h0AJrsT19356 for ietf-sasl-bks; Fri, 10 Jan 2003 11:53:54 -0800 (PST) Received: from luminous.mit.edu (LUMINOUS.MIT.EDU [18.101.1.61]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h0AJrqo19352 for ; Fri, 10 Jan 2003 11:53:52 -0800 (PST) Received: by luminous.mit.edu (Postfix, from userid 1000) id 3EB8B7680A; Fri, 10 Jan 2003 14:53:12 -0500 (EST) To: ietf-sasl@imc.org Subject: [Internet-Drafts@ietf.org] I-D ACTION:draft-josefsson-sasl-kerberos5-00.txt From: Sam Hartman Date: Fri, 10 Jan 2003 14:53:11 -0500 Message-ID: <87znq893yw.fsf@luminous.mit.edu> Lines: 112 User-Agent: Gnus/5.090006 (Oort Gnus v0.06) Emacs/21.1 (i386-debian-linux-gnu) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Sender: owner-ietf-sasl@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: --=-=-= I understand this is out of scope for our working group, but it seems that forwarding the initial announcement is reasonable. --=-=-= Content-Type: message/rfc822 Content-Disposition: inline Return-Path: Received: from solipsist-nation ([unix socket]) by solipsist-nation (Cyrus v2.1.5-Debian2.1.5-1) with LMTP; Fri, 10 Jan 2003 13:55:55 -0500 X-Sieve: CMU Sieve 2.2 Return-Path: Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by suchdamage.org (Postfix) with ESMTP id 1BC19131E1 for ; Fri, 10 Jan 2003 13:55:55 -0500 (EST) Received: from atalanta.ctd.anl.gov (atalanta.ctd.anl.gov [146.137.194.4]) by fort-point-station.mit.edu (8.9.2/8.9.2) with ESMTP id NAA12883; Fri, 10 Jan 2003 13:55:52 -0500 (EST) Received: (from majordom@localhost) by atalanta.ctd.anl.gov (8.9.1a/8.9.1) id MAA03022 for ietf-krb-wg-outgoing; Fri, 10 Jan 2003 12:52:41 -0600 (CST) Received: from hermes.ctd.anl.gov (localhost [127.0.0.1]) by atalanta.ctd.anl.gov (8.9.1a/8.9.1) with ESMTP id MAA03016 for ; Fri, 10 Jan 2003 12:52:40 -0600 (CST) Received: from hermes.ctd.anl.gov (localhost [127.0.0.1]) by hermes.ctd.anl.gov (8.9.1a/8.9.1) with ESMTP id MAA12809 for ; Fri, 10 Jan 2003 12:52:38 -0600 (CST) Received: from mailrelay.anl.gov (mailrelay.anl.gov [130.202.101.22]) by hermes.ctd.anl.gov (8.9.1a/8.9.1) with ESMTP id MAA12806 for ; Fri, 10 Jan 2003 12:52:38 -0600 (CST) Received: from localhost.localdomain (localhost [127.0.0.1]) by localhost.ctd.anl.gov (Postfix) with ESMTP id 43A605F0DAC; Fri, 10 Jan 2003 12:52:38 -0600 (CST) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by mailrelay.anl.gov (Postfix) with ESMTP id 712555F0D91 for ; Fri, 10 Jan 2003 12:52:37 -0600 (CST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10890; Fri, 10 Jan 2003 13:49:18 -0500 (EST) Message-Id: <200301101849.NAA10890@ietf.org> To: IETF-Announce: ; Cc: ietf-krb-wg@anl.gov From: Internet-Drafts@ietf.org Reply-To: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-josefsson-sasl-kerberos5-00.txt Date: Fri, 10 Jan 2003 13:49:18 -0500 X-Spam-Level: **** Sender: owner-ietf-krb-wg@achilles.ctd.anl.gov Precedence: bulk X-Spam-Status: No, hits=0.8 required=5.0 tests=NO_REAL_NAME,TO_MALFORMED,EXCUSE_6 version=2.20 X-Spam-Level: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===-=-=" --===-=-= A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : A Kerberos 5 SASL Mechanism Author(s) : S. Josefsson Filename : draft-josefsson-sasl-kerberos5-00.txt Pages : 11 Date : 2003-1-9 This document specifies a Simple Authentication and Security Layer (SASL) [3] mechanism for Kerberos 5 Client/Server Authentication [1], with optional initial Authentication Service (AS) and/or Ticket-Granting-Service (TGS) exchanges. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-josefsson-sasl-kerberos5-00.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-josefsson-sasl-kerberos5-00.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-josefsson-sasl-kerberos5-00.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. --===-=-= Content-Type: multipart/alternative; boundary="====-=-=" --====-=-= Content-Type: message/external-body; access-type=mail-server Content-Type: text/plain Content-ID: <2003-1-10140627.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-josefsson-sasl-kerberos5-00.txt --====-=-= Content-Type: message/external-body; name=draft-josefsson-sasl-kerberos5-00.txt; access-type=anon-ftp Content-Type: text/plain Content-ID: <2003-1-10140627.I-D@ietf.org> --====-=-=-- --===-=-=-- --=-=-=-- From owner-ietf-sasl Sun Jan 12 17:17:48 2003 Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h0D1HmB15245 for ietf-sasl-bks; Sun, 12 Jan 2003 17:17:48 -0800 (PST) Received: from janus.hts.com.au (ramnet15.lnk.telstra.net [165.228.239.54]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h0D1Hio15241 for ; Sun, 12 Jan 2003 17:17:46 -0800 (PST) Received: from [203.28.219.179] (pb.hts.com.au [203.28.219.179]) by janus.hts.com.au (8.11.6/8.11.6) with ESMTP id h0D1HiX19761 for ; Mon, 13 Jan 2003 12:17:45 +1100 Posted-Date: Mon, 13 Jan 2003 12:17:45 +1100 Mime-Version: 1.0 Message-Id: Date: Mon, 13 Jan 2003 12:17:42 +1100 To: ietf-sasl@imc.org From: Steve Farmer Subject: 16 Octet Hash Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-ietf-sasl@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Hi all, I may be missing something simple here. I am implementing a SMTP client using SASL. However the rfc specifies a 16 octet hash as well as a 16 octet MD5 hash. Since MD4 gives a 16 octet result , is it OK to use this ? If not what should I be using for the 16 octet hash? Regards Steve Farmer -- ------------------------------------------------- Nearly all men can stand adversity, but if you want to test a man's character, give him power. -Abraham Lincoln, U.S. president (1809-1865) Support free speech; visit http://www.efa.org.au/ Heads Together Services Pty Ltd http://www.hts.com.au Email: hts@hts.com.au Tel: 612 9982 6767 Fax: 612 9981 3081 From owner-ietf-sasl Mon Jan 13 10:19:11 2003 Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h0DIJBl18026 for ietf-sasl-bks; Mon, 13 Jan 2003 10:19:11 -0800 (PST) Received: from smtp7.andrew.cmu.edu (SMTP7.andrew.cmu.edu [128.2.10.87]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h0DIJAo18022 for ; Mon, 13 Jan 2003 10:19:10 -0800 (PST) Received: from penguin.andrew.cmu.edu (PENGUIN.andrew.cmu.edu [128.2.121.100]) by smtp7.andrew.cmu.edu (8.12.3.Beta2/8.12.3.Beta2) with ESMTP id h0DIJ3BH000569; Mon, 13 Jan 2003 13:19:03 -0500 Date: Mon, 13 Jan 2003 13:19:03 -0500 Message-Id: <200301131819.h0DIJ3BH000569@smtp7.andrew.cmu.edu> From: Lawrence Greenfield X-Mailer: BatIMail version 3.3 To: ietf-sasl@imc.org, Steve Farmer In-reply-to: Subject: Re: 16 Octet Hash References: User-Agent: SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (=?ISO-8859-4?Q?Unebigory?= =?ISO-8859-4?Q?=F2mae?=) Emacs/21.2 (i686-pc-linux-gnu) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII Sender: owner-ietf-sasl@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Date: Mon, 13 Jan 2003 12:17:42 +1100 From: Steve Farmer [...] I may be missing something simple here. I am implementing a SMTP client using SASL. However the rfc specifies a 16 octet hash as well as a 16 octet MD5 hash. Since MD4 gives a 16 octet result , is it OK to use this ? If not what should I be using for the 16 octet hash? What RFC are you talking about? What are you interested in doing? I can't think of any case where you can freely substitute one hash for another in an over-the-wire protocol, but your question leaves out too many details for me to understand what you're trying to do. Larry From owner-ietf-sasl Mon Jan 13 14:25:55 2003 Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h0DMPt023986 for ietf-sasl-bks; Mon, 13 Jan 2003 14:25:55 -0800 (PST) Received: from janus.hts.com.au (ramnet15.lnk.telstra.net [165.228.239.54]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h0DMPro23981 for ; Mon, 13 Jan 2003 14:25:54 -0800 (PST) Received: from [203.28.219.179] (pb.hts.com.au [203.28.219.179]) by janus.hts.com.au (8.11.6/8.11.6) with ESMTP id h0DMPpX32394; Tue, 14 Jan 2003 09:25:51 +1100 Posted-Date: Tue, 14 Jan 2003 09:25:51 +1100 Mime-Version: 1.0 Message-Id: In-Reply-To: <200301131819.h0DIJ3BH000569@smtp7.andrew.cmu.edu> References: <200301131819.h0DIJ3BH000569@smtp7.andrew.cmu.edu> Date: Tue, 14 Jan 2003 09:25:50 +1100 To: Lawrence Greenfield , ietf-sasl@imc.org From: Steve Farmer Subject: Re: 16 Octet Hash Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-ietf-sasl@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Hi Larry, Apologies for that, I am implementing rfc2831 and it states ... "Let KD(k, s) be H({k, ":", s}), i.e., the 16 octet hash of the string k, a colon and the string s. Let HEX(n) be the representation of the 16 octet MD5 hash" Soi I am wondering what to use for the 16 octet hash Regards Steve At 1:19 PM -0500 13/1/03, Lawrence Greenfield wrote: > Date: Mon, 13 Jan 2003 12:17:42 +1100 > From: Steve Farmer >[...] > I may be missing something simple here. I am implementing a SMTP > client using SASL. However the rfc specifies a 16 octet hash as well > as a 16 octet MD5 hash. > > Since MD4 gives a 16 octet result , is it OK to use this ? If not > what should I be using for the 16 octet hash? > >What RFC are you talking about? What are you interested in doing? > >I can't think of any case where you can freely substitute one hash for >another in an over-the-wire protocol, but your question leaves out too >many details for me to understand what you're trying to do. > >Larry -- ------------------------------------------------- Nearly all men can stand adversity, but if you want to test a man's character, give him power. -Abraham Lincoln, U.S. president (1809-1865) Support free speech; visit http://www.efa.org.au/ Heads Together Services Pty Ltd http://www.hts.com.au Email: hts@hts.com.au Tel: 612 9982 6767 Fax: 612 9981 3081 From owner-ietf-sasl Mon Jan 13 14:30:19 2003 Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h0DMUJm24061 for ietf-sasl-bks; Mon, 13 Jan 2003 14:30:19 -0800 (PST) Received: from smtp5.andrew.cmu.edu (SMTP5.andrew.cmu.edu [128.2.10.85]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h0DMUIo24056 for ; Mon, 13 Jan 2003 14:30:18 -0800 (PST) Received: from penguin.andrew.cmu.edu (PENGUIN.andrew.cmu.edu [128.2.121.100]) by smtp5.andrew.cmu.edu (8.12.3.Beta2/8.12.3.Beta2) with ESMTP id h0DMUFDX021571; Mon, 13 Jan 2003 17:30:15 -0500 Date: Mon, 13 Jan 2003 17:30:15 -0500 Message-Id: <200301132230.h0DMUFDX021571@smtp5.andrew.cmu.edu> From: Lawrence Greenfield X-Mailer: BatIMail version 3.3 To: ietf-sasl@imc.org, Steve Farmer In-reply-to: Subject: Re: 16 Octet Hash References: <200301131819.h0DIJ3BH000569@smtp7.andrew.cmu.edu> User-Agent: SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (=?ISO-8859-4?Q?Unebigory?= =?ISO-8859-4?Q?=F2mae?=) Emacs/21.2 (i686-pc-linux-gnu) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII Sender: owner-ietf-sasl@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Date: Tue, 14 Jan 2003 09:25:50 +1100 From: Steve Farmer Apologies for that, I am implementing rfc2831 and it states ... "Let KD(k, s) be H({k, ":", s}), i.e., the 16 octet hash of the string k, a colon and the string s. Let HEX(n) be the representation of the 16 octet MD5 hash" Soi I am wondering what to use for the 16 octet hash As it says, you must use MD5, as described in RFC 1321. The output of MD5 is 128-bits (16 octets) long. HMAC-MD5 is described RFC 2104. You should use exactly the hash operation that is specified. The document is a little unclear at this point. "HEX(n)" means, given n, the 128-bit output of a previous MD5 or HMAC-MD5 operation, encode it in 32 hex digits. Larry From owner-ietf-sasl Mon Jan 13 14:35:37 2003 Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h0DMZbr24191 for ietf-sasl-bks; Mon, 13 Jan 2003 14:35:37 -0800 (PST) Received: from janus.hts.com.au (ramnet15.lnk.telstra.net [165.228.239.54]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h0DMZZo24186 for ; Mon, 13 Jan 2003 14:35:35 -0800 (PST) Received: from [203.28.219.179] (pb.hts.com.au [203.28.219.179]) by janus.hts.com.au (8.11.6/8.11.6) with ESMTP id h0DMZYX32534; Tue, 14 Jan 2003 09:35:34 +1100 Posted-Date: Tue, 14 Jan 2003 09:35:34 +1100 Mime-Version: 1.0 Message-Id: In-Reply-To: <200301132230.h0DMUFDX021571@smtp5.andrew.cmu.edu> References: <200301131819.h0DIJ3BH000569@smtp7.andrew.cmu.edu> <200301132230.h0DMUFDX021571@smtp5.andrew.cmu.edu> Date: Tue, 14 Jan 2003 09:35:34 +1100 To: Lawrence Greenfield , ietf-sasl@imc.org From: Steve Farmer Subject: Re: 16 Octet Hash Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-ietf-sasl@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Larry, Thanks mate , I had assumed that but I wanted to be clear. Regards from "Down Under" Steve At 5:30 PM -0500 13/1/03, Lawrence Greenfield wrote: > Date: Tue, 14 Jan 2003 09:25:50 +1100 > From: Steve Farmer > > Apologies for that, I am implementing rfc2831 and it states ... > > "Let KD(k, s) be H({k, ":", s}), i.e., the 16 octet hash of the > string k, a colon and the string s. > > Let HEX(n) be the representation of the 16 octet MD5 hash" > > Soi I am wondering what to use for the 16 octet hash > >As it says, you must use MD5, as described in RFC 1321. The output of >MD5 is 128-bits (16 octets) long. HMAC-MD5 is described RFC 2104. > >You should use exactly the hash operation that is specified. > >The document is a little unclear at this point. "HEX(n)" means, given >n, the 128-bit output of a previous MD5 or HMAC-MD5 operation, encode >it in 32 hex digits. > >Larry -- ------------------------------------------------- Nearly all men can stand adversity, but if you want to test a man's character, give him power. -Abraham Lincoln, U.S. president (1809-1865) Support free speech; visit http://www.efa.org.au/ Heads Together Services Pty Ltd http://www.hts.com.au Email: hts@hts.com.au Tel: 612 9982 6767 Fax: 612 9981 3081 From owner-ietf-sasl Mon Jan 13 14:45:03 2003 Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h0DMj3424880 for ietf-sasl-bks; Mon, 13 Jan 2003 14:45:03 -0800 (PST) Received: from kcmso2.proxy.att.com (kcmso2.att.com [192.128.134.71]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h0DMj1o24876 for ; Mon, 13 Jan 2003 14:45:02 -0800 (PST) Received: from maillennium.att.com ([135.25.114.99]) by kcmso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h0DMixx3027255 for ; Mon, 13 Jan 2003 16:45:00 -0600 (CST) Received: from att.com (tony-ob.mt.att.com[135.91.110.11]) by maillennium.att.com (mailgw1) with SMTP id <20030113224430gw100ksdtce> (Authid: tony); Mon, 13 Jan 2003 22:44:30 +0000 Message-ID: <3E234142.5050300@att.com> Date: Mon, 13 Jan 2003 17:44:18 -0500 From: Tony Hansen User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: en-us, en MIME-Version: 1.0 CC: ietf-sasl@imc.org Subject: Re: 16 Octet Hash References: <200301131819.h0DIJ3BH000569@smtp7.andrew.cmu.edu> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-ietf-sasl@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Lawrence Greenfield wrote: > The document is a little unclear at this point. "HEX(n)" means, given > n, the 128-bit output of a previous MD5 or HMAC-MD5 operation, encode > it in 32 hex digits. ... using lower case ... Tony Hansen tony@att.com From owner-ietf-sasl Mon Jan 13 15:37:45 2003 Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h0DNbjN26110 for ietf-sasl-bks; Mon, 13 Jan 2003 15:37:45 -0800 (PST) Received: from eagle.oceana.com (eagle.oceana.com [208.17.123.12]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h0DNbio26105 for ; Mon, 13 Jan 2003 15:37:44 -0800 (PST) Received: from oceana.com (ny-kenton4d-237.buf.adelphia.net [68.66.168.237]) (authenticated bits=0) by eagle.oceana.com (8.12.7/8.12.7) with ESMTP id h0DNbMYt015234 (version=TLSv1/SSLv3 cipher=DES-CBC3-SHA bits=168 verify=NOT); Mon, 13 Jan 2003 18:37:27 -0500 Message-ID: <3E234DAD.5B136274@oceana.com> Date: Mon, 13 Jan 2003 18:37:17 -0500 From: Ken Murchison Organization: Oceana Matrix Ltd. X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en,pdf MIME-Version: 1.0 To: Steve Farmer CC: ietf-sasl@imc.org Subject: Re: 16 Octet Hash References: <200301131819.h0DIJ3BH000569@smtp7.andrew.cmu.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-ietf-sasl@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Steve Farmer wrote: > > Hi Larry, > > Apologies for that, I am implementing rfc2831 and it states ... FYI, you might want to look at the the RFC 2831bis draft, which has some corrections/clarifications: http://www.ietf.org/internet-drafts/draft-melnikov-rfc2831bis-02.txt -- Kenneth Murchison Oceana Matrix Ltd. Software Engineer 21 Princeton Place 716-662-8973 x26 Orchard Park, NY 14127 --PGP Public Key-- http://www.oceana.com/~ken/ksm.pgp From owner-ietf-sasl Wed Jan 15 04:03:01 2003 Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h0FC31x03364 for ietf-sasl-bks; Wed, 15 Jan 2003 04:03:01 -0800 (PST) Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h0FC2xo03359 for ; Wed, 15 Jan 2003 04:02:59 -0800 (PST) Received: from hobo.OpenLDAP.org (root@localhost [127.0.0.1]) by pretender.boolean.net (8.12.6/8.12.5) with ESMTP id h0FC2u0a083301 for ; Wed, 15 Jan 2003 12:02:58 GMT (envelope-from Kurt@OpenLDAP.org) Message-Id: <5.2.0.9.0.20030115125934.01f3b900@127.0.0.1> X-Sender: kurt@127.0.0.1 X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Wed, 15 Jan 2003 13:01:27 +0100 To: ietf-sasl@imc.org From: "Kurt D. Zeilenga" Subject: SASL @ IETF#56 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-ietf-sasl@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: BTW, we'll be meeting in San Francisco. If you are an editor of one of the I-Ds explicitly listed in the charter, please submit a revision as a WG I-D (e.g., draft-ietf-sasl-) for discussion as soon as possible. Kurt From owner-ietf-sasl Wed Jan 15 19:07:17 2003 Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h0G37HT03387 for ietf-sasl-bks; Wed, 15 Jan 2003 19:07:17 -0800 (PST) Received: from janus.hts.com.au (ramnet15.lnk.telstra.net [165.228.239.54]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h0G37Go03383 for ; Wed, 15 Jan 2003 19:07:16 -0800 (PST) Received: from [203.28.219.179] (pb.hts.com.au [203.28.219.179]) by janus.hts.com.au (8.11.6/8.11.6) with ESMTP id h0G37HX01173 for ; Thu, 16 Jan 2003 14:07:18 +1100 Posted-Date: Thu, 16 Jan 2003 14:07:18 +1100 Mime-Version: 1.0 Message-Id: Date: Thu, 16 Jan 2003 14:07:15 +1100 To: ietf-sasl@imc.org From: Steve Farmer Subject: Debugging SASL setup Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-ietf-sasl@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Hi all, I am implementing an SMTP client which needs to authenticate using SASL. I ma having a bit of difficulty debugging against sendmail and I was wondering if anyone could point me towards a setup which I can use to debug, perhaps IMAP or a http setup would be easier or better. Or alternatively is there a debug flag for SASL which can generate a logfile? Regards Steve Farmer -- ------------------------------------------------- Nearly all men can stand adversity, but if you want to test a man's character, give him power. -Abraham Lincoln, U.S. president (1809-1865) Support free speech; visit http://www.efa.org.au/ Heads Together Services Pty Ltd http://www.hts.com.au Email: hts@hts.com.au Tel: 612 9982 6767 Fax: 612 9981 3081 From owner-ietf-sasl Wed Jan 15 20:26:24 2003 Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h0G4QOS04967 for ietf-sasl-bks; Wed, 15 Jan 2003 20:26:24 -0800 (PST) Received: from horsey.gshapiro.net (root@horsey.gshapiro.net [64.105.95.154]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h0G4QJo04963 for ; Wed, 15 Jan 2003 20:26:23 -0800 (PST) Received: from horsey.gshapiro.net (gshapiro@localhost [IPv6:::1]) by horsey.gshapiro.net (8.12.7/8.12.7) with ESMTP id h0G4QDfi096799 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 15 Jan 2003 20:26:13 -0800 (PST) Received: (from gshapiro@localhost) by horsey.gshapiro.net (8.12.7/8.12.7/Submit) id h0G4QCmU096798; Wed, 15 Jan 2003 20:26:12 -0800 (PST) Date: Wed, 15 Jan 2003 20:26:11 -0800 From: Gregory Neil Shapiro To: Steve Farmer Cc: ietf-sasl@imc.org Subject: Re: Debugging SASL setup Message-ID: <20030116042611.GK80389@horsey.gshapiro.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.3i Sender: owner-ietf-sasl@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: > I ma having a bit of difficulty debugging against sendmail and I was > wondering if anyone could point me towards a setup which I can use to > debug, perhaps IMAP or a http setup would be easier or better. > > Or alternatively is there a debug flag for SASL which can generate a > logfile? You can try testing against test.smtp.org which offers many SASL mechanisms as well as access to the logs with a high logging level set. For more information, see: http://test.smtp.org/ From owner-ietf-sasl Wed Jan 15 20:57:22 2003 Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h0G4vMn05531 for ietf-sasl-bks; Wed, 15 Jan 2003 20:57:22 -0800 (PST) Received: from janus.hts.com.au (ramnet15.lnk.telstra.net [165.228.239.54]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h0G4vKo05527 for ; Wed, 15 Jan 2003 20:57:21 -0800 (PST) Received: from [203.28.219.179] (pb.hts.com.au [203.28.219.179]) by janus.hts.com.au (8.11.6/8.11.6) with ESMTP id h0G4vEX02622; Thu, 16 Jan 2003 15:57:15 +1100 Posted-Date: Thu, 16 Jan 2003 15:57:15 +1100 Mime-Version: 1.0 Message-Id: In-Reply-To: <20030116042611.GK80389@horsey.gshapiro.net> References: <20030116042611.GK80389@horsey.gshapiro.net> Date: Thu, 16 Jan 2003 15:57:13 +1100 To: Gregory Neil Shapiro From: Steve Farmer Subject: Re: Debugging SASL setup Cc: ietf-sasl@imc.org Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-ietf-sasl@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: HI Gregory, I have my own test SMTP server set up with SASL , I was really trying to find out how I can generate a detailed log so that I can figure out where my client auth is failing. Any pointers welcome ! Regards Steve At 8:26 PM -0800 15/1/03, Gregory Neil Shapiro wrote: > > I ma having a bit of difficulty debugging against sendmail and I was >> wondering if anyone could point me towards a setup which I can use to >> debug, perhaps IMAP or a http setup would be easier or better. >> >> Or alternatively is there a debug flag for SASL which can generate a >> logfile? > >You can try testing against test.smtp.org which offers many SASL >mechanisms as well as access to the logs with a high logging level >set. For more information, see: > >http://test.smtp.org/ -- ------------------------------------------------- Nearly all men can stand adversity, but if you want to test a man's character, give him power. -Abraham Lincoln, U.S. president (1809-1865) Support free speech; visit http://www.efa.org.au/ Heads Together Services Pty Ltd http://www.hts.com.au Email: hts@hts.com.au Tel: 612 9982 6767 Fax: 612 9981 3081 From owner-ietf-sasl Thu Jan 16 08:04:42 2003 Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h0GG4gw29492 for ietf-sasl-bks; Thu, 16 Jan 2003 08:04:42 -0800 (PST) Received: from ginger.cmf.nrl.navy.mil (ginger.cmf.nrl.navy.mil [134.207.10.161]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h0GG4eo29487 for ; Thu, 16 Jan 2003 08:04:40 -0800 (PST) Received: from cmf.nrl.navy.mil (elvis.cmf.nrl.navy.mil [134.207.10.38]) (authenticated bits=0) by ginger.cmf.nrl.navy.mil (8.12.5/8.12.5) with ESMTP id h0GG4T8H004095; Thu, 16 Jan 2003 11:04:33 -0500 (EST) Message-Id: <200301161604.h0GG4T8H004095@ginger.cmf.nrl.navy.mil> To: Steve Farmer cc: ietf-sasl@imc.org Subject: Re: Debugging SASL setup In-reply-to: Your message of "Thu, 16 Jan 2003 14:07:15 +1100." X-Face: "Evs"_GpJ]],xS)b$T2#V&{KfP_i2`TlPrY$Iv9+TQ!6+`~+l)#7I)0xr1>4hfd{#0B4 WIn3jU;bql;{2Uq%zw5bF4?%F&&j8@KaT?#vBGk}u07<+6/`.F-3_GA@6Bq5gN9\+s;_d gD\SW #]iN_U0 KUmOR.P<|um5yPkEpSD@*e` Date: Thu, 16 Jan 2003 11:04:29 -0500 From: Ken Hornstein X-Spam-Score: hits=0 () User Authenticated X-Virus-Scanned: NAI Completed X-Scanned-By: MIMEDefang 2.24 (www . roaringpenguin . com / mimedefang) Sender: owner-ietf-sasl@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: >I am implementing an SMTP client which needs to authenticate using SASL. > >I ma having a bit of difficulty debugging against sendmail and I was >wondering if anyone could point me towards a setup which I can use to >debug, perhaps IMAP or a http setup would be easier or better. If you're using the Cyrus-SASL library, I've found that the sample applications (sample-client/sample-server) are pretty good to perform debugging. At least they helped me. --Ken From owner-ietf-sasl Thu Jan 9 06:27:42 2003 Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h09ERgn19998 for ietf-sasl-bks; Thu, 9 Jan 2003 06:27:42 -0800 (PST) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h09ERfo19994 for ; Thu, 9 Jan 2003 06:27:41 -0800 (PST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11022; Thu, 9 Jan 2003 09:24:27 -0500 (EST) Message-Id: <200301091424.JAA11022@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: ietf-sasl@imc.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-sasl-anon-00.txt Date: Thu, 09 Jan 2003 09:24:27 -0500 Sender: owner-ietf-sasl@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Simple Authentication and Security Layer Working Group of the IETF. Title : The Anonymous SASL Mechanism Author(s) : K. Zeilenga Filename : draft-ietf-sasl-anon-00.txt Pages : 8 Date : 2003-1-8 It is common practice on the Internet to permit anonymous access to various services. Traditionally, this has been done with a plain text password mechanism using 'anonymous' as the user name and optional trace information, such as an email address, as the password. As plaintext login commands are not permitted in new IETF protocols, a new way to provide anonymous login is needed within the context of the Simple Authentication and Security Layer (SASL) framework. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-sasl-anon-00.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-sasl-anon-00.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-sasl-anon-00.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: <2003-1-9092500.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-sasl-anon-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-sasl-anon-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-1-9092500.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-ietf-sasl Fri Jan 10 11:53:54 2003 Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h0AJrsT19356 for ietf-sasl-bks; Fri, 10 Jan 2003 11:53:54 -0800 (PST) Received: from luminous.mit.edu (LUMINOUS.MIT.EDU [18.101.1.61]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h0AJrqo19352 for ; Fri, 10 Jan 2003 11:53:52 -0800 (PST) Received: by luminous.mit.edu (Postfix, from userid 1000) id 3EB8B7680A; Fri, 10 Jan 2003 14:53:12 -0500 (EST) To: ietf-sasl@imc.org Subject: [Internet-Drafts@ietf.org] I-D ACTION:draft-josefsson-sasl-kerberos5-00.txt From: Sam Hartman Date: Fri, 10 Jan 2003 14:53:11 -0500 Message-ID: <87znq893yw.fsf@luminous.mit.edu> Lines: 112 User-Agent: Gnus/5.090006 (Oort Gnus v0.06) Emacs/21.1 (i386-debian-linux-gnu) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Sender: owner-ietf-sasl@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: --=-=-= I understand this is out of scope for our working group, but it seems that forwarding the initial announcement is reasonable. --=-=-= Content-Type: message/rfc822 Content-Disposition: inline Return-Path: Received: from solipsist-nation ([unix socket]) by solipsist-nation (Cyrus v2.1.5-Debian2.1.5-1) with LMTP; Fri, 10 Jan 2003 13:55:55 -0500 X-Sieve: CMU Sieve 2.2 Return-Path: Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by suchdamage.org (Postfix) with ESMTP id 1BC19131E1 for ; Fri, 10 Jan 2003 13:55:55 -0500 (EST) Received: from atalanta.ctd.anl.gov (atalanta.ctd.anl.gov [146.137.194.4]) by fort-point-station.mit.edu (8.9.2/8.9.2) with ESMTP id NAA12883; Fri, 10 Jan 2003 13:55:52 -0500 (EST) Received: (from majordom@localhost) by atalanta.ctd.anl.gov (8.9.1a/8.9.1) id MAA03022 for ietf-krb-wg-outgoing; Fri, 10 Jan 2003 12:52:41 -0600 (CST) Received: from hermes.ctd.anl.gov (localhost [127.0.0.1]) by atalanta.ctd.anl.gov (8.9.1a/8.9.1) with ESMTP id MAA03016 for ; Fri, 10 Jan 2003 12:52:40 -0600 (CST) Received: from hermes.ctd.anl.gov (localhost [127.0.0.1]) by hermes.ctd.anl.gov (8.9.1a/8.9.1) with ESMTP id MAA12809 for ; Fri, 10 Jan 2003 12:52:38 -0600 (CST) Received: from mailrelay.anl.gov (mailrelay.anl.gov [130.202.101.22]) by hermes.ctd.anl.gov (8.9.1a/8.9.1) with ESMTP id MAA12806 for ; Fri, 10 Jan 2003 12:52:38 -0600 (CST) Received: from localhost.localdomain (localhost [127.0.0.1]) by localhost.ctd.anl.gov (Postfix) with ESMTP id 43A605F0DAC; Fri, 10 Jan 2003 12:52:38 -0600 (CST) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by mailrelay.anl.gov (Postfix) with ESMTP id 712555F0D91 for ; Fri, 10 Jan 2003 12:52:37 -0600 (CST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10890; Fri, 10 Jan 2003 13:49:18 -0500 (EST) Message-Id: <200301101849.NAA10890@ietf.org> To: IETF-Announce: ; Cc: ietf-krb-wg@anl.gov From: Internet-Drafts@ietf.org Reply-To: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-josefsson-sasl-kerberos5-00.txt Date: Fri, 10 Jan 2003 13:49:18 -0500 X-Spam-Level: **** Sender: owner-ietf-krb-wg@achilles.ctd.anl.gov Precedence: bulk X-Spam-Status: No, hits=0.8 required=5.0 tests=NO_REAL_NAME,TO_MALFORMED,EXCUSE_6 version=2.20 X-Spam-Level: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===-=-=" --===-=-= A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : A Kerberos 5 SASL Mechanism Author(s) : S. Josefsson Filename : draft-josefsson-sasl-kerberos5-00.txt Pages : 11 Date : 2003-1-9 This document specifies a Simple Authentication and Security Layer (SASL) [3] mechanism for Kerberos 5 Client/Server Authentication [1], with optional initial Authentication Service (AS) and/or Ticket-Granting-Service (TGS) exchanges. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-josefsson-sasl-kerberos5-00.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-josefsson-sasl-kerberos5-00.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-josefsson-sasl-kerberos5-00.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. --===-=-= Content-Type: multipart/alternative; boundary="====-=-=" --====-=-= Content-Type: message/external-body; access-type=mail-server Content-Type: text/plain Content-ID: <2003-1-10140627.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-josefsson-sasl-kerberos5-00.txt --====-=-= Content-Type: message/external-body; name=draft-josefsson-sasl-kerberos5-00.txt; access-type=anon-ftp Content-Type: text/plain Content-ID: <2003-1-10140627.I-D@ietf.org> --====-=-=-- --===-=-=-- --=-=-=-- From owner-ietf-sasl Sun Jan 12 17:17:48 2003 Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h0D1HmB15245 for ietf-sasl-bks; Sun, 12 Jan 2003 17:17:48 -0800 (PST) Received: from janus.hts.com.au (ramnet15.lnk.telstra.net [165.228.239.54]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h0D1Hio15241 for ; Sun, 12 Jan 2003 17:17:46 -0800 (PST) Received: from [203.28.219.179] (pb.hts.com.au [203.28.219.179]) by janus.hts.com.au (8.11.6/8.11.6) with ESMTP id h0D1HiX19761 for ; Mon, 13 Jan 2003 12:17:45 +1100 Posted-Date: Mon, 13 Jan 2003 12:17:45 +1100 Mime-Version: 1.0 Message-Id: Date: Mon, 13 Jan 2003 12:17:42 +1100 To: ietf-sasl@imc.org From: Steve Farmer Subject: 16 Octet Hash Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-ietf-sasl@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Hi all, I may be missing something simple here. I am implementing a SMTP client using SASL. However the rfc specifies a 16 octet hash as well as a 16 octet MD5 hash. Since MD4 gives a 16 octet result , is it OK to use this ? If not what should I be using for the 16 octet hash? Regards Steve Farmer -- ------------------------------------------------- Nearly all men can stand adversity, but if you want to test a man's character, give him power. -Abraham Lincoln, U.S. president (1809-1865) Support free speech; visit http://www.efa.org.au/ Heads Together Services Pty Ltd http://www.hts.com.au Email: hts@hts.com.au Tel: 612 9982 6767 Fax: 612 9981 3081 From owner-ietf-sasl Mon Jan 13 10:19:11 2003 Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h0DIJBl18026 for ietf-sasl-bks; Mon, 13 Jan 2003 10:19:11 -0800 (PST) Received: from smtp7.andrew.cmu.edu (SMTP7.andrew.cmu.edu [128.2.10.87]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h0DIJAo18022 for ; Mon, 13 Jan 2003 10:19:10 -0800 (PST) Received: from penguin.andrew.cmu.edu (PENGUIN.andrew.cmu.edu [128.2.121.100]) by smtp7.andrew.cmu.edu (8.12.3.Beta2/8.12.3.Beta2) with ESMTP id h0DIJ3BH000569; Mon, 13 Jan 2003 13:19:03 -0500 Date: Mon, 13 Jan 2003 13:19:03 -0500 Message-Id: <200301131819.h0DIJ3BH000569@smtp7.andrew.cmu.edu> From: Lawrence Greenfield X-Mailer: BatIMail version 3.3 To: ietf-sasl@imc.org, Steve Farmer In-reply-to: Subject: Re: 16 Octet Hash References: User-Agent: SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (=?ISO-8859-4?Q?Unebigory?= =?ISO-8859-4?Q?=F2mae?=) Emacs/21.2 (i686-pc-linux-gnu) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII Sender: owner-ietf-sasl@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Date: Mon, 13 Jan 2003 12:17:42 +1100 From: Steve Farmer [...] I may be missing something simple here. I am implementing a SMTP client using SASL. However the rfc specifies a 16 octet hash as well as a 16 octet MD5 hash. Since MD4 gives a 16 octet result , is it OK to use this ? If not what should I be using for the 16 octet hash? What RFC are you talking about? What are you interested in doing? I can't think of any case where you can freely substitute one hash for another in an over-the-wire protocol, but your question leaves out too many details for me to understand what you're trying to do. Larry From owner-ietf-sasl Mon Jan 13 14:25:55 2003 Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h0DMPt023986 for ietf-sasl-bks; Mon, 13 Jan 2003 14:25:55 -0800 (PST) Received: from janus.hts.com.au (ramnet15.lnk.telstra.net [165.228.239.54]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h0DMPro23981 for ; Mon, 13 Jan 2003 14:25:54 -0800 (PST) Received: from [203.28.219.179] (pb.hts.com.au [203.28.219.179]) by janus.hts.com.au (8.11.6/8.11.6) with ESMTP id h0DMPpX32394; Tue, 14 Jan 2003 09:25:51 +1100 Posted-Date: Tue, 14 Jan 2003 09:25:51 +1100 Mime-Version: 1.0 Message-Id: In-Reply-To: <200301131819.h0DIJ3BH000569@smtp7.andrew.cmu.edu> References: <200301131819.h0DIJ3BH000569@smtp7.andrew.cmu.edu> Date: Tue, 14 Jan 2003 09:25:50 +1100 To: Lawrence Greenfield , ietf-sasl@imc.org From: Steve Farmer Subject: Re: 16 Octet Hash Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-ietf-sasl@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Hi Larry, Apologies for that, I am implementing rfc2831 and it states ... "Let KD(k, s) be H({k, ":", s}), i.e., the 16 octet hash of the string k, a colon and the string s. Let HEX(n) be the representation of the 16 octet MD5 hash" Soi I am wondering what to use for the 16 octet hash Regards Steve At 1:19 PM -0500 13/1/03, Lawrence Greenfield wrote: > Date: Mon, 13 Jan 2003 12:17:42 +1100 > From: Steve Farmer >[...] > I may be missing something simple here. I am implementing a SMTP > client using SASL. However the rfc specifies a 16 octet hash as well > as a 16 octet MD5 hash. > > Since MD4 gives a 16 octet result , is it OK to use this ? If not > what should I be using for the 16 octet hash? > >What RFC are you talking about? What are you interested in doing? > >I can't think of any case where you can freely substitute one hash for >another in an over-the-wire protocol, but your question leaves out too >many details for me to understand what you're trying to do. > >Larry -- ------------------------------------------------- Nearly all men can stand adversity, but if you want to test a man's character, give him power. -Abraham Lincoln, U.S. president (1809-1865) Support free speech; visit http://www.efa.org.au/ Heads Together Services Pty Ltd http://www.hts.com.au Email: hts@hts.com.au Tel: 612 9982 6767 Fax: 612 9981 3081 From owner-ietf-sasl Mon Jan 13 14:30:19 2003 Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h0DMUJm24061 for ietf-sasl-bks; Mon, 13 Jan 2003 14:30:19 -0800 (PST) Received: from smtp5.andrew.cmu.edu (SMTP5.andrew.cmu.edu [128.2.10.85]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h0DMUIo24056 for ; Mon, 13 Jan 2003 14:30:18 -0800 (PST) Received: from penguin.andrew.cmu.edu (PENGUIN.andrew.cmu.edu [128.2.121.100]) by smtp5.andrew.cmu.edu (8.12.3.Beta2/8.12.3.Beta2) with ESMTP id h0DMUFDX021571; Mon, 13 Jan 2003 17:30:15 -0500 Date: Mon, 13 Jan 2003 17:30:15 -0500 Message-Id: <200301132230.h0DMUFDX021571@smtp5.andrew.cmu.edu> From: Lawrence Greenfield X-Mailer: BatIMail version 3.3 To: ietf-sasl@imc.org, Steve Farmer In-reply-to: Subject: Re: 16 Octet Hash References: <200301131819.h0DIJ3BH000569@smtp7.andrew.cmu.edu> User-Agent: SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (=?ISO-8859-4?Q?Unebigory?= =?ISO-8859-4?Q?=F2mae?=) Emacs/21.2 (i686-pc-linux-gnu) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII Sender: owner-ietf-sasl@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Date: Tue, 14 Jan 2003 09:25:50 +1100 From: Steve Farmer Apologies for that, I am implementing rfc2831 and it states ... "Let KD(k, s) be H({k, ":", s}), i.e., the 16 octet hash of the string k, a colon and the string s. Let HEX(n) be the representation of the 16 octet MD5 hash" Soi I am wondering what to use for the 16 octet hash As it says, you must use MD5, as described in RFC 1321. The output of MD5 is 128-bits (16 octets) long. HMAC-MD5 is described RFC 2104. You should use exactly the hash operation that is specified. The document is a little unclear at this point. "HEX(n)" means, given n, the 128-bit output of a previous MD5 or HMAC-MD5 operation, encode it in 32 hex digits. Larry From owner-ietf-sasl Mon Jan 13 14:35:37 2003 Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h0DMZbr24191 for ietf-sasl-bks; Mon, 13 Jan 2003 14:35:37 -0800 (PST) Received: from janus.hts.com.au (ramnet15.lnk.telstra.net [165.228.239.54]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h0DMZZo24186 for ; Mon, 13 Jan 2003 14:35:35 -0800 (PST) Received: from [203.28.219.179] (pb.hts.com.au [203.28.219.179]) by janus.hts.com.au (8.11.6/8.11.6) with ESMTP id h0DMZYX32534; Tue, 14 Jan 2003 09:35:34 +1100 Posted-Date: Tue, 14 Jan 2003 09:35:34 +1100 Mime-Version: 1.0 Message-Id: In-Reply-To: <200301132230.h0DMUFDX021571@smtp5.andrew.cmu.edu> References: <200301131819.h0DIJ3BH000569@smtp7.andrew.cmu.edu> <200301132230.h0DMUFDX021571@smtp5.andrew.cmu.edu> Date: Tue, 14 Jan 2003 09:35:34 +1100 To: Lawrence Greenfield , ietf-sasl@imc.org From: Steve Farmer Subject: Re: 16 Octet Hash Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-ietf-sasl@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Larry, Thanks mate , I had assumed that but I wanted to be clear. Regards from "Down Under" Steve At 5:30 PM -0500 13/1/03, Lawrence Greenfield wrote: > Date: Tue, 14 Jan 2003 09:25:50 +1100 > From: Steve Farmer > > Apologies for that, I am implementing rfc2831 and it states ... > > "Let KD(k, s) be H({k, ":", s}), i.e., the 16 octet hash of the > string k, a colon and the string s. > > Let HEX(n) be the representation of the 16 octet MD5 hash" > > Soi I am wondering what to use for the 16 octet hash > >As it says, you must use MD5, as described in RFC 1321. The output of >MD5 is 128-bits (16 octets) long. HMAC-MD5 is described RFC 2104. > >You should use exactly the hash operation that is specified. > >The document is a little unclear at this point. "HEX(n)" means, given >n, the 128-bit output of a previous MD5 or HMAC-MD5 operation, encode >it in 32 hex digits. > >Larry -- ------------------------------------------------- Nearly all men can stand adversity, but if you want to test a man's character, give him power. -Abraham Lincoln, U.S. president (1809-1865) Support free speech; visit http://www.efa.org.au/ Heads Together Services Pty Ltd http://www.hts.com.au Email: hts@hts.com.au Tel: 612 9982 6767 Fax: 612 9981 3081 From owner-ietf-sasl Mon Jan 13 14:45:03 2003 Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h0DMj3424880 for ietf-sasl-bks; Mon, 13 Jan 2003 14:45:03 -0800 (PST) Received: from kcmso2.proxy.att.com (kcmso2.att.com [192.128.134.71]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h0DMj1o24876 for ; Mon, 13 Jan 2003 14:45:02 -0800 (PST) Received: from maillennium.att.com ([135.25.114.99]) by kcmso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h0DMixx3027255 for ; Mon, 13 Jan 2003 16:45:00 -0600 (CST) Received: from att.com (tony-ob.mt.att.com[135.91.110.11]) by maillennium.att.com (mailgw1) with SMTP id <20030113224430gw100ksdtce> (Authid: tony); Mon, 13 Jan 2003 22:44:30 +0000 Message-ID: <3E234142.5050300@att.com> Date: Mon, 13 Jan 2003 17:44:18 -0500 From: Tony Hansen User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: en-us, en MIME-Version: 1.0 CC: ietf-sasl@imc.org Subject: Re: 16 Octet Hash References: <200301131819.h0DIJ3BH000569@smtp7.andrew.cmu.edu> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-ietf-sasl@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Lawrence Greenfield wrote: > The document is a little unclear at this point. "HEX(n)" means, given > n, the 128-bit output of a previous MD5 or HMAC-MD5 operation, encode > it in 32 hex digits. ... using lower case ... Tony Hansen tony@att.com From owner-ietf-sasl Mon Jan 13 15:37:45 2003 Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h0DNbjN26110 for ietf-sasl-bks; Mon, 13 Jan 2003 15:37:45 -0800 (PST) Received: from eagle.oceana.com (eagle.oceana.com [208.17.123.12]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h0DNbio26105 for ; Mon, 13 Jan 2003 15:37:44 -0800 (PST) Received: from oceana.com (ny-kenton4d-237.buf.adelphia.net [68.66.168.237]) (authenticated bits=0) by eagle.oceana.com (8.12.7/8.12.7) with ESMTP id h0DNbMYt015234 (version=TLSv1/SSLv3 cipher=DES-CBC3-SHA bits=168 verify=NOT); Mon, 13 Jan 2003 18:37:27 -0500 Message-ID: <3E234DAD.5B136274@oceana.com> Date: Mon, 13 Jan 2003 18:37:17 -0500 From: Ken Murchison Organization: Oceana Matrix Ltd. X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en,pdf MIME-Version: 1.0 To: Steve Farmer CC: ietf-sasl@imc.org Subject: Re: 16 Octet Hash References: <200301131819.h0DIJ3BH000569@smtp7.andrew.cmu.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-ietf-sasl@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Steve Farmer wrote: > > Hi Larry, > > Apologies for that, I am implementing rfc2831 and it states ... FYI, you might want to look at the the RFC 2831bis draft, which has some corrections/clarifications: http://www.ietf.org/internet-drafts/draft-melnikov-rfc2831bis-02.txt -- Kenneth Murchison Oceana Matrix Ltd. Software Engineer 21 Princeton Place 716-662-8973 x26 Orchard Park, NY 14127 --PGP Public Key-- http://www.oceana.com/~ken/ksm.pgp From owner-ietf-sasl Wed Jan 15 04:03:01 2003 Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h0FC31x03364 for ietf-sasl-bks; Wed, 15 Jan 2003 04:03:01 -0800 (PST) Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h0FC2xo03359 for ; Wed, 15 Jan 2003 04:02:59 -0800 (PST) Received: from hobo.OpenLDAP.org (root@localhost [127.0.0.1]) by pretender.boolean.net (8.12.6/8.12.5) with ESMTP id h0FC2u0a083301 for ; Wed, 15 Jan 2003 12:02:58 GMT (envelope-from Kurt@OpenLDAP.org) Message-Id: <5.2.0.9.0.20030115125934.01f3b900@127.0.0.1> X-Sender: kurt@127.0.0.1 X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Wed, 15 Jan 2003 13:01:27 +0100 To: ietf-sasl@imc.org From: "Kurt D. Zeilenga" Subject: SASL @ IETF#56 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-ietf-sasl@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: BTW, we'll be meeting in San Francisco. If you are an editor of one of the I-Ds explicitly listed in the charter, please submit a revision as a WG I-D (e.g., draft-ietf-sasl-) for discussion as soon as possible. Kurt From owner-ietf-sasl Wed Jan 15 19:07:17 2003 Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h0G37HT03387 for ietf-sasl-bks; Wed, 15 Jan 2003 19:07:17 -0800 (PST) Received: from janus.hts.com.au (ramnet15.lnk.telstra.net [165.228.239.54]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h0G37Go03383 for ; Wed, 15 Jan 2003 19:07:16 -0800 (PST) Received: from [203.28.219.179] (pb.hts.com.au [203.28.219.179]) by janus.hts.com.au (8.11.6/8.11.6) with ESMTP id h0G37HX01173 for ; Thu, 16 Jan 2003 14:07:18 +1100 Posted-Date: Thu, 16 Jan 2003 14:07:18 +1100 Mime-Version: 1.0 Message-Id: Date: Thu, 16 Jan 2003 14:07:15 +1100 To: ietf-sasl@imc.org From: Steve Farmer Subject: Debugging SASL setup Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-ietf-sasl@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Hi all, I am implementing an SMTP client which needs to authenticate using SASL. I ma having a bit of difficulty debugging against sendmail and I was wondering if anyone could point me towards a setup which I can use to debug, perhaps IMAP or a http setup would be easier or better. Or alternatively is there a debug flag for SASL which can generate a logfile? Regards Steve Farmer -- ------------------------------------------------- Nearly all men can stand adversity, but if you want to test a man's character, give him power. -Abraham Lincoln, U.S. president (1809-1865) Support free speech; visit http://www.efa.org.au/ Heads Together Services Pty Ltd http://www.hts.com.au Email: hts@hts.com.au Tel: 612 9982 6767 Fax: 612 9981 3081 From owner-ietf-sasl Wed Jan 15 20:26:24 2003 Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h0G4QOS04967 for ietf-sasl-bks; Wed, 15 Jan 2003 20:26:24 -0800 (PST) Received: from horsey.gshapiro.net (root@horsey.gshapiro.net [64.105.95.154]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h0G4QJo04963 for ; Wed, 15 Jan 2003 20:26:23 -0800 (PST) Received: from horsey.gshapiro.net (gshapiro@localhost [IPv6:::1]) by horsey.gshapiro.net (8.12.7/8.12.7) with ESMTP id h0G4QDfi096799 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 15 Jan 2003 20:26:13 -0800 (PST) Received: (from gshapiro@localhost) by horsey.gshapiro.net (8.12.7/8.12.7/Submit) id h0G4QCmU096798; Wed, 15 Jan 2003 20:26:12 -0800 (PST) Date: Wed, 15 Jan 2003 20:26:11 -0800 From: Gregory Neil Shapiro To: Steve Farmer Cc: ietf-sasl@imc.org Subject: Re: Debugging SASL setup Message-ID: <20030116042611.GK80389@horsey.gshapiro.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.3i Sender: owner-ietf-sasl@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: > I ma having a bit of difficulty debugging against sendmail and I was > wondering if anyone could point me towards a setup which I can use to > debug, perhaps IMAP or a http setup would be easier or better. > > Or alternatively is there a debug flag for SASL which can generate a > logfile? You can try testing against test.smtp.org which offers many SASL mechanisms as well as access to the logs with a high logging level set. For more information, see: http://test.smtp.org/ From owner-ietf-sasl Wed Jan 15 20:57:22 2003 Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h0G4vMn05531 for ietf-sasl-bks; Wed, 15 Jan 2003 20:57:22 -0800 (PST) Received: from janus.hts.com.au (ramnet15.lnk.telstra.net [165.228.239.54]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h0G4vKo05527 for ; Wed, 15 Jan 2003 20:57:21 -0800 (PST) Received: from [203.28.219.179] (pb.hts.com.au [203.28.219.179]) by janus.hts.com.au (8.11.6/8.11.6) with ESMTP id h0G4vEX02622; Thu, 16 Jan 2003 15:57:15 +1100 Posted-Date: Thu, 16 Jan 2003 15:57:15 +1100 Mime-Version: 1.0 Message-Id: In-Reply-To: <20030116042611.GK80389@horsey.gshapiro.net> References: <20030116042611.GK80389@horsey.gshapiro.net> Date: Thu, 16 Jan 2003 15:57:13 +1100 To: Gregory Neil Shapiro From: Steve Farmer Subject: Re: Debugging SASL setup Cc: ietf-sasl@imc.org Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-ietf-sasl@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: HI Gregory, I have my own test SMTP server set up with SASL , I was really trying to find out how I can generate a detailed log so that I can figure out where my client auth is failing. Any pointers welcome ! Regards Steve At 8:26 PM -0800 15/1/03, Gregory Neil Shapiro wrote: > > I ma having a bit of difficulty debugging against sendmail and I was >> wondering if anyone could point me towards a setup which I can use to >> debug, perhaps IMAP or a http setup would be easier or better. >> >> Or alternatively is there a debug flag for SASL which can generate a >> logfile? > >You can try testing against test.smtp.org which offers many SASL >mechanisms as well as access to the logs with a high logging level >set. For more information, see: > >http://test.smtp.org/ -- ------------------------------------------------- Nearly all men can stand adversity, but if you want to test a man's character, give him power. -Abraham Lincoln, U.S. president (1809-1865) Support free speech; visit http://www.efa.org.au/ Heads Together Services Pty Ltd http://www.hts.com.au Email: hts@hts.com.au Tel: 612 9982 6767 Fax: 612 9981 3081 From owner-ietf-sasl Thu Jan 16 08:04:42 2003 Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h0GG4gw29492 for ietf-sasl-bks; Thu, 16 Jan 2003 08:04:42 -0800 (PST) Received: from ginger.cmf.nrl.navy.mil (ginger.cmf.nrl.navy.mil [134.207.10.161]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h0GG4eo29487 for ; Thu, 16 Jan 2003 08:04:40 -0800 (PST) Received: from cmf.nrl.navy.mil (elvis.cmf.nrl.navy.mil [134.207.10.38]) (authenticated bits=0) by ginger.cmf.nrl.navy.mil (8.12.5/8.12.5) with ESMTP id h0GG4T8H004095; Thu, 16 Jan 2003 11:04:33 -0500 (EST) Message-Id: <200301161604.h0GG4T8H004095@ginger.cmf.nrl.navy.mil> To: Steve Farmer cc: ietf-sasl@imc.org Subject: Re: Debugging SASL setup In-reply-to: Your message of "Thu, 16 Jan 2003 14:07:15 +1100." X-Face: "Evs"_GpJ]],xS)b$T2#V&{KfP_i2`TlPrY$Iv9+TQ!6+`~+l)#7I)0xr1>4hfd{#0B4 WIn3jU;bql;{2Uq%zw5bF4?%F&&j8@KaT?#vBGk}u07<+6/`.F-3_GA@6Bq5gN9\+s;_d gD\SW #]iN_U0 KUmOR.P<|um5yPkEpSD@*e` Date: Thu, 16 Jan 2003 11:04:29 -0500 From: Ken Hornstein X-Spam-Score: hits=0 () User Authenticated X-Virus-Scanned: NAI Completed X-Scanned-By: MIMEDefang 2.24 (www . roaringpenguin . com / mimedefang) Sender: owner-ietf-sasl@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: >I am implementing an SMTP client which needs to authenticate using SASL. > >I ma having a bit of difficulty debugging against sendmail and I was >wondering if anyone could point me towards a setup which I can use to >debug, perhaps IMAP or a http setup would be easier or better. If you're using the Cyrus-SASL library, I've found that the sample applications (sample-client/sample-server) are pretty good to perform debugging. At least they helped me. --Ken Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h0GG4gw29492 for ietf-sasl-bks; Thu, 16 Jan 2003 08:04:42 -0800 (PST) Received: from ginger.cmf.nrl.navy.mil (ginger.cmf.nrl.navy.mil [134.207.10.161]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h0GG4eo29487 for ; Thu, 16 Jan 2003 08:04:40 -0800 (PST) Received: from cmf.nrl.navy.mil (elvis.cmf.nrl.navy.mil [134.207.10.38]) (authenticated bits=0) by ginger.cmf.nrl.navy.mil (8.12.5/8.12.5) with ESMTP id h0GG4T8H004095; Thu, 16 Jan 2003 11:04:33 -0500 (EST) Message-Id: <200301161604.h0GG4T8H004095@ginger.cmf.nrl.navy.mil> To: Steve Farmer cc: ietf-sasl@imc.org Subject: Re: Debugging SASL setup In-reply-to: Your message of "Thu, 16 Jan 2003 14:07:15 +1100." X-Face: "Evs"_GpJ]],xS)b$T2#V&{KfP_i2`TlPrY$Iv9+TQ!6+`~+l)#7I)0xr1>4hfd{#0B4 WIn3jU;bql;{2Uq%zw5bF4?%F&&j8@KaT?#vBGk}u07<+6/`.F-3_GA@6Bq5gN9\+s;_d gD\SW #]iN_U0 KUmOR.P<|um5yPkEpSD@*e` Date: Thu, 16 Jan 2003 11:04:29 -0500 From: Ken Hornstein X-Spam-Score: hits=0 () User Authenticated X-Virus-Scanned: NAI Completed X-Scanned-By: MIMEDefang 2.24 (www . roaringpenguin . com / mimedefang) Sender: owner-ietf-sasl@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: >I am implementing an SMTP client which needs to authenticate using SASL. > >I ma having a bit of difficulty debugging against sendmail and I was >wondering if anyone could point me towards a setup which I can use to >debug, perhaps IMAP or a http setup would be easier or better. If you're using the Cyrus-SASL library, I've found that the sample applications (sample-client/sample-server) are pretty good to perform debugging. At least they helped me. --Ken Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h0G4vMn05531 for ietf-sasl-bks; Wed, 15 Jan 2003 20:57:22 -0800 (PST) Received: from janus.hts.com.au (ramnet15.lnk.telstra.net [165.228.239.54]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h0G4vKo05527 for ; Wed, 15 Jan 2003 20:57:21 -0800 (PST) Received: from [203.28.219.179] (pb.hts.com.au [203.28.219.179]) by janus.hts.com.au (8.11.6/8.11.6) with ESMTP id h0G4vEX02622; Thu, 16 Jan 2003 15:57:15 +1100 Posted-Date: Thu, 16 Jan 2003 15:57:15 +1100 Mime-Version: 1.0 Message-Id: In-Reply-To: <20030116042611.GK80389@horsey.gshapiro.net> References: <20030116042611.GK80389@horsey.gshapiro.net> Date: Thu, 16 Jan 2003 15:57:13 +1100 To: Gregory Neil Shapiro From: Steve Farmer Subject: Re: Debugging SASL setup Cc: ietf-sasl@imc.org Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-ietf-sasl@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: HI Gregory, I have my own test SMTP server set up with SASL , I was really trying to find out how I can generate a detailed log so that I can figure out where my client auth is failing. Any pointers welcome ! Regards Steve At 8:26 PM -0800 15/1/03, Gregory Neil Shapiro wrote: > > I ma having a bit of difficulty debugging against sendmail and I was >> wondering if anyone could point me towards a setup which I can use to >> debug, perhaps IMAP or a http setup would be easier or better. >> >> Or alternatively is there a debug flag for SASL which can generate a >> logfile? > >You can try testing against test.smtp.org which offers many SASL >mechanisms as well as access to the logs with a high logging level >set. For more information, see: > >http://test.smtp.org/ -- ------------------------------------------------- Nearly all men can stand adversity, but if you want to test a man's character, give him power. -Abraham Lincoln, U.S. president (1809-1865) Support free speech; visit http://www.efa.org.au/ Heads Together Services Pty Ltd http://www.hts.com.au Email: hts@hts.com.au Tel: 612 9982 6767 Fax: 612 9981 3081 Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h0G4QOS04967 for ietf-sasl-bks; Wed, 15 Jan 2003 20:26:24 -0800 (PST) Received: from horsey.gshapiro.net (root@horsey.gshapiro.net [64.105.95.154]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h0G4QJo04963 for ; Wed, 15 Jan 2003 20:26:23 -0800 (PST) Received: from horsey.gshapiro.net (gshapiro@localhost [IPv6:::1]) by horsey.gshapiro.net (8.12.7/8.12.7) with ESMTP id h0G4QDfi096799 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 15 Jan 2003 20:26:13 -0800 (PST) Received: (from gshapiro@localhost) by horsey.gshapiro.net (8.12.7/8.12.7/Submit) id h0G4QCmU096798; Wed, 15 Jan 2003 20:26:12 -0800 (PST) Date: Wed, 15 Jan 2003 20:26:11 -0800 From: Gregory Neil Shapiro To: Steve Farmer Cc: ietf-sasl@imc.org Subject: Re: Debugging SASL setup Message-ID: <20030116042611.GK80389@horsey.gshapiro.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.3i Sender: owner-ietf-sasl@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: > I ma having a bit of difficulty debugging against sendmail and I was > wondering if anyone could point me towards a setup which I can use to > debug, perhaps IMAP or a http setup would be easier or better. > > Or alternatively is there a debug flag for SASL which can generate a > logfile? You can try testing against test.smtp.org which offers many SASL mechanisms as well as access to the logs with a high logging level set. For more information, see: http://test.smtp.org/ Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h0G37HT03387 for ietf-sasl-bks; Wed, 15 Jan 2003 19:07:17 -0800 (PST) Received: from janus.hts.com.au (ramnet15.lnk.telstra.net [165.228.239.54]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h0G37Go03383 for ; Wed, 15 Jan 2003 19:07:16 -0800 (PST) Received: from [203.28.219.179] (pb.hts.com.au [203.28.219.179]) by janus.hts.com.au (8.11.6/8.11.6) with ESMTP id h0G37HX01173 for ; Thu, 16 Jan 2003 14:07:18 +1100 Posted-Date: Thu, 16 Jan 2003 14:07:18 +1100 Mime-Version: 1.0 Message-Id: Date: Thu, 16 Jan 2003 14:07:15 +1100 To: ietf-sasl@imc.org From: Steve Farmer Subject: Debugging SASL setup Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-ietf-sasl@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Hi all, I am implementing an SMTP client which needs to authenticate using SASL. I ma having a bit of difficulty debugging against sendmail and I was wondering if anyone could point me towards a setup which I can use to debug, perhaps IMAP or a http setup would be easier or better. Or alternatively is there a debug flag for SASL which can generate a logfile? Regards Steve Farmer -- ------------------------------------------------- Nearly all men can stand adversity, but if you want to test a man's character, give him power. -Abraham Lincoln, U.S. president (1809-1865) Support free speech; visit http://www.efa.org.au/ Heads Together Services Pty Ltd http://www.hts.com.au Email: hts@hts.com.au Tel: 612 9982 6767 Fax: 612 9981 3081 Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h0FC31x03364 for ietf-sasl-bks; Wed, 15 Jan 2003 04:03:01 -0800 (PST) Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h0FC2xo03359 for ; Wed, 15 Jan 2003 04:02:59 -0800 (PST) Received: from hobo.OpenLDAP.org (root@localhost [127.0.0.1]) by pretender.boolean.net (8.12.6/8.12.5) with ESMTP id h0FC2u0a083301 for ; Wed, 15 Jan 2003 12:02:58 GMT (envelope-from Kurt@OpenLDAP.org) Message-Id: <5.2.0.9.0.20030115125934.01f3b900@127.0.0.1> X-Sender: kurt@127.0.0.1 X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Wed, 15 Jan 2003 13:01:27 +0100 To: ietf-sasl@imc.org From: "Kurt D. Zeilenga" Subject: SASL @ IETF#56 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-ietf-sasl@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: BTW, we'll be meeting in San Francisco. If you are an editor of one of the I-Ds explicitly listed in the charter, please submit a revision as a WG I-D (e.g., draft-ietf-sasl-) for discussion as soon as possible. Kurt Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h0DNbjN26110 for ietf-sasl-bks; Mon, 13 Jan 2003 15:37:45 -0800 (PST) Received: from eagle.oceana.com (eagle.oceana.com [208.17.123.12]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h0DNbio26105 for ; Mon, 13 Jan 2003 15:37:44 -0800 (PST) Received: from oceana.com (ny-kenton4d-237.buf.adelphia.net [68.66.168.237]) (authenticated bits=0) by eagle.oceana.com (8.12.7/8.12.7) with ESMTP id h0DNbMYt015234 (version=TLSv1/SSLv3 cipher=DES-CBC3-SHA bits=168 verify=NOT); Mon, 13 Jan 2003 18:37:27 -0500 Message-ID: <3E234DAD.5B136274@oceana.com> Date: Mon, 13 Jan 2003 18:37:17 -0500 From: Ken Murchison Organization: Oceana Matrix Ltd. X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en,pdf MIME-Version: 1.0 To: Steve Farmer CC: ietf-sasl@imc.org Subject: Re: 16 Octet Hash References: <200301131819.h0DIJ3BH000569@smtp7.andrew.cmu.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-ietf-sasl@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Steve Farmer wrote: > > Hi Larry, > > Apologies for that, I am implementing rfc2831 and it states ... FYI, you might want to look at the the RFC 2831bis draft, which has some corrections/clarifications: http://www.ietf.org/internet-drafts/draft-melnikov-rfc2831bis-02.txt -- Kenneth Murchison Oceana Matrix Ltd. Software Engineer 21 Princeton Place 716-662-8973 x26 Orchard Park, NY 14127 --PGP Public Key-- http://www.oceana.com/~ken/ksm.pgp Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h0DMj3424880 for ietf-sasl-bks; Mon, 13 Jan 2003 14:45:03 -0800 (PST) Received: from kcmso2.proxy.att.com (kcmso2.att.com [192.128.134.71]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h0DMj1o24876 for ; Mon, 13 Jan 2003 14:45:02 -0800 (PST) Received: from maillennium.att.com ([135.25.114.99]) by kcmso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h0DMixx3027255 for ; Mon, 13 Jan 2003 16:45:00 -0600 (CST) Received: from att.com (tony-ob.mt.att.com[135.91.110.11]) by maillennium.att.com (mailgw1) with SMTP id <20030113224430gw100ksdtce> (Authid: tony); Mon, 13 Jan 2003 22:44:30 +0000 Message-ID: <3E234142.5050300@att.com> Date: Mon, 13 Jan 2003 17:44:18 -0500 From: Tony Hansen User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: en-us, en MIME-Version: 1.0 CC: ietf-sasl@imc.org Subject: Re: 16 Octet Hash References: <200301131819.h0DIJ3BH000569@smtp7.andrew.cmu.edu> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-ietf-sasl@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Lawrence Greenfield wrote: > The document is a little unclear at this point. "HEX(n)" means, given > n, the 128-bit output of a previous MD5 or HMAC-MD5 operation, encode > it in 32 hex digits. ... using lower case ... Tony Hansen tony@att.com Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h0DMZbr24191 for ietf-sasl-bks; Mon, 13 Jan 2003 14:35:37 -0800 (PST) Received: from janus.hts.com.au (ramnet15.lnk.telstra.net [165.228.239.54]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h0DMZZo24186 for ; Mon, 13 Jan 2003 14:35:35 -0800 (PST) Received: from [203.28.219.179] (pb.hts.com.au [203.28.219.179]) by janus.hts.com.au (8.11.6/8.11.6) with ESMTP id h0DMZYX32534; Tue, 14 Jan 2003 09:35:34 +1100 Posted-Date: Tue, 14 Jan 2003 09:35:34 +1100 Mime-Version: 1.0 Message-Id: In-Reply-To: <200301132230.h0DMUFDX021571@smtp5.andrew.cmu.edu> References: <200301131819.h0DIJ3BH000569@smtp7.andrew.cmu.edu> <200301132230.h0DMUFDX021571@smtp5.andrew.cmu.edu> Date: Tue, 14 Jan 2003 09:35:34 +1100 To: Lawrence Greenfield , ietf-sasl@imc.org From: Steve Farmer Subject: Re: 16 Octet Hash Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-ietf-sasl@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Larry, Thanks mate , I had assumed that but I wanted to be clear. Regards from "Down Under" Steve At 5:30 PM -0500 13/1/03, Lawrence Greenfield wrote: > Date: Tue, 14 Jan 2003 09:25:50 +1100 > From: Steve Farmer > > Apologies for that, I am implementing rfc2831 and it states ... > > "Let KD(k, s) be H({k, ":", s}), i.e., the 16 octet hash of the > string k, a colon and the string s. > > Let HEX(n) be the representation of the 16 octet MD5 hash" > > Soi I am wondering what to use for the 16 octet hash > >As it says, you must use MD5, as described in RFC 1321. The output of >MD5 is 128-bits (16 octets) long. HMAC-MD5 is described RFC 2104. > >You should use exactly the hash operation that is specified. > >The document is a little unclear at this point. "HEX(n)" means, given >n, the 128-bit output of a previous MD5 or HMAC-MD5 operation, encode >it in 32 hex digits. > >Larry -- ------------------------------------------------- Nearly all men can stand adversity, but if you want to test a man's character, give him power. -Abraham Lincoln, U.S. president (1809-1865) Support free speech; visit http://www.efa.org.au/ Heads Together Services Pty Ltd http://www.hts.com.au Email: hts@hts.com.au Tel: 612 9982 6767 Fax: 612 9981 3081 Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h0DMUJm24061 for ietf-sasl-bks; Mon, 13 Jan 2003 14:30:19 -0800 (PST) Received: from smtp5.andrew.cmu.edu (SMTP5.andrew.cmu.edu [128.2.10.85]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h0DMUIo24056 for ; Mon, 13 Jan 2003 14:30:18 -0800 (PST) Received: from penguin.andrew.cmu.edu (PENGUIN.andrew.cmu.edu [128.2.121.100]) by smtp5.andrew.cmu.edu (8.12.3.Beta2/8.12.3.Beta2) with ESMTP id h0DMUFDX021571; Mon, 13 Jan 2003 17:30:15 -0500 Date: Mon, 13 Jan 2003 17:30:15 -0500 Message-Id: <200301132230.h0DMUFDX021571@smtp5.andrew.cmu.edu> From: Lawrence Greenfield X-Mailer: BatIMail version 3.3 To: ietf-sasl@imc.org, Steve Farmer In-reply-to: Subject: Re: 16 Octet Hash References: <200301131819.h0DIJ3BH000569@smtp7.andrew.cmu.edu> User-Agent: SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (=?ISO-8859-4?Q?Unebigory?= =?ISO-8859-4?Q?=F2mae?=) Emacs/21.2 (i686-pc-linux-gnu) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII Sender: owner-ietf-sasl@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Date: Tue, 14 Jan 2003 09:25:50 +1100 From: Steve Farmer Apologies for that, I am implementing rfc2831 and it states ... "Let KD(k, s) be H({k, ":", s}), i.e., the 16 octet hash of the string k, a colon and the string s. Let HEX(n) be the representation of the 16 octet MD5 hash" Soi I am wondering what to use for the 16 octet hash As it says, you must use MD5, as described in RFC 1321. The output of MD5 is 128-bits (16 octets) long. HMAC-MD5 is described RFC 2104. You should use exactly the hash operation that is specified. The document is a little unclear at this point. "HEX(n)" means, given n, the 128-bit output of a previous MD5 or HMAC-MD5 operation, encode it in 32 hex digits. Larry Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h0DMPt023986 for ietf-sasl-bks; Mon, 13 Jan 2003 14:25:55 -0800 (PST) Received: from janus.hts.com.au (ramnet15.lnk.telstra.net [165.228.239.54]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h0DMPro23981 for ; Mon, 13 Jan 2003 14:25:54 -0800 (PST) Received: from [203.28.219.179] (pb.hts.com.au [203.28.219.179]) by janus.hts.com.au (8.11.6/8.11.6) with ESMTP id h0DMPpX32394; Tue, 14 Jan 2003 09:25:51 +1100 Posted-Date: Tue, 14 Jan 2003 09:25:51 +1100 Mime-Version: 1.0 Message-Id: In-Reply-To: <200301131819.h0DIJ3BH000569@smtp7.andrew.cmu.edu> References: <200301131819.h0DIJ3BH000569@smtp7.andrew.cmu.edu> Date: Tue, 14 Jan 2003 09:25:50 +1100 To: Lawrence Greenfield , ietf-sasl@imc.org From: Steve Farmer Subject: Re: 16 Octet Hash Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-ietf-sasl@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Hi Larry, Apologies for that, I am implementing rfc2831 and it states ... "Let KD(k, s) be H({k, ":", s}), i.e., the 16 octet hash of the string k, a colon and the string s. Let HEX(n) be the representation of the 16 octet MD5 hash" Soi I am wondering what to use for the 16 octet hash Regards Steve At 1:19 PM -0500 13/1/03, Lawrence Greenfield wrote: > Date: Mon, 13 Jan 2003 12:17:42 +1100 > From: Steve Farmer >[...] > I may be missing something simple here. I am implementing a SMTP > client using SASL. However the rfc specifies a 16 octet hash as well > as a 16 octet MD5 hash. > > Since MD4 gives a 16 octet result , is it OK to use this ? If not > what should I be using for the 16 octet hash? > >What RFC are you talking about? What are you interested in doing? > >I can't think of any case where you can freely substitute one hash for >another in an over-the-wire protocol, but your question leaves out too >many details for me to understand what you're trying to do. > >Larry -- ------------------------------------------------- Nearly all men can stand adversity, but if you want to test a man's character, give him power. -Abraham Lincoln, U.S. president (1809-1865) Support free speech; visit http://www.efa.org.au/ Heads Together Services Pty Ltd http://www.hts.com.au Email: hts@hts.com.au Tel: 612 9982 6767 Fax: 612 9981 3081 Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h0DIJBl18026 for ietf-sasl-bks; Mon, 13 Jan 2003 10:19:11 -0800 (PST) Received: from smtp7.andrew.cmu.edu (SMTP7.andrew.cmu.edu [128.2.10.87]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h0DIJAo18022 for ; Mon, 13 Jan 2003 10:19:10 -0800 (PST) Received: from penguin.andrew.cmu.edu (PENGUIN.andrew.cmu.edu [128.2.121.100]) by smtp7.andrew.cmu.edu (8.12.3.Beta2/8.12.3.Beta2) with ESMTP id h0DIJ3BH000569; Mon, 13 Jan 2003 13:19:03 -0500 Date: Mon, 13 Jan 2003 13:19:03 -0500 Message-Id: <200301131819.h0DIJ3BH000569@smtp7.andrew.cmu.edu> From: Lawrence Greenfield X-Mailer: BatIMail version 3.3 To: ietf-sasl@imc.org, Steve Farmer In-reply-to: Subject: Re: 16 Octet Hash References: User-Agent: SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (=?ISO-8859-4?Q?Unebigory?= =?ISO-8859-4?Q?=F2mae?=) Emacs/21.2 (i686-pc-linux-gnu) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII Sender: owner-ietf-sasl@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Date: Mon, 13 Jan 2003 12:17:42 +1100 From: Steve Farmer [...] I may be missing something simple here. I am implementing a SMTP client using SASL. However the rfc specifies a 16 octet hash as well as a 16 octet MD5 hash. Since MD4 gives a 16 octet result , is it OK to use this ? If not what should I be using for the 16 octet hash? What RFC are you talking about? What are you interested in doing? I can't think of any case where you can freely substitute one hash for another in an over-the-wire protocol, but your question leaves out too many details for me to understand what you're trying to do. Larry Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h0D1HmB15245 for ietf-sasl-bks; Sun, 12 Jan 2003 17:17:48 -0800 (PST) Received: from janus.hts.com.au (ramnet15.lnk.telstra.net [165.228.239.54]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h0D1Hio15241 for ; Sun, 12 Jan 2003 17:17:46 -0800 (PST) Received: from [203.28.219.179] (pb.hts.com.au [203.28.219.179]) by janus.hts.com.au (8.11.6/8.11.6) with ESMTP id h0D1HiX19761 for ; Mon, 13 Jan 2003 12:17:45 +1100 Posted-Date: Mon, 13 Jan 2003 12:17:45 +1100 Mime-Version: 1.0 Message-Id: Date: Mon, 13 Jan 2003 12:17:42 +1100 To: ietf-sasl@imc.org From: Steve Farmer Subject: 16 Octet Hash Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-ietf-sasl@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Hi all, I may be missing something simple here. I am implementing a SMTP client using SASL. However the rfc specifies a 16 octet hash as well as a 16 octet MD5 hash. Since MD4 gives a 16 octet result , is it OK to use this ? If not what should I be using for the 16 octet hash? Regards Steve Farmer -- ------------------------------------------------- Nearly all men can stand adversity, but if you want to test a man's character, give him power. -Abraham Lincoln, U.S. president (1809-1865) Support free speech; visit http://www.efa.org.au/ Heads Together Services Pty Ltd http://www.hts.com.au Email: hts@hts.com.au Tel: 612 9982 6767 Fax: 612 9981 3081 Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h0AJrsT19356 for ietf-sasl-bks; Fri, 10 Jan 2003 11:53:54 -0800 (PST) Received: from luminous.mit.edu (LUMINOUS.MIT.EDU [18.101.1.61]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h0AJrqo19352 for ; Fri, 10 Jan 2003 11:53:52 -0800 (PST) Received: by luminous.mit.edu (Postfix, from userid 1000) id 3EB8B7680A; Fri, 10 Jan 2003 14:53:12 -0500 (EST) To: ietf-sasl@imc.org Subject: [Internet-Drafts@ietf.org] I-D ACTION:draft-josefsson-sasl-kerberos5-00.txt From: Sam Hartman Date: Fri, 10 Jan 2003 14:53:11 -0500 Message-ID: <87znq893yw.fsf@luminous.mit.edu> Lines: 112 User-Agent: Gnus/5.090006 (Oort Gnus v0.06) Emacs/21.1 (i386-debian-linux-gnu) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Sender: owner-ietf-sasl@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: --=-=-= I understand this is out of scope for our working group, but it seems that forwarding the initial announcement is reasonable. --=-=-= Content-Type: message/rfc822 Content-Disposition: inline Return-Path: Received: from solipsist-nation ([unix socket]) by solipsist-nation (Cyrus v2.1.5-Debian2.1.5-1) with LMTP; Fri, 10 Jan 2003 13:55:55 -0500 X-Sieve: CMU Sieve 2.2 Return-Path: Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by suchdamage.org (Postfix) with ESMTP id 1BC19131E1 for ; Fri, 10 Jan 2003 13:55:55 -0500 (EST) Received: from atalanta.ctd.anl.gov (atalanta.ctd.anl.gov [146.137.194.4]) by fort-point-station.mit.edu (8.9.2/8.9.2) with ESMTP id NAA12883; Fri, 10 Jan 2003 13:55:52 -0500 (EST) Received: (from majordom@localhost) by atalanta.ctd.anl.gov (8.9.1a/8.9.1) id MAA03022 for ietf-krb-wg-outgoing; Fri, 10 Jan 2003 12:52:41 -0600 (CST) Received: from hermes.ctd.anl.gov (localhost [127.0.0.1]) by atalanta.ctd.anl.gov (8.9.1a/8.9.1) with ESMTP id MAA03016 for ; Fri, 10 Jan 2003 12:52:40 -0600 (CST) Received: from hermes.ctd.anl.gov (localhost [127.0.0.1]) by hermes.ctd.anl.gov (8.9.1a/8.9.1) with ESMTP id MAA12809 for ; Fri, 10 Jan 2003 12:52:38 -0600 (CST) Received: from mailrelay.anl.gov (mailrelay.anl.gov [130.202.101.22]) by hermes.ctd.anl.gov (8.9.1a/8.9.1) with ESMTP id MAA12806 for ; Fri, 10 Jan 2003 12:52:38 -0600 (CST) Received: from localhost.localdomain (localhost [127.0.0.1]) by localhost.ctd.anl.gov (Postfix) with ESMTP id 43A605F0DAC; Fri, 10 Jan 2003 12:52:38 -0600 (CST) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by mailrelay.anl.gov (Postfix) with ESMTP id 712555F0D91 for ; Fri, 10 Jan 2003 12:52:37 -0600 (CST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10890; Fri, 10 Jan 2003 13:49:18 -0500 (EST) Message-Id: <200301101849.NAA10890@ietf.org> To: IETF-Announce: ; Cc: ietf-krb-wg@anl.gov From: Internet-Drafts@ietf.org Reply-To: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-josefsson-sasl-kerberos5-00.txt Date: Fri, 10 Jan 2003 13:49:18 -0500 X-Spam-Level: **** Sender: owner-ietf-krb-wg@achilles.ctd.anl.gov Precedence: bulk X-Spam-Status: No, hits=0.8 required=5.0 tests=NO_REAL_NAME,TO_MALFORMED,EXCUSE_6 version=2.20 X-Spam-Level: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===-=-=" --===-=-= A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : A Kerberos 5 SASL Mechanism Author(s) : S. Josefsson Filename : draft-josefsson-sasl-kerberos5-00.txt Pages : 11 Date : 2003-1-9 This document specifies a Simple Authentication and Security Layer (SASL) [3] mechanism for Kerberos 5 Client/Server Authentication [1], with optional initial Authentication Service (AS) and/or Ticket-Granting-Service (TGS) exchanges. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-josefsson-sasl-kerberos5-00.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-josefsson-sasl-kerberos5-00.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-josefsson-sasl-kerberos5-00.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. --===-=-= Content-Type: multipart/alternative; boundary="====-=-=" --====-=-= Content-Type: message/external-body; access-type=mail-server Content-Type: text/plain Content-ID: <2003-1-10140627.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-josefsson-sasl-kerberos5-00.txt --====-=-= Content-Type: message/external-body; name=draft-josefsson-sasl-kerberos5-00.txt; access-type=anon-ftp Content-Type: text/plain Content-ID: <2003-1-10140627.I-D@ietf.org> --====-=-=-- --===-=-=-- --=-=-=-- Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h09ERgn19998 for ietf-sasl-bks; Thu, 9 Jan 2003 06:27:42 -0800 (PST) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h09ERfo19994 for ; Thu, 9 Jan 2003 06:27:41 -0800 (PST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11022; Thu, 9 Jan 2003 09:24:27 -0500 (EST) Message-Id: <200301091424.JAA11022@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: ietf-sasl@imc.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-sasl-anon-00.txt Date: Thu, 09 Jan 2003 09:24:27 -0500 Sender: owner-ietf-sasl@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Simple Authentication and Security Layer Working Group of the IETF. Title : The Anonymous SASL Mechanism Author(s) : K. Zeilenga Filename : draft-ietf-sasl-anon-00.txt Pages : 8 Date : 2003-1-8 It is common practice on the Internet to permit anonymous access to various services. Traditionally, this has been done with a plain text password mechanism using 'anonymous' as the user name and optional trace information, such as an email address, as the password. As plaintext login commands are not permitted in new IETF protocols, a new way to provide anonymous login is needed within the context of the Simple Authentication and Security Layer (SASL) framework. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-sasl-anon-00.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-sasl-anon-00.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-sasl-anon-00.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: <2003-1-9092500.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-sasl-anon-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-sasl-anon-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-1-9092500.I-D@ietf.org> --OtherAccess-- --NextPart--