Date: Sat, 27 Sep 2014 15:17:23 -0400 From: Brandon Allbery <allbery.b@gmail.com> To: Dimitry Andric <dim@freebsd.org> Cc: freebsd-stable <freebsd-stable@freebsd.org>, Jan Bramkamp <crest@rlwinm.de> Subject: Re: 10.1 BETA2 World - Breaks saslauthd Message-ID: <CAKFCL4X65zdQRyHj45sPhTa_oNmnmfM4WD-%2BT5r7LHbbJs9N=Q@mail.gmail.com> In-Reply-To: <433B3FD3-55B1-4FF1-BD4E-10A0EC6CEC50@FreeBSD.org> References: <b492e700f57a52e21f7755e6d01bd863.squirrel@www.tundraware.com> <3DA4B666-AB81-4F25-ABAE-DDC163F41E20@FreeBSD.org> <5426C3F3.3040404@rlwinm.de> <A4E96B09-AEF9-46B3-A812-1DFB7EB6D90B@FreeBSD.org> <CAKFCL4V9yY17H15j=R9KKbKeK_zU64ysn4caqF9qem8JwPviCw@mail.gmail.com> <433B3FD3-55B1-4FF1-BD4E-10A0EC6CEC50@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Sep 27, 2014 at 3:11 PM, Dimitry Andric <dim@freebsd.org> wrote: > > saslauthd isn't the core SASL entry point; it's a hack to export > traditional password stores as SASL providers to cyrus-sasl. Last I > checked, it didn't actually receive the service name from SASL. > > Well, last I checked it did, and it even logs the service name. :) What I left out is that the last time I checked was something like 10 years ago, before everything was migrated to using Kerberos. :) (Come to think of it, "cyrus-sasl" might be a hint about that; cyrus-sasl v1 has been dead for a longish time, the current one is cyrus-sasl2. Although saslauthd is itself a slightly more general version of the hack v1 used.) -- brandon s allbery kf8nh sine nomine associates allbery.b@gmail.com ballbery@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAKFCL4X65zdQRyHj45sPhTa_oNmnmfM4WD-%2BT5r7LHbbJs9N=Q>