From da246d4a035c37a7c7bae3890aa92dc6d6e6e43b Mon Sep 17 00:00:00 2001 From: Tankred Hase Date: Sat, 13 Sep 2014 14:47:24 +0200 Subject: [PATCH] Update Readme for chrome.socket.secure --- README.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/README.md b/README.md index ed32b68..ea96681 100644 --- a/README.md +++ b/README.md @@ -19,8 +19,6 @@ We take the privacy of your data very seriously. Here are some of the technical * Like most native email clients whiteout mail uses raw [TCP sockets](http://developer.chrome.com/apps/socket.html) to communicate directly with your mail server via IMAP/SMTP. -* Mail server [SSL certificates are pinned](http://security.stackexchange.com/questions/29988/what-is-certificate-pinning) in order to protect against SSL certificate forgery and other man in the middle attacks. - * The app is deployed as a [Chrome Packaged App](https://developer.chrome.com/apps/about_apps.html) with [auditable static versions](https://github.com/whiteout-io/mail-html5/releases) in order to prevent [problems with host-based security](http://tonyarcieri.com/whats-wrong-with-webcrypto). * [Content Security Policy (CSP)](http://www.html5rocks.com/en/tutorials/security/content-security-policy/) is enforced to prevent injection attacks.