On Thu, 2012-04-12 at 12:25 +0200, Stef Walter wrote: > On 2012-04-12 01:36, Bruce Korb wrote: > > One slight drawback: If, say, some app that I use were to become > > a virus vector, where I keep my database of sites and passwords > > is pretty much unguessable. An unencrypted, standardized tool's > > database is not so obscure. So, I don't want seahorse keeping my > > passwords, thank you very much. I'll "vi" my private database. > > I now go back to my initial question, how do I get this beast > > off of my system forever? What you want to remove is the GNOME keyring; Seahorse is just a front-end for managing GNOME keyrings. > Hmmm. Interesting question. Normally GNOME is taken a whole. But if I > was in your situation I might do one o > $ sudo yum remove gnome-keyring > $ sudo apt-get remove gnome-keyring > $ (your choice of package manager remove command) > This removes the gnome-keyring-daemon which stores the passwords. You > can also remove the gnome-keyring-pam package. I'd assume dependency checks would require you to do so. > It also looks like the package managers for gnome-keyring have gotten > the dependencies wrong. Applications should depend on the > libgnome-keyring package, and not gnome-keyring itself. Although it's > not strictly my responsibility, I can help solve this filing some bugs > and/or alerting package maintainers. > But in the mean time you may need to persuade your package manager to > remove gnome-keyring without removing its dependencies. > Obviously this isn't configuration GNOME supports. So YMMV. HTH. +1
Attachment:
signature.asc
Description: This is a digitally signed message part