Skip to content

Commit fa1db9a

Browse files
committed
Update 100_percent_https_roadmap.md
1 parent 7e17444 commit fa1db9a

File tree

1 file changed

+7
-3
lines changed

1 file changed

+7
-3
lines changed

admin/100_percent_https_roadmap.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,11 @@
11
100% HTTPS: Roadmap for the entire Web
22
======================================
33

4-
“Just turn on https” isn’t enough.
4+
Is “Just turn on TLS” and s/http/https/g good enough?
55
----------------------------------
66
* Mixed content and secure <--> insecure information flows can violate the invariants of secure contexts.
77
* Need a plan to manage upgrading static content, including URLs-as-data and URLs-as-stable-identifiers, to work with secure transports.
8+
* What would it look like if 'http' was a potentially secure scheme?
89

910
Terminology
1011
-----------
@@ -16,11 +17,11 @@ E.g.: HTTP GET/POST send data from an application to a resource, XHR reads data
1617
Starting Assumptions
1718
----------------------------------
1819
* Axiom 1: Users cannot meaningfully deal with nuanced security models. A resource is either secure or it is not.
19-
* Axiom 2: Secure means that the source of information is authenticated, and it has privacy and integrity guarantees in transit between the source and the user.
20+
* Axiom 2: Secure means that the source of information is authenticated and it has privacy and integrity guarantees in transit between the source and the user.
2021
* Axiom 3: (controversial?) We should not ask users to make exceptions or bypass security. (follows from Axiom 1)
2122
* Axiom 4: Applications must be able to require a security contract from user agents on behalf of users.
2223

23-
e.g. if Facebook is going to send a security token somewhere on your behalf, we will never do so over an insecure channel or one that is only “optimistically” secure.
24+
e.g. 4 if Facebook is going to send a security token somewhere on your behalf, it wants to be sure it will never do so over an insecure channel or one that is only “optimistically” secure.
2425

2526
The Invariants
2627
----------------------------------
@@ -134,6 +135,9 @@ What about localStorage, indexedDB?
134135
Other Issues
135136
----------
136137
* DTDs and Namespaces in XML
138+
139+
Grab bag
140+
---------
137141
* How do we protect anonymous expression on the web in a world of 100% authenticated content?
138142
- Are Let’s Encrypt and other free DV issuance enough?
139143

0 commit comments

Comments
 (0)