STDOUT & STDERR

[Atom 'Smasher']

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

> We should probably look at it for 1.4 though.  Atom, can you give an
> example?
==============================

here, the file "test.asc" contains the signed and encrypted text string:
**TESTING**\n

the slashes are used to to separate the commands with the intent of
keeping them easy to read.

as you can see, there's a lot of stuff other then just the message being
sent to STDOUT. this happens when i specify "verbose" more than once.

/////////////////////////// ## gpg takes STDIN from file "test.asc"
/////////////////////////// ## sends STDOUT to file "test-1"
/////////////////////////// ## sends STDERR to file "test-2"

$ gpg -vv < test.asc > test-1 2> test-2

/////////////////////////// ## the file containing STDOUT
/////////////////////////// ## has a lot of diagnostic information
/////////////////////////// ## above and below the message text
/////////////////////////// ##
/////////////////////////// ## looks like "--list-packets" was implied

$ cat test-1
:pubkey enc packet: version 3, algo 16, keyid 6C6EEE7A1E88BF71
	data: [2048 bits]
	data: [2042 bits]
:encrypted data packet:
	length: 145
	mdc_method: 2
:compressed packet: algo=2
:onepass_sig packet: keyid 9C280BBF3D7D41E3
	version 3, sigclass 00, digest 2, pubkey 17, last=1
:literal data packet:
	mode b, created 1077141999, name="",
	raw data: 12 bytes
**TESTING**
:signature packet: algo 17, keyid 9C280BBF3D7D41E3
	version 3, created 1077141999, md5len 5, sigclass 00
	digest algo 2, begin of digest a1 91
	data: [160 bits]
	data: [159 bits]

/////////////////////////// ## the file containg STDERR has what
/////////////////////////// ## i would expect to see (and plenty of it!)

$ cat test-2
gpg: using character set `iso-8859-1'
gpg: armor: BEGIN PGP MESSAGE
gpg: armor header: Version: GnuPG v1.2.4 (FreeBSD)
gpg: public key is 1E88BF71
gpg: using secondary key 1E88BF71 instead of primary key 3D7D41E3
gpg: using secondary key 1E88BF71 instead of primary key 3D7D41E3
gpg: public key encrypted data: good DEK
gpg: encrypted with 2048-bit ELG-E key, ID 1E88BF71, created 2003-10-04
      "Atom Smasher <atom at suspicious.org>"
gpg: AES256 encrypted data
gpg: original file name=''
gpg: Signature made Wed Feb 18 17:06:39 2004 EST using DSA key ID 3D7D41E3
gpg: Good signature from "Atom Smasher <atom at suspicious.org>"
gpg:                 aka "Atom Smasher <atom at smasher.org>"
gpg: key 3D7D41E3: accepted as trusted key
gpg: key 1915CAC6: accepted as trusted key
gpg: key 9131544A: accepted as trusted key
gpg: key A1416513: accepted as trusted key
gpg: key 2C668519: accepted as trusted key
gpg: key 50FEA8FD: accepted as trusted key
gpg: key C0C2434A: accepted as trusted key
gpg: key 5AD1570D: accepted as trusted key
gpg: binary signature, digest algorithm SHA1
gpg: decryption okay

/////////////////////////////////////////////


        ...atom

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

	"Every successful revolt is termed a revolution,
	 and every unsuccessful one a rebellion."
		-- Joseph Priestly, 1791
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)
Comment: What is this gibberish?  -  http://atom.smasher.org/links/#digital_signatures

iD8DBQFAM+funCgLvz19QeMRAtETAJ9WDOXZKP1sfJcdAGrhnIQBGW+Q/QCfVsP8
t12SbV0bIA3nYV3CxPNU980=
=50Pr
-----END PGP SIGNATURE-----