[foaf-protocols] This message should be signed
melvincarvalho at gmail.com
Sat Jun 20 10:58:12 CEST 2009
On Sat, Jun 20, 2009 at 10:48 AM, Story Henry<henry.story at bblfish.net> wrote:
> On 20 Jun 2009, at 10:26, Toby Inkster wrote:
>> On Sat, 2009-06-20 at 09:14 +0100, Toby Inkster wrote:
>>> This message is a test. It should be signed with my FOAF+SSL-enabled
>>> X.509 key.
>> Hmmm... but wasn't.
> I was talking to naxx at the metalabs.at in Vienna about foaf+ssl, and
> he was very interested in it for this exact purpose, as he is member
> of a group that has produced a pgp encrypted secure mail solution.
> Perhaps he has some ideas on how this could help.
This is great. I'll have to try out the email part.
SSL has been used for years in email, so this could be a great
standardisation. Also SSL is used in many other subsystems such as
SSH and more recently distributed source control. What would be great
would be a coming together of all these systems over X.509 and FOAF
such that, for example, you SSH to your unix terminal and it know your
public profile, you can use gitorious for file sharing, syncing and
source control, you can log in to your email, etc. etc.
Note also many of these systems simply store the public key server
side. Perhaps an idea to make a reverse lookup service so that you
can get from a public key to a profile page.
>> Some SSL error message came up in Evolution when sending it, but it
>> didn't give me the chance to stop it sending.
>> Oh well, the principle still seems sound. FOAF+SSL could provide us
>> a unified trust model for web and e-mail, which is a potential killer
>> feature over competing technologies (but not an ov:KillerGorilla).
> foaf-protocols mailing list
> foaf-protocols at lists.foaf-project.org
More information about the foaf-protocols