diff options
Diffstat (limited to 'template/news/2013-12-28-archived-typos-pkeys.html.j2')
-rw-r--r-- | template/news/2013-12-28-archived-typos-pkeys.html.j2 | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/template/news/2013-12-28-archived-typos-pkeys.html.j2 b/template/news/2013-12-28-archived-typos-pkeys.html.j2 new file mode 100644 index 00000000..a541ef94 --- /dev/null +++ b/template/news/2013-12-28-archived-typos-pkeys.html.j2 | |||
@@ -0,0 +1,16 @@ | |||
1 | {% extends "common/news.j2" %} | ||
2 | {% block body_content %} | ||
3 | <h1>Typo-Protected Public Keys</h1> | ||
4 | <p> | ||
5 | <b>This is an imported news item from the old Drupal GNUnet homepage.</b> | ||
6 | </p> | ||
7 | <p> | ||
8 | When users type in public keys (such as the 53-characters of a GNS zone), they might make typos. The usual way to fix typos is to add a checksum, further increasing the length of the sequence that has to be typed in. | ||
9 | <br> | ||
10 | We can fix this by including the checksum of the public key in the public key itself, simply by trying new private keys until the corresponding public key happens to have a checksum (over the other bits) in the bits designated for the checksum. If a checksum is 16 bits, we would only need to try 216 keys. The basic idea of brute-forcing keys to match a particular pattern <a href="https://web.archive.org/web/20141008173738/https://bitcointalk.org/index.php?topic=84569.0">was proposed before</a> for creating "vanity" public keys, but this might be another practical variant. | ||
11 | </p> | ||
12 | <p> | ||
13 | <b>Acknowledgements</b><br/> | ||
14 | The idea popped up in a discussion on the need for short public keys for GNS with Dan Bernstein and Tanja Lange at 30c3. | ||
15 | </p> | ||
16 | {% endblock body_content %} | ||