[foaf-protocols] Poll on WebID Protocol Ontology Changes

Toby Inkster tai at g5n.co.uk
Tue Oct 5 23:55:40 CEST 2010


On Tue, 05 Oct 2010 22:36:06 +0100
Nathan <nathan at webr3.org> wrote:

> -----BEGIN PUBLIC KEY-----
> MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQD9tvsRWXEOruxpvulN9SaYCVAn
> fmjV9m9M1Xp34C3Cl6WTjacjfFmmpSghwsAwHILKkBgYWY10UW1GUpiXZQW60l6E
> bOwsD0tL8vP5VGMWyICmEimj5oGZGzfzhwqN1ZG+tS6VS7GHMnMnZwNPN2XaJj/Y
> pPFL5aE8xgnXyYpoRwIDAQAB
> -----END PUBLIC KEY-----

Apache doesn't expose this directly anyway, so you'd need to use an
ASN.1 parser to pull it out of the certificate. I don't see how that
significantly simplifies implementations.

Whatsmore, if I wanted to get this PEM key and put it in my FOAF, how
do I do it without fiddling around with the openssl command-line
client? If I look at my certificate in my browser's certificate manager
(and I've checked this with Opera and Firefox), I can't find it. I can
find the modulus in hex; I can find the exponent in hex (Opera) or
decimal (Firefox); I can't find a PEM or DER encoded public key.

-- 
Toby A Inkster
<mailto:mail at tobyinkster.co.uk>
<http://tobyinkster.co.uk>



More information about the foaf-protocols mailing list