summaryrefslogtreecommitdiff
path: root/pages/services/technology/en.haml
diff options
context:
space:
mode:
authorelijah <elijah@riseup.net>2013-02-12 21:30:06 -0800
committerelijah <elijah@riseup.net>2013-02-12 21:30:06 -0800
commit9399eb08466894ea335d8fa7d43ebf28759c1ab3 (patch)
treef0d5404034e313df5df6d20583a71397ae027f0c /pages/services/technology/en.haml
parentb8e6173d61fc213f7c065aaffdde690bc2b4bc50 (diff)
moved around some pages.
Diffstat (limited to 'pages/services/technology/en.haml')
-rw-r--r--pages/services/technology/en.haml30
1 files changed, 30 insertions, 0 deletions
diff --git a/pages/services/technology/en.haml b/pages/services/technology/en.haml
new file mode 100644
index 0000000..bc60a94
--- /dev/null
+++ b/pages/services/technology/en.haml
@@ -0,0 +1,30 @@
+%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