Date: Wed, 5 Sep 2007 07:58:58 -0500 From: Eric Crist <mnslinky@gmail.com> To: "Jim Stapleton" <stapleton.41@gmail.com> Cc: freebsd-questions@freebsd.org, Jonathan McKeown <jonathan+freebsd-questions@hst.org.za> Subject: Re: questions on setting up a mail server Message-ID: <E1365388-3B3A-4266-B633-9FF85926069F@gmail.com> In-Reply-To: <80f4f2b20709050346l21f000f0y552bc0711cfcacfd@mail.gmail.com> References: <BMEDLGAENEKCJFGODFOCGEELCAAA.tedm@toybox.placo.com> <200709051012.46793.jonathan%2Bfreebsd-questions@hst.org.za> <80f4f2b20709050346l21f000f0y552bc0711cfcacfd@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sep 5, 2007, at 5:46 AMSep 5, 2007, Jim Stapleton wrote: >> All the authentication options you mention after plain text (which >> is the >> standard method built in to the protocol) require Cyrus SASL. This >> isn't as >> scary to set up as the docs make it sound. PLAIN and LOGIN can >> both use your >> existing user passwords (which is what I do). GSSAPI requires >> Kerberos, and >> the digest methods (the -MD5 ones) need a separate file of >> passwords held in >> plain text - the sasldb. Of the passwd-based methods, PLAIN is the >> preferred >> protocol according to the docs and RFCs - LOGIN is the one >> Microsoft uses (go >> figure). > > Thanks, that's almost all of what I needed there. You insinuated (but > I don't think explicitly stated) that LOGIN is in fact encrypted in > some form? > > Thanks, > Only across SSL/TLS connections. ----- Eric F Crist Secure Computing Networks
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1365388-3B3A-4266-B633-9FF85926069F>