> Von: Peter Lebbing [mailto:pe...@digitalbrains.com] > Gesendet: Mittwoch, 5. September 2018 15:21 > An: Fiedler Roman <roman.fied...@ait.ac.at>; gnupg-users@gnupg.org > Betreff: Both correct and surprising non-interactive gen-key (was: How to fix > "ERROR key_generate 3355453" / "GENKEY' failed: IPC call has been > cancelled") > > On 31/08/18 19:11, Fiedler Roman wrote: > > ['/usr/bin/gpg', '--homedir', '/tmp/tmp-3abk6l8', '--with-colons', > > '--status-fd', > '2', '--pinentry-mode', 'loopback', '--batch', '--gen-key', '--command-fd', > '0'] > > It is unclear where the passphrase is supposed to come from... so I > think it's correct that GnuPG CANcels. Oh, by the way, commands should > come last for robustness.
Just for clarification: The "--pinentry-mode" is here only to make gpg-agent/gpg2 happy to get rid of tty-related errors. The batch commands do not request any passphrase to be set, so it should never be read - but maybe I do understand "batch-mode" the same way (consequence: never ask anything) compared to the gpg-meaning of batch. @Peter: thanks for looking at it more closely. There might be quite some sleeping dogs in semi/fully-automated gpg2 operation. > ... Regards, Roman _______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
