-
Use Firefox Browser
-
Go to https://databox.me/ and get a username
-
Note down your username
-
Enter your name and in the Webid box enter : https://username.databox.me/profile/card#me
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| var fs = require("fs"); | |
| var forge = require('node-forge'); | |
| var debug = require('debug')('converter'); | |
| var BigInteger = forge.jsbn.BigInteger; | |
| // change as necessary | |
| var countryName = 'UK'; | |
| var domain = 'http://databox.me/'; | |
| var localityName = 'London'; | |
| var organizationName = 'databox.me'; |
- allow Key generation in chrome://settings/content
- register an account that will generate a cert - eg. https://databox.me/ creates user.crt
- on OSX
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| #!/usr/bin/env node | |
| var debug = require('debug')('hn') | |
| var request = require('request') | |
| debug('starting hn') | |
| var config = {} | |
| config.defaultStories = 5 |
What I think would be helpful would be a table of auth mechanisms, something like:
This table should be used as a rough guide, not as black and white
| Name | URI used | Verification | Required | Implemented |
|---|---|---|---|---|
| WebID TLS | WebID | TLS | Y | Y |
| Cookie | implied | Shared Secret | Y | Y |
| WebID RSA | WebID | Web Crypto API | N | Y |
| HTTP Signatures | Public Key | Web Crypto API | N | N |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| { | |
| "post_tweet_hook": "sleep 1 ; curl -H \"Content-Type: text/plain; charset=UTF-8\" --cert $CERT --key $CERT -X PUT --data-binary @/home/melvin/twtxt.txt https://melvin.databox.me/Public/twtxt/twtxt.txt", | |
| "user": "melvincarvalho", | |
| "twtfile": "/home/melvin/twtxt.txt", | |
| "limit_timeline": "20", | |
| "following": [ | |
| { | |
| "user": "twtxt", | |
| "uri": "https://buckket.org/twtxt_news.txt" | |
| } |
The following describes discovery in the SoLiD framework using HTTP link following aka "follow your nose".
The starting point of SoLiD discovery is a WebID user profile, which is a hash based URI, typically denoting a (FOAF) Agent. From this profile all of your storage can be found (discovery).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| <https://melvincarvalho.com/#me> <http://xmlns.com/foaf/0.1/account> <https://github.com/melvincarvalho> . |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| var fs = require("fs"); | |
| var forge = require('node-forge'); | |
| var login = 'melvincarvalho'; | |
| var pubkeyfile; | |
| var privkeyfile; | |
| var pemfile; | |
| // command line arguments |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| #!/usr/bin/env node | |
| // requires | |
| var forge = require('node-forge'); | |
| var fs = require("fs"); | |
| // init | |
| var sshpubkey = {}; | |
| var pubkey; |

