6.0.0-beta1
7/19/25
  • Error
    Ticket 8163 was not found.

[#6836] Password = 0 does not work
Summary Password = 0 does not work
Queue IMP
Queue Version 4.1.6
Type Bug
State Resolved
Priority 2. Medium
Owners Horde Developers (at) , slusarz (at) horde (dot) org
Requester asl (at) launay (dot) org
Created 06/04/2008 (6254 days ago)
Due
Updated 06/05/2008 (6253 days ago)
Assigned 06/05/2008 (6253 days ago)
Resolved 06/05/2008 (6253 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
06/05/2008 05:56:32 AM Michael Slusarz State ⇒ Resolved
 
06/05/2008 05:16:53 AM Michael Slusarz Comment #11
Assigned to Michael Slusarz
Reply to this comment
Fixed in IMP 4.2.1.
06/05/2008 02:01:32 AM Chuck Hagenbuch State ⇒ Assigned
Assigned to Horde DevelopersHorde Developers
 
06/04/2008 11:06:37 PM Michael Slusarz Comment #9 Reply to this comment
I think empty($passwd) with passwd=0 just break the thing.
That would be correct.  That should be changed to strlen($passwd).
06/04/2008 11:04:34 PM asl (at) launay (dot) org Comment #8 Reply to this comment
Nothing at all in phplog (with E_ALL), no connection attemptto the 
imap server. Same thing on another system, will try a third tomorrow. 
No idea how to debug the thing ...

echo "var:" . $_POST['server'] . $_POST['port'] . $_POST['user'] . 
$_POST['passwd'] . $_POST['server_type'] . "\n";



on line 151 of imp/test.php shows the right stuff;



echo "foobar\n";

on line 153 (after the tests line:

if (!empty($server) && !empty($user) && !empty($passwd) && !empty($type)) {

)

doesn't appear, and it prints again the server/port/login form.



I think empty($passwd) with passwd=0 just break the thing.



Easiest way to test is probably setting up a test account with a 
password of 0.
06/04/2008 10:50:33 PM Jan Schneider Comment #7 Reply to this comment
Do you get an error message, a PHP error, a log entry, etc?
06/04/2008 10:35:06 PM asl (at) launay (dot) org Comment #6 Reply to this comment
Sorry. It just get back to the login page, again and again. test.php 
gives the fields where to put server/port/login/etc again, after 
pushing the button.
06/04/2008 10:12:05 PM Jan Schneider Comment #5 Reply to this comment
You still didn't say what exactly happens if you use this password.
06/04/2008 09:58:43 PM asl (at) launay (dot) org Comment #4 Reply to this comment
Agreed with the silly password part :) Anyway, customers...



Well, horde installed in horde/ , imp in horde/imp, horde/imp/test.php 
with any login and password = 0 show the bug -- and horde login with 
imp as the login backend show it too, imp being configured for imap 
login with the imap server above.
06/04/2008 09:36:07 PM Jan Schneider Comment #3
State ⇒ Feedback
Reply to this comment
Beside that this is really a silly password, where/how exactly does it fail?
06/04/2008 06:48:30 PM asl (at) launay (dot) org Comment #2 Reply to this comment
Uh, forgot to specify it works just fine when using a telnet session.

Cyrus IMAP4 v2.3.9 under.
06/04/2008 06:42:24 PM asl (at) launay (dot) org Comment #1
Patch ⇒ No
State ⇒ Unconfirmed
Milestone ⇒
Queue ⇒ IMP
Summary ⇒ Password = 0 does not work
Type ⇒ Bug
Priority ⇒ 2. Medium
Reply to this comment
When you have an imap configured imp (did not try with pop), and a 
user with a password of "0" (zero), it can never log in. Tested on 
horde 3.1.7, imp 4.1.6. Testing with imp/test.php shows the very same 
thing, so I suspect the bug is somewhere in the imp/lib/IMAP part.

Saved Queries