aboutsummaryrefslogtreecommitdiff
path: root/source/blog/2014-11-28-going-diceware.md
diff options
context:
space:
mode:
authorZhiming Wang <zmwangx@gmail.com>2016-01-08 11:21:54 -0800
committerZhiming Wang <zmwangx@gmail.com>2016-01-08 11:21:54 -0800
commit6053d313ce3abe876c7d05574effab438ce5e410 (patch)
tree0ff96b8118d625e57123a42e6582b9f0e0575583 /source/blog/2014-11-28-going-diceware.md
parentd484ca3946753a6dda8f37bb3a2529fc06294fc5 (diff)
downloadmy_new_personal_website-6053d313ce3abe876c7d05574effab438ce5e410.tar.xz
my_new_personal_website-6053d313ce3abe876c7d05574effab438ce5e410.zip
Markdown source files: Use ... to end YAML metadata block
Also add a newline after the metadata block. ... is easier on markdown-mode; if --- is used, the line immediately above it will be treated as a setext header and highlighted, which isn't so easy on the eyes.
Diffstat (limited to '')
-rw-r--r--source/blog/2014-11-28-going-diceware.md3
1 files changed, 2 insertions, 1 deletions
diff --git a/source/blog/2014-11-28-going-diceware.md b/source/blog/2014-11-28-going-diceware.md
index d9dfb860..e2d2b06c 100644
--- a/source/blog/2014-11-28-going-diceware.md
+++ b/source/blog/2014-11-28-going-diceware.md
@@ -2,7 +2,8 @@
title: "Going Diceware"
date: 2014-11-28T19:05:59-0800
date_display: November 28, 2014
----
+...
+
Today I'm officially going [Diceware](http://world.std.com/~reinhold/diceware.html). I published my simple C implementation of diceware on [GitHub](https://github.com/zmwangx/diceware).
I've been using 1Password for a couple years now, and I've always been a bit worried about my master password. It's a ~30 byte monster with uppercase, lowercase letters, numbers, and special symbols. By any measure it is very safe. The problem is there are (extremely) personal things in there. I assembled several unrelated things that I (secretly) hold dearest to my heart, obfuscated them with rules not found in best64, and mixed with semi-gibberish. My daily login password is a combo similar in nature, with less obfuscation to facilitate typing. People who dig really deep into my identity might be able to compromise it (or not); I'm afraid that I'm more predictable than I thought I was. I know, the worry is pretty much unwarranted, as I’m not likely the target of a focused attack — I’m neither rich nor equipped with sensitive information or power, and for wide-range exploits, 99.9% of people are lower-hanging fruits. Even for a targeted attack, [xkcd 538: Security](http://xkcd.com/538/) broke a crypto nerd’s imagination with a $5 wrench. However, a geek is a geek, you can’t block a geek’s imagination.