--batch --gen-key

Werner Koch wk at gnupg.org
Tue May 11 09:35:02 CEST 2004

On Mon, 10 May 2004 22:35:30 -0400 (EDT), Atom 'Smasher' said:

> i'm not subscribed to devel, so please CC me on any responses. (i have
> tried twice to subscribe, maybe someone should look into that.)

You are now.

> * the "%pubring" and "%secring" control statements both seem limited to
> creating files in the current directory. any directory paths as arguments
> are silently ignored. placing the argument inside of double or single

Just looked at the code and there is no special handling of filenames;
there are passed verbatim to the open function.  Tilde expansion is
also not done.

> * files are created with liberal permissions:
> 	$ ls -l seckey.sec
> 	-rw-r--r--  1 alpha  alpha  2475 May 10 22:24 seckey.sec

Quite possible.  I'll change that.

> * if a file (or STDIN) specifies making multiple keys, it seems that the
> file remains empty until the whole job is done. shouldn't gpg be writing
> the new keys to file(s) as keys are being created?

Ah tyes. This is die to the internal close/open optimization.  I'll
change that.


More information about the Gnupg-devel mailing list