Mailing List Archive

Re: Odd output on the status-fd
[.Jason, can we move this to gnupg-devel, but you have to subscribe to
this one first I think]

Jason Gunthorpe <jgg@ualberta.ca> writes:

> Given that there are no distinguishing markings or any other information
> preceeding this second section I suspect it is unintended. I'm just going

I changed it so that SIG_ID will only be emitted for signature
classes 0 and 1 and not for any key signatures.

> As an aside, I would like to completely disable the trust db, for my

There is the --always-trust option, but I'm not sure whether the
trustdb is needed anyway.

> use for the db gpg maintains. I would also like to supress it's automatic
> generation of secring.gpg and pubring.gpg, but there seem to be no options

This should not happen if you use --no-default-keyrings?


--
Werner Koch at guug.de www.gnupg.org keyid 621CC013
Re: Odd output on the status-fd [ In reply to ]
Jason Gunthorpe <jgg@ualberta.ca> writes:

> Yes, I am using --always-trust for generating encrypted messages (BTW my
> version doesn't document this flag) but when I verify a signature it still
> inserts the key into the trustdb.

I will add a way to disable this.

--
Werner Koch at guug.de www.gnupg.org keyid 621CC013