playing with ecc in batch mode
Sergi Blanch i Torné
sergi at calcurco.cat
Sat Feb 5 19:27:40 CET 2011
Ok, it works.
I have been able to create many keys with the ecc schema with lengths
of 256 and 384 and check for encrypt/decrypt, sign/verify, list,
Except for the known issue in 521, I test the basics without
passphrase. I'll do the silly pinentry to test with pass.
On Fri, Feb 4, 2011 at 6:50 AM, Werner Koch <wk at gnupg.org> wrote:
> On Thu, 3 Feb 2011 22:53, sergi at calcurco.cat said:
>> Also I have tried with '--passphrase' parameter, the
>> '--passphrase-file', and the batch command 'Passphrase'. Without
>> success, always the popup.
> You can't use that. The regression tests use this to seed the
> passphrase cache:
> gpg-preset-passphrase --preset -P def 50B2D4FA4122C212611048BC5FC31BD44393626E
> You also need to use the --allow-preset-passphrase in gpg-agent.conf.
> Obviously it does not work while generating keys.
> Another, more flexible way, is to write your own pinentry which loops
> back to your test script. gpg passes the envvar PINENTRY_USER_DATA all
> the way up to the pinentry; this can be used to convey a context.
> For testing we have the %no-protection batch parameter:
> $GPG --quiet --batch --gen-key <<EOF
> Key-Type: DSA
> Key-Length: 1024
> Subkey-Type: ELG
> Subkey-Length: 1024
> Name-Real: Harry H.
> Name-Comment: test key
> Name-Email: hh@@ddorf.de
> Expire-Date: 1
> Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.
More information about the Gnupg-devel