13.xhtml 8.6 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111
  1. <?php
  2. /**
  3. * <https://y.st./>
  4. * Copyright © 2015 Alex Yst <mailto:copyright@y.st>
  5. *
  6. * This program is free software: you can redistribute it and/or modify
  7. * it under the terms of the GNU General Public License as published by
  8. * the Free Software Foundation, either version 3 of the License, or
  9. * (at your option) any later version.
  10. *
  11. * This program is distributed in the hope that it will be useful,
  12. * but WITHOUT ANY WARRANTY; without even the implied warranty of
  13. * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
  14. * GNU General Public License for more details.
  15. *
  16. * You should have received a copy of the GNU General Public License
  17. * along with this program. If not, see <https://www.gnu.org./licenses/>.
  18. **/
  19. $xhtml = array(
  20. 'title' => 'Something needs to be done about pinentry',
  21. 'body' => <<<END
  22. <p>
  23. I&apos;m not one of those people that blasts his music all the time.
  24. Much of the time, my music is down so low you can&apos;t hear the words unless you already know what they are, and when it isn&apos;t that low, it&apos;s at least at a tolerable level and is easily covered up by any sort of loud noise in the vicinity.
  25. For that reason, I often discover new treasures in my playlist, songs that I&apos;ve heard many times before, but never really payed attention to.
  26. Today, <a href="http://www.joshwoodward.com/song/Chainsaw">Chainsaw</a> was such a song.
  27. It&apos;s got a slow, mellow melody, so if you aren&apos;t paying attention, it&apos;s easy to miss the fact that the song is about a psychopathic murderer.
  28. The narrator of the song killed three people with his chainsaw.
  29. The tune is beautiful, and if you don&apos;t take it too seriously, the lyrics are amusing.
  30. </p>
  31. <p>
  32. It appears that the Geocaching moderators finally got around to cleaning out their moderation queue, as someone responded to my now-visible post.
  33. They said that proxies should work with the Geocaching website as long as they are not anonymizing proxies.
  34. That&apos;s not particularly helpful considering that the proxy I use <strong>*is*</strong> one that anonymizes.
  35. I have clarified, <a href="http://forums.groundspeak.com/GC/index.php?showtopic=331013&amp;st=0&amp;gopid=5493588#entry5493588">stating that I do use an anonymizing proxy</a>, and asking again if there is anything I can do about it.
  36. To be perfectly clear, I once again stated that taking down or bypassing the proxy is <strong>*not*</strong> an option.
  37. </p>
  38. <p>
  39. When I converted <a href="http://www.thekyotoconnection.com/">Wake Up</a> from $a[FLAC] to Vorbis, I didn&apos;t really know what the command I entered to do so meant.
  40. It included an unneeded sound quality flag, so when I later used the command to convert Woodward&apos;s music, I left it out.
  41. It kind of bothered me a little, for $a[OCD] reasons, so I erased the music on my mobile, reconverted Wake Up, <a href="http://www.joshwoodward.com/mod/song/view_album.php?album_id=13">Ashes</a>, and <a href="http://www.joshwoodward.com/mod/song/view_album.php?album_id=15">The Beautiful Machine</a> without the flag, and tried to put the music all back onto my mobile.
  42. All the music went back on without issue, aside from <a href="http://www.joshwoodward.com/mod/song/view_album.php?album_id=5">Sunny Side of the Street</a>.
  43. I jumped to the conclusion that $a[MTP] had gone back to choking on <code>Are You Having Fun?.ogg</code>&apos;s file name, as in the past, I&apos;ve had issues transferring files with questions marks and asterisks in their names.
  44. However, that was not the case.
  45. The other tracks in that album would not transfer to the mobile either.
  46. I rebooted the mobile, and the whole album transfered without error.
  47. I don&apos;t know what the issue was, but at least it seems resolved for now.
  48. </p>
  49. <p>
  50. I downloaded some of <a href="http://kelleemaize.com/">Kellee Maize</a>&apos;s work, which was sorely missing from my playlist.
  51. Namely, I downloaded her three free albums on Jamendo (her other three on Jamendo are proprietary) including her new remix album.
  52. I&apos;m not too impressed by some of the remixes of her work.
  53. Her original versions are much better, though a few of the remixes are good too.
  54. The next albums I buy will probably be her two free albums on Bandcamp (again, the other two on Bandcamp are proprietary).
  55. Once I buy those, I can tell her that if she fixes the licensing on the others, I&apos;d have no problems buying and recommending them.
  56. Her main website says all her work is under {$a['CC BY']}, so really, it&apos;s just a matter of getting her to update to show this on BandCamp and Jamendo.
  57. </p>
  58. <p>
  59. An old friend, <a href="#redaction">[REDACTED]</a>, wrote to me today.
  60. He found my new email address, but he used my old $a[PGP] key, probably assuming I still have it.
  61. Unfortunately, this key was lost when my hard drive failed on me.
  62. I&apos;ve written back explaining such, but [REDACTED] is a cautious individual.
  63. We&apos;ll have to see how he responds and if he believes that I&apos;m the same person he once knew.
  64. </p>
  65. <p>
  66. As I said, [REDACTED] uses $a[PGP] encryption.
  67. To write back, I attempted to retrieve his public key from the key servers using Claws Mail&apos;s $a[GnuPG] plugin&apos;s interface, but it appears such an option does not exist.
  68. After searching the web and scouring the interface, I ended up giving up and looking for a new option.
  69. I installed Seahorse, which is supposed to be a graphical key manager, but it didn&apos;t show any signs that it had actually downloaded [REDACTED]&apos;s key, and the key did not show up in the list of keys I have on my machine.
  70. Next, I tried $a[GNU] Privacy Assistant.
  71. $a[GNU] Privacy Assistant throws errors complaining about an unsupported certificate every time I open or close the application, as well as if I access certain dialog windows within the application.
  72. If I attempt to download a key, I&apos;m told that on key was found but that zero were downloaded.
  73. I decided I might be better off replacing my whole mail client.
  74. Back when I used IceDove with Enigmail, key retrieval was possible from within the mail client, so I know it can be done.
  75. Additionally, replacing the mail client may allow me to escape pinentry&apos;s idiocy.
  76. I decided to try Evolution.
  77. I installed it, but it doesn&apos;t show up in the application menu and running <code>evolution</code> on the command line doesn&apos;t work.
  78. I went back to the command line to recheck what keys I needed, and found that [REDACTED]&apos;s key was installed.
  79. What I figure most likely happened is that Seahorse successfully imported the key, but showed no success message.
  80. Likewise, it does not display the key, either due to a bug or due to it not displaying public keys.
  81. $a[GNU] Privacy Assistant found the key but would not download it because it had already been downloaded by Seahorse.
  82. </p>
  83. <p>
  84. Speaking of pinentry&apos;s idiocy, I&apos;m planning to code a way around using pinentry when compiling my site.
  85. Every day I have to deal with pinentry fighting me tooth and nail to make sure I don&apos;t paste my password in or autotype it.
  86. It is a pain in the butt, and it&apos;s all because the developers think everyone should hand type their passwords.
  87. I have news though: if your password is as secure as it should be, typing your password is not a real option.
  88. I don&apos;t know what to do on the mail front.
  89. I don&apos;t send mail that often though, and most of the mail I receive is automated, so I don&apos;t have to deal with pinentry in my mail client on a regular basis.
  90. </p>
  91. <p>
  92. <strong>*Last minute update*:</strong> When I was compiling my site today to upload this entry, I found that pinentry&apos;s password prompt had changed.
  93. Autotype is now completely broken.
  94. Before, pinentry would attept to detect if I had autotyped the password, and would claim that the password was incorrect if it successfully detected that I had.
  95. Now, autotype doesn&apos;t even allow input by autotype.
  96. However, it now accepts clipboard input.
  97. I can now paste my password! No paste blocking and no complaints about pasted passwords are present.
  98. I&apos;m not sure if this is actually not pinentry at all or if something I installed while as a dependency today fixed pinentry&apos;s poor behavior.
  99. I will have to look more into this next time I have a clean system to work with, so I can try to find exactly which installation fixed the issue.
  100. </p>
  101. <p>
  102. <a href="/a/canary.txt">No one prevents me from speaking my mind today.</a>
  103. </p>
  104. <p>
  105. <strong id="redaction">*REDACTION*:</strong> I have been asked by the entity mentioned above to remove his/her name and not link to him/heron the Web.
  106. This is a request on behalf of the person&apos;s privacy, and is <strong>*not*</strong> a request made by a third-party government entity.
  107. </p>
  108. END
  109. );