TYPO3 Core

I have discovered that the value 'ses_id' in be_sessions does not match the cookie value set in the browser in which you cannot log in. Clearing the browser cookies does not work. I can login in Google Chrome but not in FF

Setting your browser "In Private" solves the problem......... FYI

#0013812 is a duplicate and seems not to appear on Windows.
Is that the same for you?

Is this bug still valid? Does the problem still exist?

BE login fails with the latest TYPO3 4.4.4 and 4.5 trunk with the Firefox 3.6.10 under LINUX.
It works with other browsers as Navigateur Web 2.28.1 and older versions of Firefox.

BE login does also not work with the latest Firefox 3.6.12 under LINUX.
It did work with a 2 month older version of TYPO3 4.5. trunk.

The backend login into TYPO3 4.5 beta4 does not work with the browsers Firefox 3.6.12, Epiphany (GNOME Navigateur Web 2.28.1) and Konqueror Konqueror
Version 4.3.5 (KDE 4.3.5)
Sous KDE 4.3.5 (KDE 4.3.5).
This is a new installation of TYPO3 4.5 beta4 with no other extension installed than those installed by the install tool.

It works with Internet Explorer 6.

It seems logging into the backend with a username which contains germaun umlauts doesn't work. Had to change 'ö' to 'oe' and backend login works again - maybe related. TYPO3 Version 4.4.6.

Yes, there's already a report for it. Problem is md5.js, which is wrong.
I want to exchange that for 4.6 (as it's too late for 4.5).

Sidenote: Works with saltedpasswords, which everybody should use btw.

Resolved, unable to reproduce:

• The 'unable to login with special chars if saltedpasswd / rsauth is not installed' should be an own (bugfix) issue if still valid.
• Unabled to reproduce login failures with most of Franz browsers (some exactly at the same version).

Please open issues for concrete problems (charset, exact browser problems) if issues are still reproducible.