Re: [gnukeyring-discuss] keyring-link utility - making it more useful

[Jochen H. <hoe...@gm...>]

On Fri, 4 Mar 2005 18:34:17 +0000, Chris Green <ch...@ar...> wrote:
> I have a need to extract data from the keyring database on the command
> line so I've taken the existing keyring-link utility and have done a
> few  simple/trivial changes to make it more useful for my use at
> least.  If anyone is interested I'm quite happy to upload this
> version.

Did you work on the latest version (keyring-link-2.0-pre1 or 
the latest cvs release)?  The only change from 0.1.1 is that this version
supports keyring-2.0pre  (database version 5). 

You can either post the patch to the sourceforge patch tracker, or post
it here.  Preferrably as a diff against the latest release/cvs version (they
should be identical).

> The changes are basically as follows:-
> 
>     Remove the password from the command line arguments leaving only
>     the keyring database file name.
> 
>     The file name defaults to $HOME/.jpilot/Keys-Gtkr.pdb so you don't
>     have to enter it normally.

Of course this depends on using jpilot.  Maybe this could be configurable
by environment variable.

>     When keyring-link is run (I've actually renamed it to kl) it
>     prompts 'Key: ' and expects the user to enter an entry name
>     followed by a password in the format '<entry>/<password>', if the
>     password is correct then just the <entry> is output.

If you read the password from tty, it may be better to use getpass() for
getting the password (which hides the entered password), at least if on
a tty.  It might make it less portable though.

> I've changed the output format a little to suit my needs and have
> removed the use of the 'rs_xxx' functions for error output, it just
> outputs to stderr.
> 


-- 
Jochen Hoenicke, University of Oldenburg, 26111 Oldenburg, Germany
Email: hoe...@in...  Tel: +49 441 798 3124