view release on metacpan or  search on metacpan

README  view on Meta::CPAN

      fairly time consuming), but only when $keyring->save is called or
      when keyring is destroyed.

    Note: it of course does not make much sense to keep app passwords in
    encrypted storage if master password is saved in plain text. The module
    most natural usage is to interactively ask for master password (and use
    it to protect noticeable number of application-specific passwords).

    Ideas of how to workaround this obstacle are welcome. I loosely
    consider either caching master password per desktop session
    (implementing sht. similar to ssh-agent/gpg-agent or using one of those
    somehow), or integrating the tool with PAM to use actual system
    password, or both - but while it seems doable on Linux, cross platform
    solution is not so easy.

 set_password(username, password, realm)

    Sets (stores) password identified by given realm for given user

 get_password($user_name, $realm)

lib/Passwd/Keyring/PWSafe3.pm  view on Meta::CPAN

=back

Note: it of course does not make much sense to keep app passwords in
encrypted storage if master password is saved in plain text. The
module most natural usage is to interactively ask for master password
(and use it to protect noticeable number of application-specific
passwords).

Ideas of how to workaround this obstacle are welcome. I loosely
consider either caching master password per desktop session
(implementing sht. similar to ssh-agent/gpg-agent or using one of
those somehow), or integrating the tool with PAM to use actual system
password, or both - but while it seems doable on Linux, cross platform
solution is not so easy.

=cut

sub new {
    my ($cls, %args) = @_;

    my $self = {};