Peter Samuelson <pe...@p12n.org> writes: > Why public key? That's useful if a certain class of people need to be > able to write but not read the file, or vice versa.
It's the other way around. Anyone with write access to the location to the cpm directory used will be able to encrypt (changes to) the keyring so it is readable by a number of GnuPG keys belonging to, for instance, a group of system administrators. If the same class of people hold the private keys as well as the read/write permissions for the cpm directory, you have a shared and hopefully secure storage for passwords. > I can't figure out how that could be useful for a password manager. It would be impolite to agree here. :) > Aside from that, can it use or import password from 'pwsafe', > 'gnome-keyring' or 'kwallet'? Through a wetware bridge, sure. > Is there a reason this app isn't just a frontend to one or more of > those? Possibly, but I won't speculate about that. You should ask the author. The reason for looking at "cpm" was because it filled a need not satisfied by 'pwsafe', 'gnome-keyring' or 'kwallet', which was "shared, console-based storage for secret information". -- Stig Sandbeck Mathisen -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/7xsk3rsg5n....@fsck.linpro.no
