we are using ldap for login to tikiwiki. If the user has a > or < character in his password he is not able to login to tikiwiki. He will get the message "password is not correct".
I asume that this might be a code problem in php or html so that tikiwiki interprete these characters as code?
The Problem will be found here:
-> /srv/www/htdocs/tikiwiki/tiki-setup_base.php
in the line:
614: $_POST = $inputFilter->filter($_POST);
...in which obviously all Request-Parameters will be somehow filtered inklusive Password
($_REQUEST'pass'). Before/After the Request-Hash looks as follows (Test-Passwort: Ordix<0590):
<!-- array(5) {
%22user%22=>
string(2) "ca"
%22pass%22=>
string(10) "Ordix>0590"
%22login%22=>
string(6) "Log In"
%22stay_in_ssl_mode_present%22=>
string(1) "y"
%22stay_in_ssl_mode%22=>
string(1) "n"
}
-->
Merging with Issue
https://dev.tiki.org/item4599
we have now removed the filter for the passwort.
affected file is wikix:/srv/www/htdocs/tikiwiki/tiki-login.php ( line 15)
9 $inputConfiguration = array(
10 array( 'staticKeyFilters' => array(
11 'user' => 'text',
12 'username' => 'text',
13 // upd by ts Fr 19. Jul 13:16:29 CEST 2013
14 // Entered password wir be no longer filtered
15 //'pass' => 'text',
16 ) )
17 );
So then logging with special characters works (although you could now also integrate with any unsightly code)
Is there a possobility to check this filter for certain bugs?
To help developers solve the bug, we kindly request that you demonstrate your bug on a show2.tiki.org instance. To start, simply select a version and click on "Create show2.tiki.org instance". Once the instance is ready (in a minute or two), as indicated in the status window below, you can then access that instance, login (the initial admin username/password is "admin") and configure the Tiki to demonstrate your bug. Priority will be given to bugs that have been demonstrated on show2.tiki.org.
filename | created | hits | comment | version | filetype | ||
---|---|---|---|---|---|---|---|
No attachments for this item |