GNOME Bugzilla – Bug 155681
[PATCH] Command line interface to gnome-keyring
Last modified: 2005-09-18 00:03:03 UTC
It would be nice to have a command line oriented program for manipulating gnome-keyrings. This would allow shell scripts to look up passwords and perform other operations. I started a utility to do this and would like to see if anyone else is interested in this functionality. The output from "gnome-keyring --help" should help illustrate some abilities that I am interested in: [mike@imp src]$ ./gnome-keyring --help gnome-keyring [options] operation [name] -h, --help print a list of options operations: unlock name unlock the named keyring create name create the named keyring passwd name change the password for the named keyring createdefault name create the named keyring and make it the default setdefault name set the named keyringas the default getdefault print the name of the default keyring delete name delete the named keyring
Created attachment 33128 [details] [review] Patch to add gnome-keyringtool to gnome-keyring This patch adds a new command line utility to gnome-keyring. Gnome-keyringtool allows one to perform basic keyring utilities.
Created attachment 33750 [details] [review] Patch to add gnome-keyringtool to gnome-keyring
Created attachment 51114 [details] [review] Patch to add gnome-keyringtool to gnome-keyring This patch now takes advantage of the new synchronous functions provided by gnome-keyring 0.4.3.
I have one issue with this. If people use it, and gnome-keyringtool ends up on the ACL list for various keys, then any app could easily read any of those passwords by just running gnome-keyringtool. This is sort of a security problem. Also, it doesn't really follow the same coding standards as the rest of gnome-keyring.
Do you see any way to resolve this ACL issue? Is there actually an issue yet, given that I have only implemented keyring operations and not key operations (you can't read or copy individual keys)?
I don't really see any way to resolve it, but you're right that it should be safe as long as we don't allow you to read the actual secrets.
Okay, I'm done with this. Setting this bug to resolved because there is no interest.