<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
<br>
On 06/09/2010 12:07 AM, From John Kemp:<br>
<blockquote cite="mid:34455205-B747-464A-8F0D-BF060F8A8213@jkemp.net"
type="cite">
<pre wrap="">I see only the same problem I saw (and reported to you) 2 years ago - which is that for all the cryptography involved, it still seems possible for an individual to self-assert that they have a WebID and that it is linked to some certificate and private/public key. Which is to say, why bother with all the crypto if a user can self-assert his or her WebID and FOAF file anyway? </pre>
</blockquote>
<br>
Saw this a bit late, but apparently I'm not alone with my impression.<br>
<br>
<div class="moz-signature">
<table cellpadding="0" cellspacing="0" border="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>
<br>
</body>
</html>