From a69a87cdf29b2840a32b79afef584ef6d101c0c3 Mon Sep 17 00:00:00 2001 From: Tankred Hase Date: Sat, 11 Jan 2014 16:29:45 +0100 Subject: [PATCH] typo --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index b25040cf..6a627f08 100644 --- a/README.md +++ b/README.md @@ -28,7 +28,7 @@ OpenPGP.js currently only fully supports browsers that implement `window.crypto. It should be noted that browser based applications, following a [**host-based security**](https://www.schneier.com/blog/archives/2012/08/cryptocat.html) model, provide users with less security than installable apps with auditable static versions. This can be achieved by deploying your HTML5 app as a [Firefox](https://developer.mozilla.org/en-US/Marketplace/Publishing/Packaged_apps) or [Chrome](http://developer.chrome.com/apps/about_apps.html) packaged app. These runtimes typically also enforce a strict [Content Security Policy (CSP)](http://www.html5rocks.com/en/tutorials/security/content-security-policy/) to protect your users against [XSS](http://en.wikipedia.org/wiki/Cross-site_scripting). This [blogpost](http://tonyarcieri.com/whats-wrong-with-webcrypto) explains the trust model of the web quite well. -It is also recommended to set a strong passphrase that protects user's private key on disk. +It is also recommended to set a strong passphrase that protects the user's private key on disk. ## Development