diff options
Diffstat (limited to 'https-cuts.txt')
| -rw-r--r-- | https-cuts.txt | 15 |
1 files changed, 15 insertions, 0 deletions
diff --git a/https-cuts.txt b/https-cuts.txt index f3ca627..3178c29 100644 --- a/https-cuts.txt +++ b/https-cuts.txt @@ -1,3 +1,18 @@ +Unused links: + +https://blog.mozilla.org/security/2015/04/30/deprecating-non-secure-http/ +https://lists.w3.org/Archives/Public/www-tag/2015Jan/0086.html +https://w3c.github.io/webappsec-subresource-integrity/#use-casesexamples +https://tools.ietf.org/html/draft-reschke-objsec-00 +http://ieeexplore.ieee.org/xpl/articleDetails.jsp?reload=true&arnumber=6454330 +https://bugzilla.mozilla.org/show_bug.cgi?id=1041087 +https://caddyserver.com/ +http://www.2rosenthals.net/wordpress/googles-https-everywhere-initiative-not-so-fast-994/ +http://andreasgal.com/2015/03/30/data-is-at-the-heart-of-search-but-who-has-access-to-it/ +https://codereview.chromium.org/1530403002/ + + + This is why the question Winer and others would like answered is so simple: why? Why should we invest all this effort to encrypt websites that are just archived flat HTML pages? |