summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorelijah <elijah@riseup.net>2013-08-15 02:00:38 -0700
committerelijah <elijah@riseup.net>2013-08-15 02:00:38 -0700
commit7c1d9e0bbb0a2ca76b8f5455929d4ab1fc47299a (patch)
treef62b1f733db9e941d19ddfc4baea6d70519272d6
parent7d595b8265b739404a812c83ac1d7987ba9e6e23 (diff)
fix email page
-rw-r--r--config/locales/en.yml1
-rw-r--r--pages/home/en.haml1
-rw-r--r--pages/services/email/en.md18
3 files changed, 9 insertions, 11 deletions
diff --git a/config/locales/en.yml b/config/locales/en.yml
index b0b77a4..2959b55 100644
--- a/config/locales/en.yml
+++ b/config/locales/en.yml
@@ -19,7 +19,6 @@ en:
voice: "Voice"
files: "Files"
client: "LEAP Client"
- infosec: "Information Security"
cloud: "Secure Cloud"
identity: "Identity"
routing: "Routing"
diff --git a/pages/home/en.haml b/pages/home/en.haml
index b84377f..92dd2db 100644
--- a/pages/home/en.haml
+++ b/pages/home/en.haml
@@ -1,5 +1,4 @@
%p.bigger.first
- %b Bring fire to the people.
LEAP is a non-profit dedicated to giving all internet users access to secure communication. Our focus is on adapting encryption technology to make it easy to use and widely available. #{link 'More about LEAP ยป' => 'about-us'}
.row-fluid.p
diff --git a/pages/services/email/en.md b/pages/services/email/en.md
index e333c56..95353b7 100644
--- a/pages/services/email/en.md
+++ b/pages/services/email/en.md
@@ -13,7 +13,7 @@ The LEAP approach to email is to support communication with the legacy email inf
Above all else, our focus is on creating a user experience that is as easy and troublefree as possible while still ensuring a very high level of security.
-### How it works
+## How it works
When a service provider runs the LEAP platform, their users can access secure email in three steps:
@@ -23,26 +23,26 @@ When a service provider runs the LEAP platform, their users can access secure em
The Bitmask application acts as a "proxy" between the service provider and the mail client. It handles all the encryption and data synchronization.
-### Immediate benefits of using LEAP email
+## Immediate benefits of using LEAP email
Email features include:
* LEAP encrypted email is easy to use while still being backward compatible with the existing OpenPGP protocol for secure email.
* All incoming email is automatically encrypted before being stored, so only you can read it (including meta-data).
* Whenever possible, outgoing email is automatically encrypted so that only the recipients can read it (if a valid OpenPGP public keys can be discovered for the recipients). This encryption takes place on the user's device.
-* OpenPGP public keys are #{link 'automatically discovered and validated' => 'nicknym'}, allowing you to have confidence your communication is confidential and with the correct person (without the headache of typical key signing).
+* OpenPGP public keys are [automatically discovered and validated](/nicknym), allowing you to have confidence your communication is confidential and with the correct person (without the headache of typical key signing).
* The user does not need to worry about key management. Their keys are always kept up-to-date on every device.
* The user is able to use any email client of their choice (e.g. Thunderbird, Apple Mail, Outlook).
* When disconnected from the internet, the user can still interact with a local copy of all their mail. When the internet connect is available again, all their changes will get synchronized with the server storage and to their other devices.
General security features of the Bitmask application include:
-* All stored data is encrypted, including local data and cloud backups. This encryption always #{link "takes place on the user's device" => 'soledad'}, so the service provider cannot read your stored data.
-* Although you specify a username and password to login, your #{link 'password is never communicated to the provider' => 'https://en.wikipedia.org/wiki/Secure_Remote_Password_protocol'}.
-* If you download the Bitmask application from #{link 'downloads.leap.se' => 'https://downloads.leap.se'}, your service provider cannot add a backdoor to compromise your security.
+* All stored data is encrypted, including local data and cloud backups. This encryption always [takes place on the user's device](/soledad), so the service provider cannot read your stored data.
+* Although you specify a username and password to login, your [password is never communicated to the provider](https://en.wikipedia.org/wiki/Secure_Remote_Password_protocol).
+* If you download the Bitmask application from [downloads.leap.se](https://downloads.leap.se), your service provider cannot add a backdoor to compromise your security.
* The Bitmask application is always kept up to date with the latest security patches (coming soon).
-### Long term benefits when two LEAP compatible providers talk to one another
+## Long term benefits when two LEAP compatible providers talk to one another
One of the fundamental problems with email is that the meta-data routing information is exposed as cleartext. Encrypting a message with OpenPGP or S/MIME does nothing to help with this.
@@ -55,7 +55,7 @@ For now, LEAP addresses these problems with two enhancements when two compatible
This approach is effective against external network observers, but does not protect the meta-data from the service providers themselves. Also, it does not, by itself, protect against more advanced attacks involving timing and traffic analysis.
-In the long term, we plan to adopt one of several different schemes for #{link 'securely routing meta-data' => 'routing'}.
+In the long term, we plan to adopt one of several different schemes for [securely routing meta-data](routing).
## Limitations
@@ -66,4 +66,4 @@ In the long term, we plan to adopt one of several different schemes for #{link '
* We do not plan to support key revocation. Instead, we plan to migrate to shorter and shorter lived keys, as practical.
* With the current implementation, a compromised or nefarious service provider can still gather incoming messages that are not encrypted and meta-data routing information. As more users and providers adopt secure email, many of these problems will go away.
-For more details, please see #{link 'known limitations' => 'limitations'}. \ No newline at end of file
+For more details, please see [known limitations](limitations). \ No newline at end of file