#4 Various option to make pwmanager multi instance capable

[donavan nelson]

1) Add the option to auto the current list of in
memory passwords if the current list has changed in
memory (additions, changed command, changed passwords
etc.). User configurable timeout would be nice as well.

2) Add option to auto reload the current disk file it
it changes. (Either automatically or with user
approval). User configuratable time interval to check
would be nice.

3) .pwm file locking during write operations.

I run a shared .pwm file (available over secure nfs)
that several pwmanager clients access during the course
of a day.

1) my laptop (VPN nfs mount)
2) my work station at work (VPN nfs mount)
3) my main system at home (also the nfs server)
4) my graphically enabled server at my data center (nfs
over a secure channel)

This program is a life saver, particularly with
recently mandated security changes at work where we
don't have openLDAP access on production boxes. (Users
only get accounts on as required basis.) Not to
mention the crazy rules about changing passwords and
whatis expected to be contained in them.

But I occassionally find that I change or add a
password and forget to save it. A bigger problem is
that I don't restart pwManager to get any existing
changes to the .pwm file before adding/changing a
password in the current instance.

I normally keep pwManager running in the KDE system
tray on 3 of my 4 boxes listed above.

[Michael Buesch]

Logged In: YES
user_id=856853

All your requested features are in development. You can
checkout branch "daemon-dev" in CVS to see the progress.
It's still far from being complete, but once PwManager-2.0
is released, all your features will be implemented.
Short summary: PwManager will be capable of running in
daemon/server mode. So you can set up a central PwManager
server and access this server from all machines in your
network in a secure and reentrancy save way.

[Nobody/Anonymous]

Logged In: NO

Any progress reports on 2.0 with some of these features?

[Michael Buesch]

Logged In: YES
user_id=856853

Well, I'm currently in active development.
It's harder to get right, as it seemd to be in the first
place. I'm finally realising, that I have to rewrite the
whole codebase, to get it right. I almost finished the core
API design, now. A complete implementation of the server and
the GUI is in progress. Please give me some additional time.
I don't know when KDE4 will be out, but as it looks like at
the moment, PwManager-2 will depend at least on QT4.
Current 2.0 development is taking place in HEAD.
Current stable branch is 1.2 and actively maintained.
Thanks for your interrest in PwManager development.