Project

General

Profile

Actions

Bug #31293

closed

Login with UTF8-Chars impossible anymore

Added by Jonny no-lastname-given over 12 years ago. Updated over 10 years ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
Backend API
Target version:
-
Start date:
2011-10-25
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.6
PHP Version:
Tags:
Complexity:
medium
Is Regression:
No
Sprint Focus:

Description

Hello,
currently I am updating my installations to Typo3 4.6.
When I use the old build 4.5.7 I can log in with my password (which contains symbols like ☺ ☻ ◘ ○).
With the new 4.6.0 my login is not valid anymore.
I'm not using saltedpasswords/rsaauth.

greetz

Actions #1

Updated by Jeff Segars over 12 years ago

  • Category set to Backend API
  • Complexity set to medium

Jonny,
Thanks for the bug report. What PHP version and operating system are you using?

Thanks,
Jeff

Actions #2

Updated by Xavier Perseguers over 12 years ago

We updated the md5.js library which is used in login form to have UTF8 support which was not the case before. In fact, the md5 hash in TYPO3 4.5 is wrongly calculated.

Please try to manually update your md5 hash in the database, I guess it should then work.

HTH

Actions #3

Updated by Steffen Gebert over 12 years ago

But why did this work before?

Actions #4

Updated by Jonny no-lastname-given over 12 years ago

Hello,
I'm using Debian Lenny with PHP 5.3.8.
I tried several times to set the PW in the backend with an other admin, but it Never worked. So the algorithm is wrong at this Place now, isnt it? Typo3 should be compatuble with itself :)

Actions #5

Updated by Philipp Gampe over 10 years ago

  • Status changed from New to Needs Feedback

Can you still reproduce this? If yes, can you provide a sample password?

Actions #6

Updated by Alexander Opitz over 10 years ago

  • Status changed from Needs Feedback to Closed
  • Is Regression set to No

No feedback within the last 90 days => closing this ticket.

If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.

Actions

Also available in: Atom PDF