FOAF+SSL uses PKI standards ? usually thought of as hierarchical trust management tools ? in a decentralized web-of-trust way. The web of trust is built using semantic web vocabularies (particularly FOAF) published in RESTful manner to form [Linked Data].
Based on well known existing standards, FOAF+SSL is currently in development, and is being discussed on the FOAF protocols mailing list.
For the most recent description of the protocol, read the one-page ''FOAF+SSL: Adding Security to Open Distributed Social Networks''. For a more detailed explanation of how the authentication works, see ''FOAF+SSL: Creating a Web of Trust without Key Signing Parties''.
Automatic discovery of interpersonal trust relationships enables automatic application of appropriate permissions.
In other words, data owners can set fuzzy permissions like "only let my friends see this" or "only let my family edit this." Applications can discover the relationships between the data owner and the data requester/user, and permit (or disallow) any attempted actions, without needing the data owner to explicitly set permissions for each potential user.
One example might be a parent setting permissions on a photo gallery, to permit viewing only by "immediate family". The parent need not list each and every such relative specifically for this application -- and need not add new permissions for a new family member (whether by marriage, birth, or otherwise), though they do need to be added to the owner's FOAF. When a new user comes and asks to see the pictures, the gallery application would check the relationships declared by each person (the owner and the visitor), and if they matched up (in other words, the visitor could not get in simply by claiming a family relationship; the relationship must be confirmed by the owner's FOAF data), the pictures would be shown.
The FOAF+SSL consumer needs an x509 certificate with v3 extension "Subject Alternate Name". This attribute is used for the owner's Web ID. For testing purposes we used OpenSSL? demo CA to generate such certificates. If you are not using the OpenSSL? demo CA, you must first setup a self-signed CA; read OpenSSL? documents on how to do this.
- Add the following line to the
[usr_cert]section of the
- Set the environment variable
ALTNAMEto the owner's Web ID, e.g.,
- Make a self-signed certificate, e.g.,
$ CA.pl -newreq (follow the dialog) $ CA.pl -sign
- When asked to commit the certificate, make sure you see several lines above, like —
X509v3 Subject Alternative Name: URI:http://localhost/dataspace/person/myname#this
- If your browser wants a
PKCS#12bundle, you must make one —
$ openssl pkcs12 -export -in newcert.pem -inkey newkey.pem -out mycert.p12
mykey.pemfor example. The PEM format of the certificate will be needed below.
To enable the HTTPS listener, you will need another certificate. Existing certificates may not have Subject Alternate Name, so you may want to generate one as in the previous section.
- The next step is to move
cacert.peminto the server's working directory. In our test case, we put the keys in a '
keys' sub-directory, and added the following lines to the
section of the Virtuoso INI file,
SSLPort = 4443 SSLCertificate = ./keys/localhost.cert.pem SSLPrivateKey = ./keys/localhost.key.pem X509ClientVerifyCAFile = ./keys/localhost.ca.pem X509ClientVerify = 1 X509ClientVerifyDepth = 15
- Also in the Virtuoso INI file, in the
localhost:8890below) must be edited to correspond to the DNS-resolvable host name ("CNAME") of the Virtuoso host, combined with the
ServerPort?as set in the
section of the same INI file.
[URIQA] DynamicLocal = 1 DefaultHost = localhost:8890
For instance, if the CNAME of the host is
virtuoso.example.com, and the
DefaultHost?should be set to
[URIQA] DynamicLocal = 1 DefaultHost = virtuoso.example.com:4321
- Start the Virtuoso server, and look at the log file.
Once HTTPS is up, you should see something like —
HTTPS Using X509 Client CA .... HTTPS/X509 server online at 4443
- In the Preferences dialog, open the Advanced tab, and click the "View certificates" button.
- Click the "Add exception" button ,and enter the address of the HTTPS server you've just configured, i.e., https://virtuoso.example.com:4443/
- Click OK, and confirm the exception.
- Click to the "Your Certificates" tab, and import
- Log in to your ODS account, and edit your profile.
- Click to the Security Tab, and scroll to the bottom, where you will find the X.509 certificate entry area.
- Copy & paste the PEM format of the certificate (i.e., the content of
mykey.pem, from earlier).
- Press "Save Certificate" button, and you are set.
- Enter an ODS user's URI in the address bar, and the fun begins.
- You should see a protected document's URI.
Note that there is no specific "address" data seen:
- When clicked, the browser will ask the user to select a certificate (note: certificate details are erased in picture below).
- Now the protected document includes the private address data alongside the previously visible public data!