On Fri, 04 Jul 2008, Werner Koch wrote:
> On Fri, 4 Jul 2008 09:35, [EMAIL PROTECTED] said:
>
> > When verifying a signature by a key that has subkeys, some of which are
> > expired, GnuPG always prints KEYEXPIRED to the status-fd. It does this
> > even if not the subkey that signed the message
On Sat, 05 Jul 2008, Werner Koch wrote:
> On Fri, 4 Jul 2008 14:53, [EMAIL PROTECTED] said:
>
> > When I have a signature made by an expired key, will I get
> > {GOODSIG,EXPKEYSIG},
> > or {BADSIG,EXPKEYSIG}?
>
> Only one them:
>
> if( !rc || gpg_err_code (rc) == GPG_ERR_BAD_SIGNATURE ) {
On Fri, 4 Jul 2008 14:53, [EMAIL PROTECTED] said:
> When I have a signature made by an expired key, will I get
> {GOODSIG,EXPKEYSIG},
> or {BADSIG,EXPKEYSIG}?
Only one them:
if( !rc || gpg_err_code (rc) == GPG_ERR_BAD_SIGNATURE ) {
KBNODE un, keyblock;
int count=0, statno;
On Fri, 04 Jul 2008, Werner Koch wrote:
> On Fri, 4 Jul 2008 09:35, [EMAIL PROTECTED] said:
>
> > When verifying a signature by a key that has subkeys, some of which are
> > expired, GnuPG always prints KEYEXPIRED to the status-fd. It does this
> > even if not the subkey that signed the message
On Fri, 4 Jul 2008 09:35, [EMAIL PROTECTED] said:
> When verifying a signature by a key that has subkeys, some of which are
> expired, GnuPG always prints KEYEXPIRED to the status-fd. It does this
> even if not the subkey that signed the message expired.
That is due to the way we generate this
Package: gnupg
Version: 1.4.9
When verifying a signature by a key that has subkeys, some of which are
expired, GnuPG always prints KEYEXPIRED to the status-fd. It does this
even if not the subkey that signed the message expired.
Consider this case:
gpg --status-fd=2 --no-default-keyring --keyri
6 matches
Mail list logo
