View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002571 | unreal | ircd | public | 2005-06-24 18:20 | 2005-06-24 19:39 |
| Reporter | Monk | Assigned To | |||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Product Version | 3.2.3 | ||||
| Summary | 0002571: Error in password encryption | ||||
| Description | .:23•55•17:. *** Authentication phrase (method=crypt, para=test) is: E4Kp0pNwvv0M2 .:23•55•18:. *** Authentication phrase (method=crypt, para=test) is: 27kA1jNyRcjug .:23•56•05:. *** Authentication phrase (method=md5, para=test) is: $TpDpMNsl$HsCBw0jcwnz6bE8R3KiJPQ== .:23•56•08:. *** Authentication phrase (method=md5, para=test) is: $lmcq6HYH$zhAud5+ZM8b0qphYo0CYZw== This is reproducible for all our current servers and naturally makes using this feature impossible. First I thought it may be related to updated openssl libraries but the problem persists after a recompile. My box is currently running OpenSSL 0.9.7e from the current Debian sarge distribution. Updates are running regularly so this is the most recent version they offer. The reproducibility doesn’t depend on hash algorithm uses nor on the method to generate the password (command line or within irc client). Regards, Monk | ||||
| 3rd party modules | |||||
|
|
I think it is supposed to be like that... |
|
|
Assuming you mean it can output different strings with the same password... This isn't an error, this is actually a (great) feature... These encrypted passwords contain 'salts' which makes brute force attacks harder and stored-plaintext/ciphertext attacks completely infeasible. |
|
|
Hmm, the strange thing is that I cannot get it to work with new passwords anymore. If I try to set a encrypted oper pwd I cannot oper anymore. This is from my unrealircd.conf password $jMHn3PHi$6GeD4pwJBM+KoVD+aMsAw7w2XBQ= { ripemd-160; }; I rehashed the ircd, reconnected my client and cannot oper anymore. Password was created with /mkpasswd ripemd-160 bla Monk |
|
|
I suggest at least quoting it, just to be sure: password "$jMHn3PHi$6GeD4pwJBM+KoVD+aMsAw7w2XBQ=" { ripemd-160; }; That said, be sure you the server is running a recent version of unreal.. salting for md5/sha1/ripemd160 was introduced in Unreal3.2.2. Salting in crypt has always been supported (on *NIX). |
|
|
Hmpf, quoting it did the trick. Could have come to this solution on my own. Thanks . Regards, Monk |
|
|
Hm.. you sure you copypasted that correctly? I can't oper up with 'bla' here. If I '/mkpasswd ripemd-160 bla' myself I get a string that works: password "$aaZmRb68$ay1oNS1oW7nPzrJp++7LkMfJzyo=" { ripemd-160; }; Does that work for you? |
|
|
hm.. ok ;) |
|
|
Uh, sorry "bla" was just for typing laziness here. The hash value is from a different password. After quoting it, it works perfectly :) |
|
|
ok |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2005-06-24 18:20 | Monk | New Issue | |
| 2005-06-24 18:26 | Stealth | Note Added: 0010106 | |
| 2005-06-24 18:33 | syzop | Note Added: 0010109 | |
| 2005-06-24 19:26 | Monk | Note Added: 0010113 | |
| 2005-06-24 19:26 | Monk | Note Edited: 0010113 | |
| 2005-06-24 19:29 | syzop | Note Added: 0010114 | |
| 2005-06-24 19:32 | Monk | Note Added: 0010115 | |
| 2005-06-24 19:35 | syzop | Note Added: 0010117 | |
| 2005-06-24 19:37 | syzop | Note Added: 0010118 | |
| 2005-06-24 19:37 | Monk | Note Added: 0010119 | |
| 2005-06-24 19:39 | syzop | Status | new => closed |
| 2005-06-24 19:39 | syzop | Note Added: 0010120 | |
| 2005-06-24 19:39 | syzop | Resolution | open => no change required |
