[Dovecot] Concerned about Dovecot's new NTLM code

[Timo Sirainen]

On 27.9.2004, at 15:17, Andrew Bartlett wrote:

>>>>>  - Unicode support is by 'null padding' - there is no real support 
>>>>> for
>>>>> non-ascii characters.

What does support for this actually mean? Does NTLM support multiple 
character sets or how exactly is the conversion done? A simple UTF8 -> 
UTF16 would be easy. iconv() could be used for other translations.

> Use of ntlm_auth allows use of external password databases, but doesn't
> prevent the use of other mechanisms in any way.  As I mentioned before,
> I'm quite willing to work with developers in the implementation of an
> appropriate callback to allow application that already assume 'I have
> the plaintext' to have Samba at least handle the NTLMSSP parsing and
> authentication.

I'm not against ntlm_auth() support, but personally I don't really care 
about it at the moment. I'm of course willing to answer questions about 
Dovecot code if someone wants to implement it.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
URL: <http://dovecot.org/pipermail/dovecot/attachments/20040927/66d1269e/attachment-0001.bin>