--batch --gen-key

[Atom 'Smasher']

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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.)

since the man page calls this an "experimental feature", i guess that
means i should ask about it on the devel list.

i'm using gpg 1.2.4

there are a few things about generating keys in batch mode that seem odd
to me....

* 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
quotes produces an error.

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

* 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?


        ...atom

 _________________________________________
 PGP key - http://atom.smasher.org/pgp.txt
 3EBE 2810 30AE 601D 54B2 4A90 9C28 0BBF 3D7D 41E3
 -------------------------------------------------

	"The unleashed power of the atom has changed
	 everything save our modes of thinking and
	 we thus drift toward unparalleled catastrophe."
		-- Albert Einstein
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)
Comment: What is this gibberish?  -  http://atom.smasher.org/links/#digital_signatures

iEYEARECAAYFAkCgO/cACgkQnCgLvz19QeN/kQCeN7DY1OnmDXVreeclOaAi4yoV
pqIAniNYFSIw9MO6sYq49dLGysbZ39k+
=mRX3
-----END PGP SIGNATURE-----