Michael J Gruber writes:
> Sorry, this got "lost in vacation". Before that, I was looking for an
> easy way to test expired signatures, but gpg1 and gpg2 behave somewhat
> differently in that respect (2 does not allow to create already expired
> signatures).
>
> Is
Junio C Hamano venit, vidit, dixit 06.10.2016 23:43:
> Junio C Hamano writes:
>
>> Michael J Gruber writes:
>>
>>> Also, I'm open to using another letter for EXPKEYSIG but couldn't decide
>>> between 'Y', 'Z', 'K'. 'K' could be confused with
Junio C Hamano writes:
> Michael J Gruber writes:
>
>> Also, I'm open to using another letter for EXPKEYSIG but couldn't decide
>> between 'Y', 'Z', 'K'. 'K' could be confused with REVKEYSIG, I'm afraid.
>> 'Y' is next to 'X' and contained in 'KEY',
Ramsay Jones venit, vidit, dixit 28.09.2016 23:09:
>
>
> On 28/09/16 20:59, Junio C Hamano wrote:
>> Michael J Gruber writes:
>
>>> + "X" for a good expired signature, or good signature made by an expired
>>> key,
>>
>> As an attempt to clarify that we cover both
Junio C Hamano venit, vidit, dixit 28.09.2016 21:59:
> Michael J Gruber writes:
>
>> - Use GNUPGHOME="$HOME/gnupg-home-not-used" just like in other tests (lib).
>
> If you are not using /dev/null, I expected you to do
>
> . ./test-lib.sh
>
On 28/09/16 20:59, Junio C Hamano wrote:
> Michael J Gruber writes:
>> + "X" for a good expired signature, or good signature made by an expired
>> key,
>
> As an attempt to clarify that we cover both EXPSIG and EXPKEYSIG
> cases, I think this is good enough. I
Michael J Gruber writes:
> - Use GNUPGHOME="$HOME/gnupg-home-not-used" just like in other tests (lib).
If you are not using /dev/null, I expected you to do
. ./test-lib.sh
GNUPGHOME_saved=$GNPGHOME
. "$TEST_DIRECTORY/lib-gpg.sh"
and then use
On 28/09/16 15:24, Michael J Gruber wrote:
> According to gpg2's doc/DETAILS:
> "For each signature only one of the codes GOODSIG, BADSIG, EXPSIG,
> EXPKEYSIG, REVKEYSIG or ERRSIG will be emitted."
>
> gpg1 ("classic") behaves the same (although doc/DETAILS
> differs).
>
> Currently, we parse
According to gpg2's doc/DETAILS:
"For each signature only one of the codes GOODSIG, BADSIG, EXPSIG,
EXPKEYSIG, REVKEYSIG or ERRSIG will be emitted."
gpg1 ("classic") behaves the same (although doc/DETAILS
differs).
Currently, we parse gpg's status output for GOODSIG, BADSIG and trust
information
9 matches
Mail list logo