<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-cite-prefix">On 11/09/2015 03:29 PM, Dean Coclin
wrote:<br>
</div>
<blockquote
cite="mid:14D026C7F297AD44AC82578DD818CDD047C2AE07E1@TUS1XCHEVSPIN35.SYMC.SYMANTEC.COM"
type="cite">
<pre wrap="">You made a statement in another email which, if I'm remembering correctly, said something like this: If a cert is issued from a public root, for public domains, for use by the public, then its contents is automatically public. </pre>
</blockquote>
<br>
I think by definition any certificate content is meant for public
consumption, e.g. a third party that relies on it. As compared to
sensitive documents or other personal details that may be used for
the verification of a party stated in a certificate, that part
wouldn't be meant for public consumption.<br>
<br>
My 0.02 US$<br>
<br>
<div class="moz-signature">-- <br>
<table border="0" cellpadding="0" cellspacing="0">
<tbody>
<tr>
<td colspan="2">Regards </td>
</tr>
<tr>
<td colspan="2"> </td>
</tr>
<tr>
<td>Signer: </td>
<td>Eddy Nigg, COO/CTO</td>
</tr>
<tr>
<td> </td>
<td><a href="http://www.startcom.org">StartCom Ltd.</a></td>
</tr>
<tr>
<td>XMPP: </td>
<td><a href="xmpp:startcom@startcom.org">startcom@startcom.org</a></td>
</tr>
<tr>
<td>Blog: </td>
<td><a href="http://blog.startcom.org">Join the Revolution!</a></td>
</tr>
<tr>
<td>Twitter: </td>
<td><a href="http://twitter.com/eddy_nigg">Follow Me</a></td>
</tr>
<tr>
<td colspan="2"> </td>
</tr>
</tbody>
</table>
</div>
</body>
</html>