summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorelijah <elijah@riseup.net>2013-08-22 15:32:41 -0700
committerelijah <elijah@riseup.net>2013-08-22 15:32:41 -0700
commit70ff05ae2eb828a0473de7b76305a75043088fe7 (patch)
tree76203b4a8889f2ec1e0fdba3e90ff1a9623c710a
parentfc08bfa3e34c5abe91f44b936b54fd7e71b1ea30 (diff)
added big seven post
-rw-r--r--pages/about-us/news/2012/the-big-seven/en.haml7
1 files changed, 7 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
new file mode 100644
index 0000000..7d24be0
--- /dev/null
+++ b/pages/about-us/news/2012/the-big-seven/en.haml
@@ -0,0 +1,7 @@
+- @title = "The big seven hard problems in secure communication"
+- @author = "Elijah"
+- @posted_at = "2013-08-22"
+- @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