From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: passwordcheck: Log cracklib diagnostics |
Date: | 2020-08-25 11:48:39 |
Message-ID: | C3FEFD22-ABAD-4C14-83EA-DFB5D9C04BE5@yesql.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> On 25 Aug 2020, at 12:20, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
>
> A user tried to use the cracklib build-time option of the passwordcheck module. This failed, as it turned out because there was no dictionary installed in the right place, but the error was not properly reported, because the existing code just throws away the error message from cracklib. Attached is a patch that changes this by logging any error message returned from the cracklib call.
+1 on this, it's also in line with the example documentation from cracklib.
The returned error is potentially a bit misleading now, as it might say claim
that a strong password is easily cracked if the dictionary fails load. Given
that there is no way to distinguish between the class of returned errors it's
hard to see how we can do better though.
While poking at this, we might as well update the docs to point to the right
URL for CrackLib as it moved from Sourceforge five years ago. The attached
diff fixes that.
cheers ./daniel
Attachment | Content-Type | Size |
---|---|---|
cracklib_url.diff | application/octet-stream | 662 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Masahiko Sawada | 2020-08-25 12:17:05 | Re: recovering from "found xmin ... from before relfrozenxid ..." |
Previous Message | Gavin Flower | 2020-08-25 10:57:02 | Re: Hybrid Hash/Nested Loop joins and caching results from subplans |