summaryrefslogtreecommitdiff
path: root/_posts
diff options
context:
space:
mode:
authorBrian Picciano <bgp2396@bellsouth.net>2013-11-23 11:38:58 -0500
committerBrian Picciano <bgp2396@bellsouth.net>2013-11-23 11:38:58 -0500
commitca8a5da6113277d6cac8085b9a26f02ae7d009ad (patch)
tree3148c1d776474677bce7ee7adfb8c43558d8374b /_posts
parent5b0c6a37394f3d5676ac6bc0250f99d7ddf59b21 (diff)
typo in namecoin post
Diffstat (limited to '_posts')
-rw-r--r--_posts/2013-10-25-namecoind-ssl.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/_posts/2013-10-25-namecoind-ssl.md b/_posts/2013-10-25-namecoind-ssl.md
index c5ad7e8..1ee2ab6 100644
--- a/_posts/2013-10-25-namecoind-ssl.md
+++ b/_posts/2013-10-25-namecoind-ssl.md
@@ -8,7 +8,7 @@ system where a user can upload their already encrypted content to our storage
system and be 100% confident that their data can never be decrypted by anyone
but them.
-On of the main problems with this approach is that the client has to be sure
+One of the main problems with this approach is that the client has to be sure
that the code that's being run in their browser is the correct code; that is,
that they aren't the subject of a man-in-the-middle attack where an attacker is
turning our strong encryption into weak encryption that they could later break.