#177 The lock file not taken into account!!!!!

v1.0_(example)
closed
5
2012-09-17
2005-02-17
Anonymous
No

The lock file is not taken into account when on
the "Safe Combination Entry Window" and you open
another database other then the default.
It will not take into account the password lock file and
when you exit it will delete the other users password
lock file.

Steps to reproduce.

Users must be using older versions of PWDSafe.exe so
presistent settings are already in the registry.

User 1 opens password.dat on network share and enters
correct key combination (lock file created and users and
passwords show up)

User 2
Runs 2.08 and usually works DBpasswords.dat. But now
wants to open password.dat that User 1 just opened.
User 2 opens password.dat and enters key combination.
(passwords and users show up, lock file remains,
note:no alert shows up saying it can be only used for
read only.)

User 2 makes changes, saves and exits
(lock file gone)

User 1 makes changes, saves and exits

User 2 later goes in and files missing.

Note when the default database is set for both users
and they never change the DB the lock file mechanism
works correctly.

Regards,
Anthony

Discussion

  • Rony Shapiro

    Rony Shapiro - 2005-02-18

    Logged In: YES
    user_id=370700

    Hm,

    There is a problem with locks and opening via file->open
    after an existing database is displayed, but not exactly as
    described.

    If user 1 is using a version earlier than 2.08, then s/he
    will not be locking the file, and the behaviour will be as
    described.
    For the locking mechanism to work between users, all users
    must be using version 2.08 or later.

    The problem I found is that if a user starts up passwordsafe
    with database "A" and the uses file->open to open database
    "B", the lock on "A" is never released. This will be fixed.

     
  • Rony Shapiro

    Rony Shapiro - 2005-02-21

    Logged In: YES
    user_id=370700

    Fixed in 2.09

     

Log in to post a comment.