Re: Passwords containing backslash - problem.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Citando Dan White <dwhite@xxxxxxx>:

On 20/07/11 09:46 -0500, Dan White wrote:
On 20/07/11 10:50 -0300, Lauro Costa G. Borges wrote:
Does saslauthd handle backslashes ok for the rest of you? Cause it
doesn't seem to handle it with testsaslauthd or as a Postfix auth daemon.

I can't reproduce this problem while using the PAM backend. Which saslauthd
backend are you using? If relevant, what sasl configuration is your imap
server using?

Both of these work for me:

testsaslauthd -u username -p 'test\1234'
testsaslauthd -u username -p test\\1234

Where the password is:

test\1234

Saslauthd at the smtp server uses RIMAP as the backend, and the remote imap server to which it connects (Dovecot) does not use saslauthd, it uses LDAP. As I said before, this imap server can understand backslashes in the password, since I successfully authenticated on it using telnet.

I can reproduce the problem while using the rimap backend.

I've filed the following bug report:

https://bugzilla.cyrusimap.org/show_bug.cgi?id=3493

 Thanks for that. I will monitor the bug report.

I tested using testsaslauthd and single quotes, it worked, but using RIMAP backend it still doesn't work. So I guess these were two different problems: RIMAP backend problem and testsaslauthd usage problem (single quotes vs double quotes).

 Thanks


Also, saslauthd has an ldap backend you may want to use, as a work around.
See doc/LDAP_SASLAUTHD in the sasl source for configuration documentation.

--
Dan White



----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.





[Index of Archives]     [Info Cyrus]     [Squirrel Mail]     [Linux Media]     [Yosemite News]     [gtk]     [KDE]     [Gimp on Windows]     [Steve's Art]

  Powered by Linux