Bluehost.com Web Hosting $6.95

Re: sasl > 2.1.15 and user@domain logins

This is a discussion on Re: sasl > 2.1.15 and user@domain logins within the mailing.postfix.users forums, part of the Mail Servers and Related category; On Sun, Feb 22, 2004 at 01:07:39PM +0100, Andreas Winkelmann wrote: Hi ya, <..problem descr..> > ...


Go Back   Usenet Forums > Mail Servers and Related > mailing.postfix.users

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 02-22-2004
Wouter de Jong
 
Posts: n/a
Default Re: sasl > 2.1.15 and user@domain logins

On Sun, Feb 22, 2004 at 01:07:39PM +0100, Andreas Winkelmann wrote:

Hi ya,

<..problem descr..>

> Not a problem, a new Feature of Cyrus-SASL.
>
> Maybe this Patch will help you:
>
> http://asg.web.cmu.edu/archive/messa...patch&msg=4669


Thank you :) Stupid feature IMHO, since it's not controllable via
config.

--
WideXS http://www.widexs.nl
Wouter de Jong System-Administrator
Tel +31 (0)23 5698070 Fax +31 (0)23 5698099
Bijlmermeerstraat 62, 2131 HG HOOFDDORP, NL
Reply With Quote
  #2 (permalink)  
Old 02-26-2004
J?rg Spilker
 
Posts: n/a
Default Re: sasl > 2.1.15 and user@domain logins

wouter@widexs.nl (Wouter de Jong) wrote in message news:<c1a722$2v73$1@FreeBSD.csie.NCTU.edu.tw>...

Hello,

> <..problem descr..>
>
> > Not a problem, a new Feature of Cyrus-SASL.
> >
> > Maybe this Patch will help you:
> >
> > http://asg.web.cmu.edu/archive/messa...patch&msg=4669

>
> Thank you :) Stupid feature IMHO, since it's not controllable via
> config.


sorry, but probably my problem with sasl authentification in postfix
is related to yours. But iīm using sasl 2.1.15 and postfix 2.0.14
(which are the original versions from SuSE 9.0). When a client tries
to authenticate with postfix the following happened:

Feb 26 17:18:15 daolin postfix/smtpd[9422]: connect from
lotus.jetsys.de[192.168.9.10]
Feb 26 17:18:15 daolin postfix/smtpd[9422]: setting up TLS connection
from lotus.jetsys.de[192.168.9.10]
Feb 26 17:18:15 daolin postfix/smtpd[9422]: TLS connection established
from lotus.jetsys.de[192.168.9.10]: TLSv1 with cipher RC4-MD5 (128/128
bits)
Feb 26 17:18:15 daolin saslauthd[1813]: rel_accept_lock : released
accept lock
Feb 26 17:18:15 daolin saslauthd[1813]: pam_unix2:
pam_sm_authenticate() called
Feb 26 17:18:15 daolin saslauthd[1813]: pam_unix2:
username=[js@mail.jetsys.de]
Feb 26 17:18:15 daolin saslauthd[1814]: get_accept_lock : acquired
accept lock
Feb 26 17:18:15 daolin saslauthd[1813]: pam_unix2: pw == NULL, return
PAM_USER_UNKNOWN
Feb 26 17:18:15 daolin saslauthd[1813]: DEBUG: auth_pam:
pam_authenticate failed: User not known to the underlying
authentication module
Feb 26 17:18:15 daolin saslauthd[1813]: do_auth : auth
failure: [user=js@mail.jetsys.de] [service=smtp]
[realm=mail.jetsys.de] [mech=pam] [reason=PAM auth error]
Feb 26 17:18:15 daolin postfix/smtpd[9422]: warning:
lotus.jetsys.de[192.168.9.10]: SASL LOGIN authentication failed

As i understand the problem is the domain part in the username which
isnīt handled correctly by pam.

cyrus-imapd doesnīt show this behaviour. This username transmitted to
saslauthd only contains the plain username and no domain part.

Should i upgrade to sasl 2.1.16 and apply the fix?

Greetings, Joerg
Reply With Quote
Reply
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are Off
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On




All times are GMT +1. The time now is 07:47 AM.


Powered by vBulletin® Version 3.7.3
Copyright ©2000 - 2009, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO 3.0.0