[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

base64 encodings

-----BEGIN PGP SIGNED MESSAGE-----


  I have decided to consider all whitespace to be "binary" since they
are also likely to be munged in transit. 

  I have three possible output "flavours" for the example in 4.1.3,
all of which have the same binary format, so it should not matter.

unencoded: (4:test26:abcdefghijklmnopqrstuvwxyz5:123455::: ::)

1. base64 if anything in the cert is considered binary:
{KDQ6dGVzdDI2OmFiY2RlZmdoaWprbG1ub3BxcnN0dXZ3eHl6NToxMjM0NTU6OjogOjop}

2. base64 only the "binary" portions, but always encode at least three bytes:

(4:test26:abcdefghijklmnopqrstuvwxyz5:123455:::{IDo6})

3. base64 only the "binary" portions, but only encode what is necessary.
(4:test26:abcdefghijklmnopqrstuvwxyz5:123455:::{IA==}::)

   :!mcr!:            |  Network and security consulting/contract programming
   Michael Richardson |   I do IPsec policy code for SSH <http://www.ssh.fi/>
 Personal: <A HREF="http://www.sandelman.ottawa.on.ca/People/Michael_Richardson/Bio.html">mcr@sandelman.ottawa.on.ca</A>. PGP key available.
 Corporate: <A HREF="http://www.sandelman.ottawa.on.ca/SSW/">sales@sandelman.ottawa.on.ca</A>. 






-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: latin1
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface

iQB1AwUBNE5C4aZpLyXYhL+BAQFpjAMAudj+w3gJWxTwsDskg0znadBQ3HVwxNdM
pC/qXt6D82CZ/dgwmasWqmBupLcLhOW/80bEnNo2YqHG7C34s58PGaMy5i7dhqyS
qqc41AERuWdjdg/5vQ3aFhvRvhpotuX3
=u7G5
-----END PGP SIGNATURE-----
Follow-Ups: