-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Is there a reason why FileSink will write a Hex encoded public/private key to a single line in the file, while a Base64 encoded key will be written to multiple lines?
Example:
RSAES_OAEP_SHA_Encryptor pub(priv); Base64Encoder pubFile(new FileSink(pubfn)); ~ pub.DEREncode(pubFile); ~ pubFile.MessageEnd();
gives you (with 3 carriage returns)
MIGdMA0GCSqGSIb3DQEBAQUAA4GLADCBhwKBgQC5n7Pg1vurj0Y2znTGmtUXKX4OEKSmTNKc w+lnccxRJ4YotcRi1n92C5kI/X78fIRHhAmet6n7wefxxo1W36g653JR7dwVlPKl2nrky/8p +ppoOcU68yemiJkbzBZQbNDVgZyby+kgctFfYxn5vsB+lzOawlLTeZ6x/LWHUnwdUQIBEQ==
while
RSAES_OAEP_SHA_Encryptor pub(priv); HexEncoder pubFile(new FileSink(pubfn)); ~ pub.DEREncode(pubFile); ~ pubFile.MessageEnd();
gives you (with no carriage returns)
30819D300D0..(rest of key here)....F14061C5020111
Regards,
Ludwig Seitz
- -- Dipl.-Inform. Ludwig Seitz, LIRIS, INSA-LYON, 7 B�t. Blaise Pascal (501), 20 Avenue Albert Einstein, 69621 Villeurbanne T�l. bureau: +33 (0)4 72 43 63 48 email: [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFAF94vvkfWH3neoacRAvvcAJ43uzuIPBcBqKKkGGpCIkwAz2o+aQCgiXBa bRn2PMtNsEk3EjmFaJfuRrw= =e7U/ -----END PGP SIGNATURE-----
