diff options
| author | kali <kali@katsi> | 2014-08-28 18:25:55 -0500 |
|---|---|---|
| committer | kali <kali@katsi> | 2014-08-28 19:25:10 -0500 |
| commit | 381d43a2c0398d90511e9db757f29883f8a1fa73 (patch) | |
| tree | 2a802048c031af65fa3a32c183a5869771a2a0bd /overview/en.html | |
| parent | 007bab4fbceaeb0722e3625412ca926a4fb1a42a (diff) | |
overview/es.html + minor updates to en.html
Diffstat (limited to 'overview/en.html')
| -rw-r--r-- | overview/en.html | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/overview/en.html b/overview/en.html index 43af1e2..d19db34 100644 --- a/overview/en.html +++ b/overview/en.html @@ -197,7 +197,7 @@ At LEAP, we have worked to solve the availability problem with a system we call <section> <h2>Update problem</h2> <blockquote style="margin-bottom:2em;">Almost universally, software updates are done in ways that invite attacks and device compromises</blockquote> - <li class="fragment">Thandy (thanks, Tor!)</li> + <li class="fragment">TUF (thanks, Thandy/Tor!)</li> <aside class="notes" data-markdown> The sad state of update security is especially troublesome because update attacks can now be purchased off the shelf by repressive regimes. The problem of software update is particular bad on desktop platforms. In the case of mobile and HTML5 apps, the vulnerabilities are not as dire, but the issues are also harder to fix. @@ -349,8 +349,8 @@ $ leap --yes deploy <section> <section> <h2>Provider Online</h2> - <p><a href="https://bitmask.net">Bitmask.net</a> - Reference Provider of LEAP </p> - <p>soon to be open for beta testers</p> + <p><a href="https://demo.bitmask.net">demo.bitmask.net</a> - Reference Provider of LEAP </p> + <p>already open for beta testers</p> </section> <section> |