11.xhtml 11 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150
  1. <?xml version="1.0" encoding="utf-8"?>
  2. <!--
  3. h t t :: / / t /
  4. h t t :: // // t //
  5. h ttttt ttttt ppppp sssss // // y y sssss ttttt //
  6. hhhh t t p p s // // y y s t //
  7. h hh t t ppppp sssss // // yyyyy sssss t //
  8. h h t t p s :: / / y .. s t .. /
  9. h h t t p sssss :: / / yyyyy .. sssss t .. /
  10. <https://y.st./>
  11. Copyright © 2015 Alex Yst <mailto:copyright@y.st>
  12. This program is free software: you can redistribute it and/or modify
  13. it under the terms of the GNU General Public License as published by
  14. the Free Software Foundation, either version 3 of the License, or
  15. (at your option) any later version.
  16. This program is distributed in the hope that it will be useful,
  17. but WITHOUT ANY WARRANTY; without even the implied warranty of
  18. MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
  19. GNU General Public License for more details.
  20. You should have received a copy of the GNU General Public License
  21. along with this program. If not, see <https://www.gnu.org./licenses/>.
  22. -->
  23. <!DOCTYPE html>
  24. <html xmlns="http://www.w3.org/1999/xhtml">
  25. <head>
  26. <base href="https://y.st./en/weblog/2015/03-March/11.xhtml" />
  27. <title>Twitter and pinentry vex me, but email (including PGP) is up &lt;https://y.st./en/weblog/2015/03-March/11.xhtml&gt;</title>
  28. <link rel="icon" type="image/png" href="/link/CC_BY-SA_4.0/y.st./icon.png" />
  29. <link rel="stylesheet" type="text/css" href="/link/basic.css" />
  30. <link rel="stylesheet" type="text/css" href="/link/site-specific.css" />
  31. <script type="text/javascript" src="/script/javascript.js" />
  32. <meta name="viewport" content="width=device-width" />
  33. </head>
  34. <body>
  35. <nav>
  36. <p>
  37. <a href="/en/">Home</a> |
  38. <a href="/en/a/about.xhtml">About</a> |
  39. <a href="/en/a/contact.xhtml">Contact</a> |
  40. <a href="/a/canary.txt">Canary</a> |
  41. <a href="/en/URI_research/"><abbr title="Uniform Resource Identifier">URI</abbr> research</a> |
  42. <a href="/en/opinion/">Opinions</a> |
  43. <a href="/en/coursework/">Coursework</a> |
  44. <a href="/en/law/">Law</a> |
  45. <a href="/en/a/links.xhtml">Links</a> |
  46. <a href="/en/weblog/2015/03-March/11.xhtml.asc">{this page}.asc</a>
  47. </p>
  48. <hr/>
  49. <p>
  50. Weblog index:
  51. <a href="/en/weblog/"><abbr title="American Standard Code for Information Interchange">ASCII</abbr> calendars</a> |
  52. <a href="/en/weblog/index_ol_ascending.xhtml">Ascending list</a> |
  53. <a href="/en/weblog/index_ol_descending.xhtml">Descending list</a>
  54. </p>
  55. <hr/>
  56. <p>
  57. Jump to entry:
  58. <a href="/en/weblog/2015/03-March/07.xhtml">&lt;&lt;First</a>
  59. <a rel="prev" href="/en/weblog/2015/03-March/10.xhtml">&lt;Previous</a>
  60. <a rel="next" href="/en/weblog/2015/03-March/12.xhtml">Next&gt;</a>
  61. <a href="/en/weblog/latest.xhtml">Latest&gt;&gt;</a>
  62. </p>
  63. <hr/>
  64. </nav>
  65. <header>
  66. <h1>Twitter and pinentry vex me, but email (including <abbr title="Pretty Good Privacy">PGP</abbr>) is up</h1>
  67. <p>Day 00004: Wednesday, 2015 March 11</p>
  68. </header>
  69. </p>
  70. I registered an account with <a href="http://freeola.com/">Freeola</a> today, thinking I could set up email at my own domain through them.
  71. However, it seems they only offer that service for domains registered through them.
  72. Even if I wanted to transfer my domain to Freeola, which I don&apos;t, Freeola does not support <code>//st.</code> domains.
  73. </p>
  74. </p>
  75. I have still not received a response from Zoho, but I decided to try again to register there.
  76. Registration is back to being functional.
  77. So now, I have email up and running.
  78. </p>
  79. </p>
  80. The main reason I needed to get my email account set up so quickly is that without an email address, you can&apos;t register accounts in most places.
  81. Now that I have email access, I began setting up accounts.
  82. First, I tried to register an account at the <a href="ircs://volatile.club:6697/">Volatile Club</a>.
  83. However, services are currently down.
  84. Next, I registered at <a href="ircs://irc.oftc.net:6697/">OFTC</a>.
  85. After that, I thought a bit, and decided to get onto Twitter.
  86. It&apos;s a decent source of quick news for when I&apos;m on my break at work.
  87. However, Twitter does not seem to like me.
  88. They locked up my account within about ten minutes, and I hadn&apos;t even done anything.
  89. I couldn&apos;t tweet to Twitter support with my Twitter account on lockdown, so I decided to try email support, which meant I needed to get my <abbr title="Pretty Good Privacy">PGP</abbr> key set up.
  90. </p>
  91. </p>
  92. And cue more technical difficulties.
  93. As you&apos;ve no doubt guessed from my previous entries, I rely on a password database application called KeePassX.
  94. I don&apos;t actually know any of my passwords, they are all stored in an encrypted database, and I paste them into whatever application is asking for a given password.
  95. Enigmail refuses to allow me to paste the password needed to use my <abbr title="Pretty Good Privacy">PGP</abbr> key! I ended up sending the letter without signing it because I thought it would take at least until tomorrow to fix the problem.
  96. </p>
  97. </p>
  98. I tried to register at SourceForge, because the Enigmail forums are hosted there.
  99. No dice.
  100. I wanted to report the issue there and find out for sure if it was an accidental bug in need of fixing (similar to the bug in Irrlicht that prevents pasting text into Minetest) or an intentional anti-feature.
  101. With nowhere else to turn on the Enigmail issue, I decided to ask around in <a href="ircs://irc.oftc.net:6697/%23nottor">#nottor</a> and see if anyone there knew of a better email client and/or plugin for sending <abbr title="Pretty Good Privacy">PGP</abbr>-encrypted/signed email.
  102. Instead of recommending a new mail setup, cacahuatl showed me <a href="http://blog.philippbeck.net/security/enigmail-pinentry-paste-problem-thunderbird-gpg-gnupg-163">how to trick Enigmail into accepting the password</a>! Additionally, it seems that the issue <a href="https://bugs.launchpad.net/ubuntu/+source/pinentry/+bug/326132">is an intentional anti-feature</a>, not a bug.
  103. This auto-type feature of KeePassX is great news though! Using this same feature that bypasses Enigmail&apos;s anti-feature, I can also work around Irrlicht&apos;s bug.
  104. I can now store my Minetest passwords in my KeePassX database.
  105. </p>
  106. </p>
  107. At work today, I learned that both the government and criminals have access to these scary devices called &quot;<abbr title="international mobile subscriber identity">IMSI</abbr>-Catchers&quot;.
  108. These devices are used for man-in-the-middle attacks against mobile devices.
  109. They pretend to be legitimate cell towers, capturing and tracking traffic and device information.
  110. Law enforcement uses this data to take roll at protests, for example, and <a href="https://firstlook.org/theintercept/2014/02/10/the-nsas-secret-role/">the <abbr title="National Security Agency">NSA</abbr> uses it to track targets to be taken out</a>.
  111. Criminals use this to steal credit card numbers and passwords.
  112. The government&apos;s use of this technology is much scarier.
  113. All my traffic is run encrypted through <abbr title="The Onion Router">Tor</abbr>, so credit card information and passwords cannot be stolen locally.
  114. But tracking by the government for their evil purposes is still a possibility.
  115. I doubt the government would bomb me, honestly.
  116. I&apos;m not a threat to national security and they don&apos;t need any more bad <abbr title="public relations">PR</abbr>.
  117. But head counts are a realistic invasion of privacy.
  118. I suggest everyone use a prepaid anonymous <abbr title="subscriber identity module">SIM</abbr> card if they have a mobile device, and install <a href="https://secupwn.github.io/Android-IMSI-Catcher-Detector/">Android <abbr title="international mobile subscriber identity">IMSI</abbr>-Catcher Detector</a>.
  119. </p>
  120. </p>
  121. We got a spammer in <a href="ircs://irc.oftc.net:6697/%23tor">#tor</a>, repeatedly asking <q>WHAT IS THE FUTURE OF TOR? WHATS PLANNED FOR 2016?</q> in full capitals and pinging everyone.
  122. One thing led to another, and arma said a way we could all help prevent this sort of spam was by answering <abbr title="The Onion Router">Tor</abbr>-related questions online.
  123. I took a look at the linked site, and saw a very interesting one: <a href="https://tor.stackexchange.com/questions/3274/why-does-claws-mail-included-in-tails-generate-pgp-keys-with-only-1024-key-lengt">Why does Claws Mail included in Tails generate PGP keys with only 1024 key length?</a>.
  124. Claws Mail can use <abbr title="Pretty Good Privacy">PGP</abbr>!? The whole reason I use Icedove is because I never found a way to get Claws Mail to use <abbr title="Pretty Good Privacy">PGP</abbr>.
  125. I tracked down and installed <a href="https://www.claws-mail.org/plugin.php?plugin=gpg">the appropriate plugin</a>, as well as Claws Mail, then purged Icedove.
  126. The Claws Mail <abbr title="Pretty Good Privacy">PGP</abbr> plugin has the same anti-feature that Enigmail does, the one that prevents pasting of passwords.
  127. It turns out pinentry is not Enigmail-specific, and is also used by the <abbr title="GNU Privacy Guard">GnuPG</abbr> plugin for Claws Mail.
  128. </p>
  129. <hr/>
  130. <p>
  131. Copyright © 2015 Alex Yst;
  132. You may modify and/or redistribute this document under the terms of the <a rel="license" href="/license/gpl-3.0-standalone.xhtml"><abbr title="GNU&apos;s Not Unix">GNU</abbr> <abbr title="General Public License version Three or later">GPLv3+</abbr></a>.
  133. If for some reason you would prefer to modify and/or distribute this document under other free copyleft terms, please ask me via email.
  134. My address is in the source comments near the top of this document.
  135. This license also applies to embedded content such as images.
  136. For more information on that, see <a href="/en/a/licensing.xhtml">licensing</a>.
  137. </p>
  138. <p>
  139. <abbr title="World Wide Web Consortium">W3C</abbr> standards are important.
  140. This document conforms to the <a href="https://validator.w3.org./nu/?doc=https%3A%2F%2Fy.st.%2Fen%2Fweblog%2F2015%2F03-March%2F11.xhtml"><abbr title="Extensible Hypertext Markup Language">XHTML</abbr> 5.1</a> specification and uses style sheets that conform to the <a href="http://jigsaw.w3.org./css-validator/validator?uri=https%3A%2F%2Fy.st.%2Fen%2Fweblog%2F2015%2F03-March%2F11.xhtml"><abbr title="Cascading Style Sheets">CSS</abbr>3</a> specification.
  141. </p>
  142. </body>
  143. </html>