summaryrefslogtreecommitdiff
path: root/pages/docs/design
diff options
context:
space:
mode:
Diffstat (limited to 'pages/docs/design')
-rw-r--r--pages/docs/design/nicknym-draft.md4
-rw-r--r--pages/docs/design/nicknym.md2
-rw-r--r--pages/docs/design/soledad.md2
3 files changed, 4 insertions, 4 deletions
diff --git a/pages/docs/design/nicknym-draft.md b/pages/docs/design/nicknym-draft.md
index 9398a9f..e96ce96 100644
--- a/pages/docs/design/nicknym-draft.md
+++ b/pages/docs/design/nicknym-draft.md
@@ -85,7 +85,7 @@ There are a number of established methods for binding identifier to key:
* [X.509 Certificate Authority System](https://en.wikipedia.org/wiki/X.509)
* Trust on First Use (TOFU)
* Mail-back Verification
-* [Web of Trust (WOT)](http://en.wikipedia.org/wiki/Web_of_trust)
+* [Web of Trust (WOT)](https://en.wikipedia.org/wiki/Web_of_trust)
* [DNSSEC](https://en.wikipedia.org/wiki/Dnssec)
* [Shared Secret](https://en.wikipedia.org/wiki/Socialist_millionaire)
* [Network Perspective](http://convergence.io/)
@@ -156,7 +156,7 @@ For a long discussion of the simple thing, see [messaging list](https://moderncr
**WebID and Mozilla Persona**
-What about [WebID](http://www.w3.org/wiki/WebID) or [Mozilla Persona](https://www.mozilla.org/en-US/persona/)? These are both interesting standards for cryptographically proving identify, so why do we need something new?
+What about [WebID](https://www.w3.org/wiki/WebID) or [Mozilla Persona](https://www.mozilla.org/en-US/persona/)? These are both interesting standards for cryptographically proving identify, so why do we need something new?
These protocols, and the poorly conceived OpenID Connect, are designed to address a fundamentally different problem: authenticating a user to a website. The problem of authenticating users to one another requires a different architecture entirely. There are some similarities, however, and in the long run a Nicknym provider could also be a WebID and Mozilla Persona provider.
diff --git a/pages/docs/design/nicknym.md b/pages/docs/design/nicknym.md
index 3f94875..cb638ab 100644
--- a/pages/docs/design/nicknym.md
+++ b/pages/docs/design/nicknym.md
@@ -51,7 +51,7 @@ There are a number of established methods for binding identifier to key:
* [X.509 Certificate Authority System](https://en.wikipedia.org/wiki/X.509)
* Trust on First Use (TOFU)
* Mail-back Verification
-* [Web of Trust (WOT)](http://en.wikipedia.org/wiki/Web_of_trust)
+* [Web of Trust (WOT)](https://en.wikipedia.org/wiki/Web_of_trust)
* [DNSSEC](https://en.wikipedia.org/wiki/Dnssec)
* [Shared Secret](https://en.wikipedia.org/wiki/Socialist_millionaire)
* [Network Perspective](http://convergence.io/)
diff --git a/pages/docs/design/soledad.md b/pages/docs/design/soledad.md
index a0eeed4..d02ae7d 100644
--- a/pages/docs/design/soledad.md
+++ b/pages/docs/design/soledad.md
@@ -66,7 +66,7 @@ Related software
[Firefox Sync](https://wiki.mozilla.org/Services/Sync) - A client-encrypted data sync from Mozilla, designed to securely synchronize bookmarks and other browser settings.
-[U1DB](http://pythonhosted.org/u1db/) - Similar API as Soledad, without encryption.
+[U1DB](https://pythonhosted.org/u1db/) - Similar API as Soledad, without encryption.
Soledad protocol
===================================