summaryrefslogtreecommitdiff
path: root/docs/technology/en.haml
diff options
context:
space:
mode:
Diffstat (limited to 'docs/technology/en.haml')
-rw-r--r--docs/technology/en.haml30
1 files changed, 0 insertions, 30 deletions
diff --git a/docs/technology/en.haml b/docs/technology/en.haml
deleted file mode 100644
index bc60a94..0000000
--- a/docs/technology/en.haml
+++ /dev/null
@@ -1,30 +0,0 @@
-%h1.first The Technology of LEAP
-
-%p The long term LEAP plan consists of a set of #{link 'communication services' => 'services'} built upon the core technologies detailed here.
-
-%p
- %b #{link 'Information Security' => 'infosec'}:
- An analysis of different approaches to information security and how the LEAP strategy compares.
-
-%p
- %b #{link 'Provider Platform' => 'platform'}:
- Turn-key automation for communication service providers.
-
-%p
- %b #{link 'LEAP Client' => 'client'}:
- Easy to use client for secure communication.
-
-%p
- %b #{link 'Secure Identity' => 'identity'}:
- Federated system to automate validation of cryptographic identity.
-
-%p
- %b #{link 'Map Resistant Routing' => 'routing'}:
- A system for message routing that is resistant to association mapping.
-
-%p
- %b #{link 'Critiques' => 'critiques'}:
- Anticipated critiques of the LEAP architecture.
-
-
--# https://guardianproject.info/wiki/Always_Secure_Messaging \ No newline at end of file