TLS - Revision history

Annevk: /* HSTS */

2014-10-15T08:21:52Z

HSTS

← Older revision		Revision as of 08:21, 15 October 2014
Line 22:		Line 22:

	* [https://annevankesteren.nl/2014/09/tls-hsts TLS: deploy HSTS] TL;DR without HSTS your TLS deployment is not worth much		* [https://annevankesteren.nl/2014/09/tls-hsts TLS: deploy HSTS] TL;DR without HSTS your TLS deployment is not worth much
			* https://www.eff.org/deeplinks/2014/02/websites-hsts

Annevk at 08:55, 27 September 2014

2014-09-27T08:55:50Z

← Older revision		Revision as of 08:55, 27 September 2014
Line 17:		Line 17:
	* [https://indiewebcamp.com/HTTPS#Why Indie Web Camp on HTTPS]		* [https://indiewebcamp.com/HTTPS#Why Indie Web Camp on HTTPS]
	* [https://konklone.com/post/switch-to-https-now-for-free How to switch to HTTPS for free]		* [https://konklone.com/post/switch-to-https-now-for-free How to switch to HTTPS for free]
	* [https://wiki.mozilla.org/Security/Server_Side_TLS Mozilla ~~recommend~~ server configurations]		* [https://wiki.mozilla.org/Security/Server_Side_TLS Mozilla recommended server configurations]

	== HSTS ==		== HSTS ==

	* [https://annevankesteren.nl/2014/09/tls-hsts TLS: deploy HSTS] TL;DR without HSTS your TLS deployment is not worth much		* [https://annevankesteren.nl/2014/09/tls-hsts TLS: deploy HSTS] TL;DR without HSTS your TLS deployment is not worth much

Annevk at 08:55, 27 September 2014

2014-09-27T08:55:32Z

← Older revision		Revision as of 08:55, 27 September 2014
Line 17:		Line 17:
	* [https://indiewebcamp.com/HTTPS#Why Indie Web Camp on HTTPS]		* [https://indiewebcamp.com/HTTPS#Why Indie Web Camp on HTTPS]
	* [https://konklone.com/post/switch-to-https-now-for-free How to switch to HTTPS for free]		* [https://konklone.com/post/switch-to-https-now-for-free How to switch to HTTPS for free]
			* [https://wiki.mozilla.org/Security/Server_Side_TLS Mozilla recommend server configurations]

	== HSTS ==		== HSTS ==

	* [https://annevankesteren.nl/2014/09/tls-hsts TLS: deploy HSTS] TL;DR without HSTS your TLS deployment is not worth much		* [https://annevankesteren.nl/2014/09/tls-hsts TLS: deploy HSTS] TL;DR without HSTS your TLS deployment is not worth much

Annevk: /* TLS */

2014-09-25T08:52:35Z

TLS

← Older revision		Revision as of 08:52, 25 September 2014
Line 4:		Line 4:
	* Protection of end user credentials		* Protection of end user credentials
	* 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		* Access to new platform features
	* Web Crypto (only Chrome requires TLS for now)		** Service workers
			** Push API
			** Subresource Integrity
			** [https://html.spec.whatwg.org/multipage/forms.html#dom-form-requestautocomplete requestAutocomplete()]
			** WebRTC (maybe)
			** Web Crypto (only Chrome requires TLS for now)
			** Hopefully getUserMedia() and geolocation down the line (mistakenly allowed, will probably have non-TLS deprecation period before disabling there)
	* [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]

Annevk: /* TLS */

2014-09-25T08:10:36Z

TLS

← Older revision		Revision as of 08:10, 25 September 2014
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)		* Web Crypto (only Chrome requires TLS 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]

Annevk: /* TLS */

2014-09-25T08:10:15Z

TLS

← Older revision		Revision as of 08:10, 25 September 2014
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]

Zcorpan at 09:45, 24 September 2014

2014-09-24T09:45:58Z

← Older revision		Revision as of 09:45, 24 September 2014
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
	* ~~Reduced problems with proxy traversal~~ http://www.infoq.com/articles/Web-Sockets-Proxy-Servers		* [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		* [https://www.tbray.org/ongoing/When/201x/2012/12/02/HTTPS Tim Bray on why privacy should be on by default]
	* http://googleonlinesecurity.blogspot.co.uk/2014/08/https-as-ranking-signal_6.html		* [http://googleonlinesecurity.blogspot.co.uk/2014/08/https-as-ranking-signal_6.html HTTPS is a ranking signal for Google]
	* https://indiewebcamp.com/HTTPS#Why		* [https://indiewebcamp.com/HTTPS#Why Indie Web Camp on HTTPS]
	* https://konklone.com/post/switch-to-https-now-for-free		* [https://konklone.com/post/switch-to-https-now-for-free How to switch to HTTPS for free]

	== HSTS ==		== HSTS ==

	* https://annevankesteren.nl/2014/09/tls-hsts TL;DR without HSTS your TLS deployment is not worth much		* [https://annevankesteren.nl/2014/09/tls-hsts TLS: deploy HSTS] TL;DR without HSTS your TLS deployment is not worth much

MikeSmith: /* TLS */ Reduced problems with proxy traversal

2014-09-24T06:58:32Z

TLS: Reduced problems with proxy traversal

← Older revision		Revision as of 06:58, 24 September 2014
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
			* Reduced problems with proxy traversal http://www.infoq.com/articles/Web-Sockets-Proxy-Servers
	* https://www.tbray.org/ongoing/When/201x/2012/12/02/HTTPS		* https://www.tbray.org/ongoing/When/201x/2012/12/02/HTTPS
	* http://googleonlinesecurity.blogspot.co.uk/2014/08/https-as-ranking-signal_6.html		* http://googleonlinesecurity.blogspot.co.uk/2014/08/https-as-ranking-signal_6.html

Annevk: /* TLS */

2014-09-23T18:25:18Z

TLS

← Older revision		Revision as of 18:25, 23 September 2014
Line 3:		Line 3:
	* Integrity of content (no tampering possible)		* Integrity of content (no tampering possible)
	* Protection of end user credentials		* Protection of end user credentials
	* Increased ~~privacy~~ (not perfect; domain is leaked, ~~package~~ 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
	* https://www.tbray.org/ongoing/When/201x/2012/12/02/HTTPS		* https://www.tbray.org/ongoing/When/201x/2012/12/02/HTTPS

Annevk: Created page with "== TLS == * Integrity of content (no tampering possible) * Protection of end user credentials * Increased privacy (not perfect; domain is leaked, package analysis can still t..."

2014-09-23T17:16:04Z

Created page with "== TLS == * Integrity of content (no tampering possible) * Protection of end user credentials * Increased privacy (not perfect; domain is leaked, package analysis can still t..."

New page

== TLS ==

* Integrity of content (no tampering possible)
* Protection of end user credentials
* Increased privacy (not perfect; domain is leaked, package analysis can still tell a great deal)
* Service workers
* https://www.tbray.org/ongoing/When/201x/2012/12/02/HTTPS
* http://googleonlinesecurity.blogspot.co.uk/2014/08/https-as-ranking-signal_6.html
* https://indiewebcamp.com/HTTPS#Why
* https://konklone.com/post/switch-to-https-now-for-free

== HSTS ==

* https://annevankesteren.nl/2014/09/tls-hsts TL;DR without HSTS your TLS deployment is not worth much