1. 17 Jun, 2020 1 commit
    • anonym's avatar
      Update design doc for Thunderbird. · 9c84b918
      anonym authored
      Upstream did not want this patch, and we are not applying it any
      more. Luckily the default url is https so we are good. :)
      9c84b918
  2. 14 Apr, 2020 1 commit
  3. 28 Mar, 2020 2 commits
  4. 26 Mar, 2020 1 commit
    • intrigeri's avatar
      Switch Japanese input method from Anthy to Mozc (refs: #16719) · c56cd06b
      intrigeri authored
      A Japanese speaker (passis12345678) tells us that:
      
      "I don't think any Japanese users would agree that Anthy is better than Mozc.
      The accuracy of Mozy's Kanji conversion is clearly superior to that of Anthy.
      I’ve never seen or heard of anyone who likes Anthy.
      Any Japanese user would be happy to replace Anthy with Mozc."
      
      They also note that ibus-anthy has one advantage over ibus-mozc: it defaults to
      Japanese input, while ibus-mozc defaults to alphabetic and the user has to
      change the setting to Japanese every time they login. Despite that drawback,
      passis12345678 thinks that switching to Mozc is worth it anyway: it's
      a one-per-Tails-session annoyance, as opposed to a permanent annoyance while
      typing in Japanese.
      
      This would be fixed by fcitx-mozc (which defaults to Japanese), but switching to
      fcitx is another, much bigger matter: IBus seems to be much better integrated
      into GNOME than fcitx. Let's stick to IBus for now and try this minimal change.
      c56cd06b
  5. 25 Mar, 2020 1 commit
  6. 21 Mar, 2020 1 commit
  7. 29 Feb, 2020 1 commit
  8. 21 Feb, 2020 1 commit
  9. 26 Jan, 2020 2 commits
  10. 30 Nov, 2019 2 commits
  11. 29 Nov, 2019 1 commit
  12. 08 Nov, 2019 1 commit
  13. 19 Oct, 2019 1 commit
    • intrigeri's avatar
      Use keys.openpgp.org's Onion service as the default keyserver (refs: #12689, #14770) · dbfbfa7b
      intrigeri authored
      For background, see #12689 and its various duplicates. The short version is:
      
       - Unfortunately, hkp://jirk5u4osbsr34t5.onion is way too unreliable.
      
       - Most non-tech-savvy OpenPGP users don't use keyservers at all,
         so this change should not affect them much.
      
       - Tech-savvy OpenPGP users who want to use the Web-of-Trust (which
         keys.openpgp.org's design essentially kills) should be able
         to switch to a keyserver of their choosing, that includes
         non-self certifications.
      
      Let's use the Onion service instead of hkps://keys.openpgp.org/, so that we
      don't lose end-to-end encryption and authentication of the keyserver in
      Seahorse, which doesn't support hkps://. Alternatively, we could use
      hkps://keys.openpgp.org/ everywhere else, but it feels simpler to use the same
      keyserver everywhere.
      
      At this point, the only Tails systems that are affected by this change are those
      run without GnuPG persistence, and newly created persistent GnuPG configuration.
      Pre-existing persistent GnuPG configuration is not updated (yet).
      
      On the test suite front:
      
       - This commit keeps the Chutney-based redirector setup as-is, except it will
         proxy requests to keys.openpgp.org, instead of pool.sks-keyservers.net
         previously. This should work as long as keys.openpgp.org supports cleartext
         communication on port 11371.
      
       - In theory, our long-term plan is to replace this with a local mock keyserver
         Onion service. We'll see if that's still worth the effort once we redirect
         requests to a more reliable upstream keyserver.
      
       - I'm removing the @fragile tag for torified_gnupg.feature. There might
         be other reasons why these scenarios are fragile; let's learn about them.
      dbfbfa7b
  14. 11 Oct, 2019 1 commit
    • intrigeri's avatar
      De-duplicate Tier-1 languages doc. · 444117d8
      intrigeri authored
      I had documented this in our design doc in
      March (179b3335). A few months later, sajolida
      document this again elsewhere
      (ac10f0a3)
      
      Let's not maintain this info in two different places, especially given it is
      clearly not obvious how one could/should find the second instance.
      444117d8
  15. 20 Jul, 2019 1 commit
  16. 14 Jul, 2019 1 commit
  17. 11 Jul, 2019 2 commits
  18. 06 Jul, 2019 2 commits
  19. 05 Jul, 2019 1 commit
  20. 28 Jun, 2019 1 commit
  21. 12 Apr, 2019 1 commit
  22. 08 Apr, 2019 1 commit
  23. 23 Mar, 2019 4 commits
  24. 07 Nov, 2018 1 commit
  25. 22 Oct, 2018 2 commits
  26. 14 Aug, 2018 2 commits
  27. 03 Jul, 2018 1 commit
    • intrigeri's avatar
      Bundle our custom prefs into the Tor Browser's omni.ja (refs: #15023) · b52a5596
      intrigeri authored
      Shipping them in user.js has a few downsides:
      
       - They override whatever is in prefs.js so basically prefs in user.js are
         locked:  any modification done in about:config will be reverted next time Tor
         Browser starts, which can be a PITA when developing Tails.
      
       - In about:config, all these prefs are listed as modified by the user,
         which feels wrong.
      
       - It makes it harder for derivatives to implement things properly.
      b52a5596
  28. 01 Jul, 2018 1 commit
  29. 29 Jun, 2018 2 commits