TYPO3 Core

I faced the same problem, you can use: sv_login_redirect
But I'm not sure if it is the kb_md5 extension, but in general typo3 4.1

I use 4.1.1 with kb_md5, newloginbox and sv_login_redirect and it works fine.

Probably we should think about integrating redirection to newloginbox. There are crowds of extensions online to solve this problem in different ways. Difficult for users to find the right one. Also an integration of md5 fe pwd to the core would be fine. This will users give more security by default.
Maybe little problems with updating existing installations!

I found the same fix sv_login_redirect. Option to redirect with the newloginbox would be handy. Although i find more flexibility with redirecting per group or user. md5 would be a great integration to fe_admin and sr_feuser_register, help secure passwords by default.

md5 passwords should become default in the core (as the fe_users and fe_groups tables come with the core).
At the moment you have first to install one of the registration/authentication extensions, and after that you have to install md5 (loadorder). Which sometimes may be too complicated to beginners/not so advanced administrators

Concerning redirection: there are lots of redirection extensions, if one will be integrated in newloginbox, it has to be decided which functionalities are useful. I think there should be a possibility for a general redirection, and also one per group. And a very nice option would be, that users can decide on their own, where they are redirected after login. And all these features should be configureable with typoscript.

That's not a bug of newloginbox. This is because dkd_redirect_at_login uses xclasses to integrate the redirection-function, which overwrites code of newloginbox and uses quite old newloginbox-code.

Regarding redirection I'm working on a flexible solution to integrate some redirection-options.

May I close this bug as it isn't really related to newloginbox?

In my opinion, you may close this bugreport, but probably move our suggestions for further development to some feature wishes.

There are two:
1. Integrate a state-of-the-art redirection system into newloginbox, as most administrators use this extension for authentication.
2. Include md5 encrypted fe_user passwords to the core as a default pwd handling.

Also for me it's not clear, if your redirection works will come into newloginbox or if it will be another standalone extension. In my opinion, the whole frontend user authentication/administration should be thought over, like it happend to direct_mail @t3con06. Probably a paper or bof on t3con07?

Probably someone could easily change the category of this to 'missing feature'. Saves time.

Just changing this issue to 'missing feature' wouldn't be correct I think.

1. The redirection-system is on the way and will be integrated in newloginbox. The goal is to make a couple of extensions obsolete by providing the additional redirection-features through newloginbox. I guess that a first version of it will get into svn in the next two weeks. It is a flexible solution that may be extended easily.

2. I'll take note of this at the newloginbox-wishlist. But I guess there will be a faster change if you create an issue related to the core and/or write a mail to Bernhard Kraft (author of kb_md5fepw) about it, because it isn't a main-goal of newloginbox at the moment.

Personally I don't have yet the time and overview to write a paper for t3con07 about it and I won't be there myself this year.