[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: SCRAM-SHA-1 support in GSASL
From: |
Lothar May |
Subject: |
Re: SCRAM-SHA-1 support in GSASL |
Date: |
Wed, 24 Mar 2010 13:32:24 +0100 |
Hi Simon,
2010/3/22 Simon Josefsson <address@hidden>:
[...]
>> With the new GS2-KRB5 - do you mean this one?
>> http://tools.ietf.org/html/draft-ietf-sasl-gs2-20
>
> Yes, or http://www.rfc-editor.org/authors/rfc5801.txt, although not
> quite final yet.
So gsasl is really cutting edge :-). Thanks for all your work!
>> [...]
>>>> Oh well... Does anyone know how I can use a user name containing utf8
>>>> characters without prior conversion?
>>>
>>> If you use non-ascii strings, you need to build Libidn and link GNU SASL
>>> to it as well -- GNU SASL will reject any non-ascii strings when Libidn
>>> is not enabled. You could hack around this in lib/src/saslprep.c if you
>>> want, but (of course) then you aren't fully SCRAM standards compliant.
>>
>> Oh OK that is the cause of the problem. Is there any chance that I can
>> use the prebuilt mingw gsasl with libidn?
>
> The prebuilt mingw gsasl are built with --without-stringprep. I enabled
> libidn for the build and it went fine, so please test these:
>
> http://josefsson.org/gnutls4win/gsasl-1.4.2-idn.zip
> http://josefsson.org/gnutls4win/gsasl-1.4.2-idn.zip.sig
This one works like a charm! In a first test, I am now able to use
utf8 usernames. Thanks!
> http://josefsson.org/gnutls4win/mingw32-gsasl_1.4.2-idn-1_all.deb
>
> Future gsasl4win builds will use libidn too.
Great!
Lothar