Bug #22328
closedwrong md5-hash of md5.js, frontend-, backend-login
100%
Description
The md5-calculation produces wrong, it belongs to the used characters.
Following characters produces this failure:
äöüÄÖܧáÁ and many more.
These characters are not forbidden.
The md5.js is also used to send the backend-password.
Due the failure of md5.js it could be easier to descend the password-algorythm.
Following characters are availible:
01234567890123456789012345678901!\"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ [\\]^_`abcdefghijklmnopqrstuvwxyz{|}~
All other characters produces a wrong hash.
As fe-users want to change their password, I've noticed this problem in affinity with Issue #0012206.
It's not possible to replace the md5.js simple.
All hashed passwords are written in the wrong md5-code, that means, all users have to retype their password on login or have to receive automatically a new password...
See:
http://www.typo3.net/index.php?id=13&action=list_post&tid=70355&page=2%29
language: german, the problem occurs on usernames with specialchars/umlauts.
Attached is the old md5.js and a new one with no failure.
(issue imported from #M13917)
Files