- From: Kingsley Idehen <kidehen@openlinksw.com>
- Date: Tue, 17 Jul 2012 15:15:58 -0400
- To: public-rww@w3.org
- Message-ID: <5005B9EE.1040309@openlinksw.com>
On 7/17/12 3:01 PM, Henry Story wrote: > > On 17 Jul 2012, at 20:50, Henry Story wrote: > >> >> On 17 Jul 2012, at 20:20, Jürgen Jakobitsch wrote: >> >>> ok thanks henry... >>> >>> i think i can live with that... >> >> I wonder if it is not just a case of these mailing lists breaking the >> signature by altering the mail content. See if you can send me >> directly - without passing through the list an e-mail. > > Thanks Jürgen. That's it. Here is the mail you sent me. It shows up > correctly. > That is another reason for RESTful mail over TLS. Essentially any > system where you allow an intermediary to handle your content, is an > opportunity for that intermediary to alter it. And they will always > find good reasons to alter it a bit ( copyright ) then more, then more... But, you can't push this as an alternative to Email, just yet. Let's fix Email with WebID as it is still the ultimate WebID vector. At this point, we've been able to verify the following re. WebID bootstrap: WebID+S/MIME == killer. WebID+IMAP4 == killer. WebID+WebDAV == killer. WebID+CalDAV == killer. WebID+CardDAV == killer. WebID+OpenID == killer. Kingsley > > Henry > >> >> Henry >> >> >> >>> >>> wkr turnguard >> >> Social Web Architect >> http://bblfish.net/ >> > > Social Web Architect > http://bblfish.net/ > -- Regards, Kingsley Idehen Founder & CEO OpenLink Software Company Web: http://www.openlinksw.com Personal Weblog: http://www.openlinksw.com/blog/~kidehen Twitter/Identi.ca handle: @kidehen Google+ Profile: https://plus.google.com/112399767740508618350/about LinkedIn Profile: http://www.linkedin.com/in/kidehen
Attachments
- application/pkcs7-signature attachment: S/MIME Cryptographic Signature
Received on Tuesday, 17 July 2012 19:15:47 UTC