Ken Murchison wrote:
> The SASLv1 library used to store a non-plaintext secret for use with
> DIGEST-MD5. In fact, it stored separate secrets for each mechanism. In
> SASLv2, it was decided to use a single plaintext secret. Part of this
> decision was based on the fact that the DIGEST-MD5 se
On Wed, Dec 05, 2007 at 09:26:58AM -0600, Dan White wrote:
> The auxprop plugin gives you the ability to authenticate using
> the PLAIN, LOGIN, DIGEST-MD5, CRAM-MD5, NTLM and OTP mechs (and
> probably more).
>
> saslauthd only gives you the ability to authenticate using PLAIN
> and LOGIN (I bel
Guillermo Gómez wrote:
>> pam_mysql would correlate to saslauthd, and the cyrus sasl plugin
>> would correlate to auxprop.
>>
>> See documentation on the SASL pwcheck_method setting
>> (sasl_pwcheck_method in /etc/imapd.conf).
>>
>> When set to saslauthd, the pwcheck_method will allow the use of
>>
On Dec 5, 2007 9:42 PM, Guillermo Gómez <[EMAIL PROTECTED]> wrote:
> > pam_mysql would correlate to saslauthd, and the cyrus sasl plugin
> > would correlate to auxprop.
> >
> > See documentation on the SASL pwcheck_method setting
> > (sasl_pwcheck_method in /etc/imapd.conf).
> >
> > When set to sas
Guillermo Gómez wrote:
> Thanks Dan, im reading and trying to digest all the material available.
>
> What the customer wants is:
>
> 1.- md5-digest between imap client/server (squirrelmail/cyrus-imapd)
> 2.- md5 encrypted passwords stored in mysql db (cyrus-imap-??)
>
> Is this combination possi
> pam_mysql would correlate to saslauthd, and the cyrus sasl plugin
> would correlate to auxprop.
>
> See documentation on the SASL pwcheck_method setting
> (sasl_pwcheck_method in /etc/imapd.conf).
>
> When set to saslauthd, the pwcheck_method will allow the use of
> the PLAIN and LOGIN mechanisms
Guillermo Gómez wrote:
> Ive been looking on how to work cyrus imap with mysql and found two options:
>
> cyrus pam with pam_mysql
> cyrus sasl sql plugin
>
> In the first one it look like the store can have the password encrypted MD5
> The second one needs the passwords in the clear in the db
>
> On Dec 5, 2007 9:52 AM, Guillermo Gómez <[EMAIL PROTECTED]> wrote:
> > afaik the digest-md5 occurs between cyrus and the imap client
> > (AUTHENTICATE command) so my doubt is about the user db and password
> > store. Is the password stored in plain text? (mysql auth like
> > http://www.delouw.ch/
On Dec 5, 2007 9:52 AM, Guillermo Gómez <[EMAIL PROTECTED]> wrote:
> afaik the digest-md5 occurs between cyrus and the imap client
> (AUTHENTICATE command) so my doubt is about the user db and password
> store. Is the password stored in plain text? (mysql auth like
> http://www.delouw.ch/linux/Post
On Fri, 7 Nov 2003, Craig Ringer wrote:
> > * Getting sasl to use an auxprop method that calls an LDAP server is
> >possible, but tricky. Various patches exist, but are non trivial
> >to install and configure.
>
> OK, I may be totally wrong here but I thought LDAP authentication was
> nor
Thanks Craig, useful comments.
On Fri, 7 Nov 2003, Craig Ringer wrote:
> > * Getting sasl to use an auxprop method that calls an LDAP server is
> >possible, but tricky. Various patches exist, but are non trivial
> >to install and configure.
>
> OK, I may be totally wrong here but I thoug
* imapd falls back to using sasldb access if digest authentication
is tried
IMHO that calls for a FAQ entry. "I'm trying to use saslauthd, and cyrus
keeps on complaining that it can't read the SASL db - what's wrong?".
* Getting sasl to use an auxprop method that calls an LDAP server is
p
Some delving into the tangled mess that is documentation, the mailing
lists, and the Cyrus wiki, has taught me the following:
* saslauthd can't do digest type authentications. OK, this seems
to be a genuine design restriction
* imapd falls back to using sasldb access if digest authenticatio
On Wed, 18 Jun 2003, Tom Carroll wrote:
> Good day -
>
> Upon upgrading to sasl 2.1.13,cyrus 2.1.13, I started receiving the
> following errors:
>
> bad digest-uri: doesn't match service
> badlogin: XXX.XXX.XXX.XXX DIGEST-MD5 SASL(-13): authentication failure: bad
> digest-uri: doesn't match serv
14 matches
Mail list logo
