summaryrefslogtreecommitdiff
path: root/pages
diff options
context:
space:
mode:
authorelijah <elijah@riseup.net>2013-08-22 15:50:27 -0700
committerelijah <elijah@riseup.net>2013-08-22 15:50:27 -0700
commit25e8050ed8f9c627493b51f8e9c9a730c71ddcd4 (patch)
tree6de9475b471748639379205d82e39c9eb3e03c06 /pages
parent70ff05ae2eb828a0473de7b76305a75043088fe7 (diff)
css fixes
Diffstat (limited to 'pages')
-rw-r--r--pages/about-us/news/2012/the-big-seven/en.haml3
1 files changed, 3 insertions, 0 deletions
diff --git a/pages/about-us/news/2012/the-big-seven/en.haml b/pages/about-us/news/2012/the-big-seven/en.haml
index 7d24be0..b8b6fa4 100644
--- a/pages/about-us/news/2012/the-big-seven/en.haml
+++ b/pages/about-us/news/2012/the-big-seven/en.haml
@@ -1,7 +1,10 @@
- @title = "The big seven hard problems in secure communication"
- @author = "Elijah"
- @posted_at = "2013-08-22"
+- @more = true
+- @layout = 'application'
- @preview = capture_haml do
If you take a survey of interesting initiatives to create more secure communication, a pattern starts to emerge: it seems that any serious attempt to build a system for secure message communication eventually comes up against the following list of seven hard problems. These problems appear to be present regardless of which architectural approach you take (centralized authority, distributed peer-to-peer, or federated servers).
+
= act_as('hard-problems') \ No newline at end of file