A user account is required in order to edit this wiki, but we've had to disable public user registrations due to spam.
To request an account, ask an autoconfirmed user on Chat (such as one of these permanent autoconfirmed members).
TLS: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
(→TLS) |
||
| Line 5: | Line 5: | ||
* Increased confidentiality (not perfect; domain is leaked, traffic analysis can still tell a great deal) | * Increased confidentiality (not perfect; domain is leaked, traffic analysis can still tell a great deal) | ||
* Service workers | * Service workers | ||
* Web Crypto (only Chrome requires this for now) | |||
* [http://www.infoq.com/articles/Web-Sockets-Proxy-Servers Reduced problems with proxy traversal] | * [http://www.infoq.com/articles/Web-Sockets-Proxy-Servers Reduced problems with proxy traversal] | ||
* [https://www.tbray.org/ongoing/When/201x/2012/12/02/HTTPS Tim Bray on why privacy should be on by default] | * [https://www.tbray.org/ongoing/When/201x/2012/12/02/HTTPS Tim Bray on why privacy should be on by default] | ||
Revision as of 08:10, 25 September 2014
TLS
- Integrity of content (no tampering possible)
- Protection of end user credentials
- Increased confidentiality (not perfect; domain is leaked, traffic analysis can still tell a great deal)
- Service workers
- Web Crypto (only Chrome requires this for now)
- Reduced problems with proxy traversal
- Tim Bray on why privacy should be on by default
- HTTPS is a ranking signal for Google
- Indie Web Camp on HTTPS
- How to switch to HTTPS for free
HSTS
- TLS: deploy HSTS TL;DR without HSTS your TLS deployment is not worth much