#1023 Password policies causing crash

v1.0_(example)
closed
None
5
2013-01-09
2012-04-07
Mitch Ames
No

With PasswordSafe v3.28 (build 4783) running on Windows XP SP1, PasswordSafe crashes when I try to use a named password policy other than the default policy. Unfortuneately:
- It doesn't happen every time, and I can't reproduce it with any specific sequence (that I have found yet)
- It only happens with my real database - which I'm not prepared to send the crash dump from. It does not happen with a test database that I created to try to reproduce the problem.
The real database has 49 entries and 6 groups (including a couple of nested groups); the test database has 13 items and 3 groups.
The default policy is 32 characters with at least 1 uppercase, 1 lowercase, 1 digit, 1 symbol from the default set. The other policy is 20 characters, 1 upper, 1 lower, 1 digit, 1 symbol from the special set !@$%^&*
The good news is that even with the test database I can see some strange things happening. If I repeatedly generate passwords, either with Ctrl-P or by adding a new entry, swapping between the default and other policy, I'll eventually see (eg in the Ctrl-P dialog) that the generation rules do not match the policy when I switch policies. Sometimes it's a subtle as the Default or Special Set radio button not changing when it should, sometimes the password length is wrong. Once I had very wrong values for all lengths (password and "at least") - in the thousands! These incorrect values don't necessarily mean that it will crash, nor even generate the password from the wrong rules, but it does reproducibly demonstrate that there is some problem in the policy handling.

Discussion

  • DrK

    DrK - 2012-04-07

    I can guarantee that the small mini-dump (usually less than 70Kb) does not contain any of your user data (this is a password manager and we would be very remiss to include such data!). Without it, we are unlikely be able to easily solve your problem.

    You can look at the source and see what is allowed and what is not allowed to be included in this mini-dump. You can use an editor (NotePad++ can handle these files but please open it read-only) to view the dump and search for anything you recognise.

    If you don't want to upload it to this Bug Report, you can send it via email to me: "c-273 AT users.sourceforge.net" or the Project Admin: "ronys AT users.sourceforge.net"

    David

     
  • Mitch Ames

    Mitch Ames - 2012-04-08

    Test database. Password is 1234

     
  • Mitch Ames

    Mitch Ames - 2012-04-08

    I've reproduced the problem a couple of times with a test database, and attached the test database and dump files. In both cases the crash occurred while I had the Generate Password (Ctrl-P) dialog open and was changing between policies. In each case I done a few other related things first, eg added entries to the database, generated new passwords for entries, generated passwords with Ctrl-P. It took maybe 5-10 minutes of doing these things before it failed, so I don't have the exact sequence of operations.

     
  • Rony Shapiro

    Rony Shapiro - 2012-04-08

    Got it - fix imminent.

     
  • Rony Shapiro

    Rony Shapiro - 2012-04-08

    Hi,

    Thanks to Mitch for the minidump and description, and to David for parsing the minidump. With this level of information, the fix is almost always obvious & straightforward. A version with the fix implemented may be found in
    http://pwsafe.org/tmp/pwsafe-3.28.1-bin.zip. (revision 4856)

    Cheers,

    Rony

     
  • Rony Shapiro

    Rony Shapiro - 2013-01-09
    • status: pending --> closed
    • milestone: --> v1.0_(example)
     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks