[TYPO3-core] FYI: Added feature #11314: Extract functionality to create session ID from t3lib_userAuth::start()

[David Bruchmann]

----- Ursprüngliche Nachricht -----
Von:        David Bruchmann <typo3-team-core at bruchmann-web.de>
Gesendet:   Mittwoch, 10. Juni 2009 19:27:37
An:         TYPO3 core team <typo3-team-core at lists.netfielders.de>
CC:
Betreff:    Re: [TYPO3-core] FYI: Added feature #11314: Extract 
functionality to create session ID from t3lib_userAuth::start()
> ----- Ursprüngliche Nachricht -----
> Von:        Oliver Hader <oliver at typo3.org>
> Gesendet:   Mittwoch, 10. Juni 2009 18:29:27
> An:         typo3-team-core at lists.netfielders.de
> CC:
> Betreff:    Re: [TYPO3-core] FYI: Added feature #11314: Extract 
> functionality to create session ID from t3lib_userAuth::start()
>> Hi again,
>>
>> there's another thing that I'd like to change as follow-up to this issue.
>>
>> Problem:
>> The lenth of the "hash" (session ID) is fixed to a maximum of 32 chars.
>> If another hash-function shall be used to create the session ID, e.g.
>> SHA1, it won't work.
>>
>> Solution:
>> Add a new member variable $maxHashLength that can be overriden.
>>
>> Notes:
>> If nobody objects, I'm going to commit the attached change to SVN Trunk
>> in 24 hours.
>>
> 
> Hy Oliver,
> 
> Additionally perhaps it's useful to define the hash-type as type that 
> can be choosen. So validating of different standard-types can be 
> integrated while the type "user" or "userdefined" has to be verified by 
> a user-function.
> 
> Best regards
> David
> 

Hy Oliver,

for the case my proposition is accepted, $maxHashLength will become a 
parameter of userfunction because it doesn't make any sense for other 
hash-types I think.

Best regards
David