W3C home > Mailing lists > Public > public-xg-webid@w3.org > December 2011

using encoded cert (signed) as adjunct to unsigned mod

From: Peter Williams <home_pw@msn.com>
Date: Wed, 28 Dec 2011 20:58:27 -0800
Message-ID: <SNT143-W403CA12861907AC236E50992AD0@phx.gbl>
To: "public-xg-webid@w3.org" <public-xg-webid@w3.org>




if you look at the cert:certificate property (not real), http://rdf-translator.appspot.com/parse?url=http%3A%2F%2Fyorkporc2.blogspot.com%2F&of=n3&html=1 doesnt it make some sense? just think about it (again). The cert is signed. Its IAN fields can point out, by fingerprint(s), the SSL cert(s) on the (_future_ certified https) endpoint(s) on which the profile is to be AUTHORIZED to be bound (by the signing user).
For no effort, you get alot of assurance. You get to prepare for the rollover of the https certs of the server supproting an https-grade webid.   		 	   		  
Received on Thursday, 29 December 2011 04:59:04 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 29 December 2011 04:59:07 GMT