summaryrefslogtreecommitdiff
path: root/pages/docs/design
diff options
context:
space:
mode:
authorkwadronaut <kwadronaut@leap.se>2015-06-25 16:16:04 +0200
committerkwadronaut <kwadronaut@leap.se>2015-06-25 16:16:04 +0200
commitb759ae57556282619b09b855812832c57857c41a (patch)
treea805730094db17fae5649784b42d462f4441b2f9 /pages/docs/design
parentc301d101ad457bdfba10c7fa4e46ec5ad7aa337f (diff)
update a bunch of external links to https
Diffstat (limited to 'pages/docs/design')
-rw-r--r--pages/docs/design/nicknym-draft.md4
-rw-r--r--pages/docs/design/nicknym.md2
2 files changed, 3 insertions, 3 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/)