- 21 Feb, 2021 1 commit
-
-
anonym authored
-
- 15 Feb, 2021 5 commits
- 23 Jan, 2021 2 commits
- 19 Jan, 2021 2 commits
-
-
intrigeri authored
We only need them at build time, for config/chroot_local-hooks/58-create-tails-website-CA-bundle. There's no reason we should fiddle with the system-wide CA store.
-
- 15 Jan, 2021 1 commit
-
- 13 Jan, 2021 1 commit
-
-
intrigeri authored
-
- 30 Dec, 2020 1 commit
-
-
intrigeri authored
-
- 29 Dec, 2020 8 commits
- 26 Dec, 2020 1 commit
-
-
tous authored
-
- 22 Dec, 2020 1 commit
-
-
intrigeri authored
The "/2" division confused sajolida: tails/tails!305 (comment 162385)
-
- 19 Dec, 2020 2 commits
- 18 Dec, 2020 5 commits
-
-
intrigeri authored
Outside of Tails, socks5:// would lead to DNS leaks. This does not matter in the context of Tails: the system DNS resolver is torified, and on top of that we have firewall protections against DNS leaks. I'm going to propose we stop supporting our htpdate fork outside of Tails.
-
intrigeri authored
Unfortunately, this is not very helpful, given how curl handles errors when one uses --socks5-hostname. For example, upon DNS resolution error: - with --socks5-hostname: curl: (7) Can't complete SOCKS5 connection to nope.puscii.nl. (4) ⇒ We don't learn anything useful. - with torsocks and without --socks5-hostname: 1608286055 ERROR torsocks[1351008]: Unable to resolve. Status reply: 4 (in socks5_recv_resolve_reply() at socks5.c:677) curl: (6) Could not resolve host: nope.puscii.nl ⇒ We learn that the problem is about DNS resolution.
-
intrigeri authored
Nowadays we only download the HTTP headers.
-
intrigeri authored
I suspect that displaying a size in MiB, claiming it's GB, will confuse users :)
-
intrigeri authored
-
- 17 Dec, 2020 2 commits
-
-
sajolida authored
And use GB consistently. See #15104.
-
anonym authored
It's unclear to me why we needed this patch: https://bugzilla.mozilla.org/show_bug.cgi?id=1680483
-
- 16 Dec, 2020 3 commits
-
-
anonym authored
... which it hasn't been depending on for over six years. :) I also had to clean up some debugging code that depended on yelp in persistence-setup, which does not seem like a good enough reason to keep including it.
-
anonym authored
Otherwise, if Tor Browser is not running, then this process is turned into the Tor Browser process, which is not ideal when called from a notification (which we do in several places) since its code then cannot exit until the Tor Browser process exits, using resources unnecessarily.
-
anonym authored
-
- 15 Dec, 2020 1 commit
-
-
sajolida authored
"Don't Show Again" seems to be the usual phrasing for such things.
-
- 14 Dec, 2020 1 commit
-
-
intrigeri authored
-
- 11 Dec, 2020 3 commits
-
-
anonym authored
Since Tails 4.13 when a user has disabled persistence, or plugs another Tails with a TailsData partition, and tries to mount TailsData through Nautilus, they are met with an error: 'This location could not be displayed. You do not have the permissions necessary to view the contents of "TailsData"'. This is due to #7465 (!210) where we indeed made the TailsData root world-non-readable, and did not consider this use case. Note that this change indeed changes the permission, which might seem dangerous, but if the Tails is later booted it will self-heal, so all is ok.
-
intrigeri authored
-
intrigeri authored
-