Ticket #57 (defect)

Opened 4 years ago

Last modified 4 years ago

--keyring argument to openpgp appears to require a full path

Status: new

Reported by: sion Assigned to: sion
Priority: normal Milestone:
Component: library Version:
Severity: normal Keywords:
Cc:

If i try to provide a relative path to the --keyring option in openpgp, it appears to assume that to item is relative to the root directory (/).

For example:

> 0 wt215 at pip:~/testring$ GNUPGHOME=. gpg --list-keys > ./pubring.gpg > ------------- > pub 1024R/1099C2FF 2009-06-09 > uid test key for openpgp (DO NOT USE) <foo at example.org> > > 0 wt215 at pip:~/testring$ GNUPGHOME=. gpg --with-colons --fixed-list-mode --list-keys > tru::1:1244572477:0:3:1:5 > pub:u:1024:1:FD42ADC41099C2FF:1244570552:::u:::scSC: > uid:u::::1244570552::F2F772CEBDF749BF5C455DAB23DB5915A35DCBA0::test key for openpgp (DO NOT USE) <foo at example.org>: > 0 wt215 at pip:~/testring$ openpgp --list-keys --keyring=pubring.gpg > dir: /home/wt215/.gnupg > /pubring.gpg: No such file or directory > Cannot read keyring /pubring.gpg > 255 wt215 at pip:~/testring$ openpgp --list-keys --keyring=$(pwd)/pubring.gpg > dir: /home/wt215/.gnupg > 1 keys > pub FD42ADC41099C2FF 2009-05-09 test key for openpgp (DO NOT USE) <foo at example.org> > 0 wt215 at pip:~/testring$

It seems that this utility should be able to accept any standard path designation, relative or absolute.

--dkg

Change History

06/11/09 10:39:33: Modified by sion

  • owner changed from rachel to sion.