Last modified by Sanjay Jangid on 2024/04/17 14:46

From version Icon 54.1 Icon
edited by Henry Story
on 2010/05/28 13:12
Change comment: There is no comment for this version
To version Icon 55.1 Icon
edited by Henry Story
on 2010/05/28 13:15
Change comment: There is no comment for this version

Summary

Details

Icon Page properties
Content
... ... @@ -8,7 +8,7 @@
8 8  <object width="640" height="385"><param name="movie" value="http://www.youtube.com/v/8iZPJBpI2Po&hl=en_US&fs=1&"></param><param name="allowFullScreen" value="true"></param><param name="allowscriptaccess" value="always"></param><embed src="http://www.youtube.com/v/8iZPJBpI2Po&hl=en_US&fs=1&" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="640" height="385"></embed></object>
9 9  {{/html}}
10 10  
11 -With foaf+ssl, you no longer need to type a username or remember a password. Public Key Cryptography takes care of that. As Dan Kaminsky pointed out in a few of his speeches, the major security problem on the web are passwords. 60% of security breaches can be attributed to this technology. Why is it still here? Because the way X.509 was used did not work. By tying X.509 to the semantic web, we solve the major problem on the client side. On the server side DNSsec will solve the other half of the problem. See [[the recent thread on the foaf-protocols list>>http://foaf.markmail.org/thread/6mavqww3d6oii4dt#query:+page:1+mid:5t57suylbzvk44ub+state:results]].
11 +With foaf+ssl, you no longer need to type a username or remember a password. Public Key Cryptography takes care of that. As Dan Kaminsky pointed out in a few of his speeches, the major security problem on the web are passwords. 60% of security breaches can be attributed to them. Why are they still so ubiquitous? Because the only secure contender, SSL - the protocol that gave us online shopping - and X.509 were too expensive and complex for end users. But this need to be so. By tying X.509 to the semantic web, we solve the major problem of cost, and introduce powerful flexibility. On the server side DNSsec will solve the other half of the problem. See [[the recent thread on the foaf-protocols list>>http://foaf.markmail.org/thread/6mavqww3d6oii4dt#query:+page:1+mid:5t57suylbzvk44ub+state:results]].
12 12  
13 13  Currently you can get yourself an account on here, the normal way, then create yourself a [[WebID>>http://esw.w3.org/topic/WebID]].
14 14