From owner-freebsd-isp Fri Jun 12 11:47:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA12616 for freebsd-isp-outgoing; Fri, 12 Jun 1998 11:47:57 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from ve7tcp.ampr.org (ve7tcp.ampr.org [198.161.92.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA12374; Fri, 12 Jun 1998 11:46:40 -0700 (PDT) (envelope-from lyndon@ve7tcp.ampr.org) Received: from ve7tcp.ampr.org (localhost.ampr.org [127.0.0.1]) by ve7tcp.ampr.org (8.9.0/8.9.0) with ESMTP id MAA15378; Fri, 12 Jun 1998 12:46:21 -0600 (MDT) Message-Id: <199806121846.MAA15378@ve7tcp.ampr.org> To: The Hermit Hacker cc: freebsd-isp@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: SASL References In-reply-to: Your message of "Fri, 12 Jun 1998 11:49:24 EDT." Date: Fri, 12 Jun 1998 12:46:20 -0600 From: Lyndon Nerenberg Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>>>> "The" == The Hermit Hacker writes: The> Well, this is the first time I even hear about SASL, The> and I tend to follow the cyrus/IMAP4/ACAP mailing list quite The> closely...what is SASL and where can I read more up on it? RFC2222 defines the framework and the KERBEROS_V4, SKEY, and EXTERNAL mechanisms. RFC2060 defines how SASL works with IMAP4rev1 (i.e. the AUTHENTICATE command). I don't have the ACAP references handy. The proposed SMTP SASL interface (AUTH command) is described in the I-D draft-myers-smtp-auth-*.txt. The CRAM-MD5 SASL mechanism, along with profiles for IMAP and POP, are described in RFC2195. RFC2245 describes the SASL ANONYMOUS mechanism. --lyndon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message