22 Jul
2013
22 Jul
'13
7:51 a.m.
Hi,
I've switched to our own internal hex encoder which is probably faster anyway, and it gives the correct hex encoding.
That's better.
And I can confirm that SSHA1 auth now works again "throughout our userbase". Putting that in quotes because beforehand I used to think I was at that point, too, but then found 0X and the few pitiful users that fell into that. I'm hoping that that was my last find though :-) In short, right now there's nothing on my table that would need fixing for a 2.2.1. Greetings, Stefan -- Stefan WINTER Ingenieur de Recherche Fondation RESTENA - Réseau Téléinformatique de l'Education Nationale et de la Recherche 6, rue Richard Coudenhove-Kalergi L-1359 Luxembourg Tel: +352 424409 1 Fax: +352 422473