[foaf-protocols] Problem with certificate on home-grown WebID
henry.story at bblfish.net
Sun Dec 18 11:22:48 CET 2011
On 18 Dec 2011, at 10:03, Sebastian Trüg wrote:
> On 12/17/2011 10:18 PM, Henry Story wrote:
>> On 17 Dec 2011, at 22:09, Sebastian Trüg wrote:
>>> On 12/17/2011 08:26 PM, Henry Story wrote:
>>>> On 17 Dec 2011, at 17:12, Sebastian Trüg wrote:
>>>>>>> Yes, same error.
>>>>>> Ok, I rebuilt the whole thing just to make sure. I think the loading of new modules does not work in
>>>>>> my version anymore.
>>>>>> Can you try the above test again, and send me the output?
>>>>> Looks a bit better now. The public keys are identical but still the
>>>>> error persists (attached).
>>>> Yep, it is very odd, because everything seems to line up but without you being able to log in.
>>>> I have made a few more changes. Can you try once more?
>>> Sorry, the error is still the same as last time: the public keys are the
>>> same but the verification still fails.
>>> But as mentioned I can log into ODS.
>> yes. I know. But this bother me. Because we are not just creating a service that works for ODS but for
>> everyone. Can you send me again the output of the test please?
>> That is all I have to go on. If I can't fix it from there, I'll probably push out the other version
>> I have been working on. The Clerezza version is too much for me to maintain.
> The way see it there are two possibilities:
> 1. There is an actual bug in your solution and my profile exposes it
> 2. My profile or the way I publish it is not 100% correct and the ODS is
> less strict about it
> In any case I doubt that my very simple foaf could be the problem. So it
> is probably the way I serve the file by rewriting "foaf" to "foaf.ttl".
no need that part seems well done at present.
$ curl -I http://www.trueg.de/sebastian/foaf
HTTP/1.1 200 OK
Date: Sun, 18 Dec 2011 10:09:13 GMT
Last-Modified: Sat, 17 Dec 2011 19:16:43 GMT
$ cwm http://www.trueg.de/sebastian/foaf --ntriples | grep cert
<http://www.trueg.de/sebastian/foaf#me> <http://www.w3.org/ns/auth/cert#key> _:L22C14 .
_:L22C14 <http://www.w3.org/ns/auth/cert#exponent> "65537"^^<http://www.w3.org/2001/XMLSchema#integer> .
_:L22C14 <http://www.w3.org/ns/auth/cert#modulus> "c7e391a372f193354c4bf63254516e951dae1167763aef8991f5d07732ba92e09e35944b88d36197aff5177eb7d3142ce083b37f8ac074a47a8eeb8325aef5308baf799852c340a102f09a52fd17ed13a2b3b09fc2a43b164c8815ecaab681961599aaa6826e68c58ac678da043e0a11723d239a153fb828fc801c0ea1689adcddb7a8b65b2a2b1fe688b79bff500ff8530fbac7609f6a97a51901f05e2e9a7998e34ba5f700c51fbfe97bb6332f438b885ca5641970739778e948798f26199c349d51df411dc9304bee1a31b09cbe291744ef78ecddcf4b99e615cdce660f58370f6bec58943f354acee283b8be09dd5f002b064c9533fd26993a5251e83439"^^<http://www.w3.org/2001/XMLSchema#hexBinary> .
But when I now look into my database to see what graph clerezza received I don't see anything. It's empty. It was not yesterday though... Perhaps you reconnected with a missing foaf file in between...
Your certificate also seems to be good.
Version: 3 (0x2)
Signature Algorithm: sha1WithRSAEncryption
Issuer: C=FR, ST=Essonne, O=webid.fcns.eu, CN=webid.fcns.eu/emailAddress=webid at fcns.eu
Not Before: Dec 16 18:56:36 2011 GMT
Not After : Dec 15 18:56:36 2012 GMT
Subject: C=FR, CN=Sebastian Trueg/emailAddress=sebastian at trueg.de
Subject Public Key Info:
Public Key Algorithm: rsaEncryption
Public-Key: (2048 bit)
Exponent: 65537 (0x10001)
X509v3 Basic Constraints:
OpenSSL Generated Certificate
X509v3 Subject Key Identifier:
X509v3 Authority Key Identifier:
X509v3 Subject Alternative Name:
email:sebastian at trueg.de, URI:http://www.trueg.de/sebastian/foaf#me
Signature Algorithm: sha1WithRSAEncryption
> So I tried to create a new profile for my daughter Clara, uploaded it to
> http://www.trueg.de/clara/foaf.ttl and used the WebID
> http://www.trueg.de/clara/foaf.ttl#me. Sadly this does not work either.
> The error is the same. But it also works in ODS.
yes, but I am sure clara will be happier if she does not have her WebID tied to one representation.
It would be best for long term if you used
or perhaps even
The spec was pointing at this. (But the link is not visible, so I'll fix it)
> Please let me know if you want me to try other things. SSL maybe?
SSL longer term is certainly a good idea. But the issue here is not SSL unless someone is man in the middle
attacking me and changing your rdf along the way. But from your test report it seems that that was not the case
as at the time my server was able to analyse your rdf.
I only recently rewrote clerezza to work with our new ontology, so that is why you are seeing
these problems. Clerezza does not have SPARQL either, so there are a lot of little
places there can be a bug. But it is odd that you stumbled on it, but not me before.
Still your turtle looks good, and we accept turtle... I'll think about this.
If you read the spec and you find things that you learnt through this conversation that would have helped
you were they in the spec, please let us know.
>> Social Web Architect
Social Web Architect
More information about the foaf-protocols