20.xhtml 9.5 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133
  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 © 2016 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/2016/02-February/20.xhtml" />
  27. <title>Orbot onions and tox: URIs &lt;https://y.st./en/weblog/2016/02-February/20.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/2016/02-February/20.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/2016/02-February/19.xhtml">&lt;Previous</a>
  60. <a rel="next" href="/en/weblog/2016/02-February/21.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>Orbot onions and <code>tox:</code> <abbr title="Uniform Resource Identifier">URI</abbr>s</h1>
  67. <p>Day 00350: Saturday, 2016 February 20</p>
  68. </header>
  69. <p>
  70. I&apos;ve been very curious about hidden service hosting on a mobile.
  71. In particular, I wanted to know where the onion key for such a hidden service is stored by Orbot.
  72. So today, I decided to give in and give it a random onion address.
  73. I have tried assigning it one of my generated onion addresses, but I never got that working, so now, I allowed it to generate its own onion address.
  74. I found that if you use oandbackup to view and modify Orbot&apos;s files, the onion address will be located at &quot;{decompressed directory}/org.torproject.android/app_data/hs{port that you specified}/private_key&quot;.
  75. Changing onion ports will cause Orbot to generate a new onion address, though the original one will not be deleted, it will only go dormant until the port is switched back.
  76. Unlike Ricochet, Orbot is not afraid to generate onion addresses without Internet access, so I was able to generate these onion addresses without causing any of them to go live.
  77. It should be very easy to swap out the onion for a more readable address if I ever decided to host a hidden service on my mobile.
  78. </p>
  79. <p>
  80. <a href="http://ronsor.net/">Ronsor</a> built a new encryption library called <a href="http://ronsor.net/rcrypt.tgz">rcrypt</a>.
  81. I&apos;m not sure if there&apos;s any sort of security goal that he is trying to accomplish by building his own encryption algorithms, but I get the feeling that this is more of a project for fun than anything.
  82. I hope that he learns a lot from this project, though unless he is extremely good at securing encryption algorithms, rcrypt isn&apos;t going to become widely used.
  83. Still, it seems like fun to experiment with and encrypting alone is no fun, so I generated a set of keys myself.
  84. I need to get an encryption page up at some point, displaying the various public keys that I use, such as this new key, my <abbr title="Pretty Good Privacy">PGP</abbr> key, my <abbr title="Secure Shell">SSH</abbr> key, and because people ask for it sometimes, the hash of my <abbr title="Transport Layer Security">TLS</abbr> certificate.
  85. I might put the two onion addresses that I use there too, as onion addresses are a means of locating a particular public key for hidden service encryption.
  86. </p>
  87. <p>
  88. I received a letter from the state today saying that they had amended my tax return and were giving me back more money than I had asked for.
  89. The issue had been that I had not applied for the kickback from last year because the tax-preparation site had been very confusing in regards to how to apply for that.
  90. In any case, the hilarious part is that the state said that I disagreed with them giving me this extra money, I could appeal to have them accept my original filed return instead.
  91. Though less funny, this notice that they sent came a day later than the actual check from them.
  92. </p>
  93. <p>
  94. I&apos;ve been considering installing <a href="https://tox.chat/">Tox</a> lately.
  95. It seems like a nice encryption-heavy and decentralized communication platform.
  96. However, they use an <a href="https://wiki.tox.chat/users/toxlinks">unregistered <abbr title="Uniform Resource Identifier">URI</abbr> scheme</a> for linking to chat handles on Web pages.
  97. This of course has no impact on whether or not I start using the software, but if they register their scheme, I&apos;ll actually post a link to my handle as well.
  98. Over the past few days, I&apos;ve considered attempting to register the <code>tox:</code> scheme as a provisional scheme, but I decided that it would be better if I tried to talk the Tox developers into registering it themselves.
  99. They would have better control of it that way.
  100. I was going to post the suggestion as a feature request, but reading through the bug tracker, it was already there.
  101. The developers seemed to be planning to attempt to register the scheme after the protocol is more finalized.
  102. I didn&apos;t think that waiting was the best idea unless they planned on waiting to roll out support for such <abbr title="Uniform Resource Identifier">URI</abbr>s in their software, but they had already rolled out support.
  103. From what I&apos;ve been reading, <abbr title="Uniform Resource Identifier">URI</abbr> schemes should not be turned loose outside of a closed test environment without being registered, even if only registered provisionally, so I decided to see if I could change their minds.
  104. The worst that would happen is that they would turn me down or ignore me, right? So I plead my case, <a href="https://github.com/irungentoo/toxcore/issues/1445#issuecomment-186682857">citing three main reasons that they might want to consider a provisional registration now</a>, and it seems that one of the developers is now looking into it!
  105. </p>
  106. <p>
  107. While we did clean up around the house today, we ended up going to the beach instead of working in the classroom.
  108. I think that my mother was too weary of the place to set foot in there today.
  109. I can&apos;t really blame here.
  110. She spends nearly every day wrangling monsters in there.
  111. </p>
  112. <hr/>
  113. <p>
  114. Copyright © 2016 Alex Yst;
  115. 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>.
  116. If for some reason you would prefer to modify and/or distribute this document under other free copyleft terms, please ask me via email.
  117. My address is in the source comments near the top of this document.
  118. This license also applies to embedded content such as images.
  119. For more information on that, see <a href="/en/a/licensing.xhtml">licensing</a>.
  120. </p>
  121. <p>
  122. <abbr title="World Wide Web Consortium">W3C</abbr> standards are important.
  123. This document conforms to the <a href="https://validator.w3.org./nu/?doc=https%3A%2F%2Fy.st.%2Fen%2Fweblog%2F2016%2F02-February%2F20.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%2F2016%2F02-February%2F20.xhtml"><abbr title="Cascading Style Sheets">CSS</abbr>3</a> specification.
  124. </p>
  125. </body>
  126. </html>