diff options
| author | elijah <elijah@riseup.net> | 2013-08-14 03:31:27 -0700 |
|---|---|---|
| committer | elijah <elijah@riseup.net> | 2013-08-14 03:31:27 -0700 |
| commit | 442b94d9599f73efa90de3f2740ec51c1692e2c8 (patch) | |
| tree | e4ba3a7fc39f44f15721dd1e18408b512350fa09 /docs | |
| parent | a8ac7369aaec2ad2a14d9e9a4abbfb88d497db5c (diff) | |
fix typo in limitations page
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/design/limitations.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/design/limitations.md b/docs/design/limitations.md index a49ab44..e61d1c3 100644 --- a/docs/design/limitations.md +++ b/docs/design/limitations.md @@ -10,7 +10,7 @@ Provider problems Meta-data can be recorded by the provider ------------------------------------------------- -Currently, the service provider is able to observe the meta-data routing information of messages in transit of their own users. This information is not stored, but a nefarious provider could observe this information in transit and record it. +Currently, the service provider is able to observe the meta-data routing information of messages in transit of their own users (email and chat). This information is not stored, but a nefarious provider could observe this information in transit and record it. We have several plans to eliminate this, but these are not part of the initial release. @@ -85,7 +85,7 @@ In order to shield the service provider from being pressured by a host governmen This is good for the provider, but not so good for LEAP, since this system could potentially place pressure on LEAP. Because LEAP does not have a provider-customer relationship with any user, LEAP cannot target compromised applications for particular users. LEAP could, however, introduce a backdoor in the client used by all users. -To prevent this, we place to adopt [Gitian](https://gitian.org/) or something equivalent. Gitian allows for a way to standardize the entire build environment and build process in order for third parties to be able to verify that the released binary application does indeed match the correct source code. +To prevent this, we plan to adopt [Gitian](https://gitian.org/) or something equivalent. Gitian allows for a way to standardize the entire build environment and build process in order for third parties to be able to verify that the released binary application does indeed match the correct source code. External authority problems ================================================= |