10.xhtml 7.0 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889909192939495969798
  1. <?php
  2. /**
  3. * <https://y.st./>
  4. * Copyright © 2016 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' => 'Beginning to file bug reports against Web browsers',
  21. 'body' => <<<END
  22. <p>
  23. I broke down and tried using <a href="apt:uzbl">uzbl</a> without <a href="apt:tor">$a[Tor]</a>.
  24. However, as it won&apos;t accept &quot;bad&quot; certificates, I can&apos;t test its handling of $a[SNI] host names.
  25. I sorted the rest of the Web browser I tried into categories debending on the nature of the bugs that they display in relation to Host headers and $a[SNI] host names.
  26. I found that <a href="apt:links">Links</a> and <a href="apt:links2">Links2</a> were the only two without bugs! Those two don&apos;t support $a[SNI] host names, but that means that they are at least not sending malformed $a[SNI] host names.
  27. </p>
  28. <p>
  29. I tried to report the bug in <a href="apt:iceweasel">Firefox</a> to Mozilla, but I when attempting to register an account, I was greeted with this error message:
  30. </p>
  31. <blockquote><p>
  32. User account creation has been restricted.
  33. Contact your administrator or the maintainer (bugzilla-admin@mozilla.org) for information about creating an account.
  34. </p></blockquote>
  35. <p>
  36. I need this bug fixed though, so I wrote to the email address provided in hopes of getting help.
  37. </p>
  38. <p>
  39. Next, I went to report the bug in <a href="apt:midori">Midori</a>.
  40. That seemed simple enough at first, but they wanted me to include information on what version of Midori I&apos;m running.
  41. Seeing as every Web browser I&apos;ve tested either has this bug, one of two others, doesn&apos;t support $a[SNI], or won&apos;t start, the chances that this is fixed in recent versions is very slim.
  42. However, I didn&apos;t want my report dismissed on the grounds that I&apos;m using an outdated software, so I looked into upgrading.
  43. The Midori team provides a <a href="http://midori-browser.org/download/debian/">package</a>, but they also warn that installing it can lead to complications due to dependency on more recent versions of libraries than are available in the repository, so I downloaded the <a href="http://midori-browser.org/download/source/">source</a> instead.
  44. Before compiling it though, I decided to check the version number of my installed copy to see how far behind the most recent version it is.
  45. As it turns out, I already had the most recent version! Because Debian dropped Midori from their repository in Debian 8, I had gotten Midori from the unofficial backports repository, and the backports repository has an up-to-date copy of Midori.
  46. </p>
  47. <p>
  48. Next, I tried to report the bug in <a href="apt:arora">Arora</a>, but I can&apos;t find a place to do so.
  49. The main website redirects to the <a href="https://github.com/Arora/arora">Github repository</a>, but that repository seems to have its &quot;issues&quot; feature disabled.
  50. I ended up sending an email to the developer.
  51. He responded saying that the functionality in question is actually a part of the Qt networking library, so that is where the bug lies.
  52. I&apos;ll probably submit a bug report on Qt tomorrow.
  53. </p>
  54. <p>
  55. I tried to report the bug in <a href="apt:chromium">Chromium</a>, but a Google account is required and Google will not allow me to register without a telephone number.
  56. I went to <a href="ircs://sbuk7aqcxkoyipwv.onion:49152/%23Chromium">#Chromium</a> for help, and found a URI mentioned in their topic about reporting bugs, so I followed it.
  57. It redirected to a page that throws 500 errors if you don&apos;t have a User-Agent string set.
  58. After I set my User-Agent string, it redirected to another Google log in page.
  59. I still couldn&apos;t report the bug without a telephone number, which is both obnoxious and counterproductive.
  60. If people want to report bugs, you should be happy to have testers, especially when you aren&apos;t even paying them, and should not demand pieces of information that they may not have or may not want to give you.
  61. I pasted my bug report <a href="https://paste.debian.net/413999/">somewhere where it&apos;ll be accessible for the next ninety days</a>, then asked someone in-channel to file it on my behalf.
  62. Thankfully, ellyjones stepped up and said she&apos;d submit the <a href="https://bugs.chromium.org/p/chromium/issues/detail?id=593952">bug report</a> for me, though she also told me something I already knew: it&apos;s unlikely that the developers will even care.
  63. However, it seems that the Chromium developers think that the bug is yet another symptom of a <a href="https://bugs.chromium.org/p/chromium/issues/detail?id=496472">known bug</a>.
  64. Looking over the details, it does indeed mention the $a[SNI] host name issue.
  65. My interference wasn&apos;t needed.
  66. </p>
  67. <p>
  68. I still haven&apos;t heard back from my old school about the check.
  69. I&apos;ll likely need to write to them again on Monday.
  70. </p>
  71. <p>
  72. Tonight, my mother freaked out again.
  73. She invited me to a trivia challenge event.
  74. Not wanting to deal with her and her name issues, I thought that the safest option was to decline.
  75. However, I made the mistake of trying to justify my declining of the offer.
  76. If I had simply said that I didn&apos;t want to go with no explanation, everything would have probably been fine.
  77. I said that it didn&apos;t seem like something I would enjoy, as it sounds like competition and I&apos;m not a fan of the necessity of there being winners and losers.
  78. She replied that that it&apos;s similar to how things work in life.
  79. I continued that not everything in life is enjoyable, and competition is one of those things in life that I don&apos;t enjoy.
  80. That really set her off.
  81. It was as if she thinks that everything that&apos;s mandatory in life must somehow be fun and should be craved.
  82. It&apos;s utter nonsense.
  83. </p>
  84. <p>
  85. With mother in such a mood, I really wanted to stay home and not go to the family science night.
  86. I didn&apos;t know how to tell her this without pissing her off further though, so I went anyway.
  87. As it turned out, we ended up manning different stations, so it all worked out.
  88. Vanessa and I worked a balloon booth with a stranger, while our mother worked a booth on the other side of the room.
  89. Cyrus ended up volunteering as well instead of participating as he had planned, and worked a booth near the center of the room.
  90. </p>
  91. <p>
  92. Before heading off to bed, I noticed that my my hidden service port-listing function had failed to alphabetize the known port forward destinations.
  93. I fixed the function, then updated the port listing online.
  94. </p>
  95. END
  96. );