- 26 Jan, 2018 8 commits
-
-
anonym authored
This way any mounts made by users of this library (e.g. the Unsafe Browser) can mount targets inside the chroot and let the automatic teardown of the chroot browser deal with the umounting.
-
anonym authored
-
anonym authored
We want to allow something in Tor's rule that is blocked in the LAN rules, so the Tor rule must be listed first.
-
anonym authored
This has been broken since we migrated from our custom Iceweasel to TBB.
- 22 Jan, 2018 2 commits
-
-
anonym authored
-
- 20 Jan, 2018 1 commit
-
- 18 Jan, 2018 2 commits
-
- 08 Jan, 2018 1 commit
-
-
anonym authored
-
- 06 Jan, 2018 1 commit
-
-
intrigeri authored
Linux 4.14 brings new AppArmor mediation features and the policy shipped in Stretch may not be ready for it. So let's disable these new features to avoid breaking stuff: it's too hard to check if all the policy for apps we ship (and that users install themselves) has the right rules to cope with these new mediation features. This feature set file will be: - either removed: once we install an apparmor package that ships its own, maintained elsewhere, feature set (probably via Debian#879585); - or upgraded: to the Buster kernel's, when we move to Buster, iff. Debian does not ship any pinned feature set then (refs: #15149). This commit ports to our build system the changes that are in Buster/sid currently, except we include the Stretch's kernel feature set while Buster/sid is pinned to Linux 4.14's feature set (the policy in Buster/sid was updated to support it). This is exactly what will likely land in the next Debian Stretch point release. I'm using a different filename from the one used on Debian, in order to make it easier to compare the "upstream" (Debian) file with ours. And while I'm at it I'm adding a build-time sanity check that will warn us if there's some maintenance work to do on our side.
-
- 04 Jan, 2018 1 commit
-
-
intrigeri authored
-
- 02 Jan, 2018 1 commit
-
-
intrigeri authored
Whenever persistent Claws Mail setting is enabled, this creates an empty ~/.icedove/ directory, that prevents Thunderbird from starting.
-
- 15 Dec, 2017 1 commit
-
- 29 Nov, 2017 1 commit
-
-
intrigeri authored
Debian enables HashKnownHosts by default via /etc/ssh/ssh_config for good reasons, let's not revert to the upstream default.
-
- 23 Nov, 2017 1 commit
-
-
sajolida authored
The configuration has changed since the original commit (55674b5d). See 1.2~exp1 in: https://anonscm.debian.org/git/apt/apt.git/tree/debian/NEWS
-
- 18 Nov, 2017 1 commit
-
-
intrigeri authored
-
- 14 Nov, 2017 4 commits
-
-
anonym authored
-
anonym authored
Me and (mostly) segfault had a late night hacking session, and implemented some pretty full-featured search functionality: * Interactive search * Wrapping search * Keyboard shortcuts: - Ctrl+f => focus find entry - Enter / Shift+Enter: search forward / backward - While find entry is focused: Escape => stop searching
-
anonym authored
We cannot connect, so an error page is shown. Links will still be opened with any configured external application. Thanks for the fix, segfault!
-
anonym authored
Thanks for the tip, segfault!
-
- 13 Nov, 2017 2 commits
-
-
anonym authored
-
- 11 Nov, 2017 1 commit
-
- 08 Nov, 2017 1 commit
-
- 22 Oct, 2017 2 commits
-
-
intrigeri authored
-
- 07 Oct, 2017 2 commits
-
-
intrigeri authored
This fixes #14796 (on Buster, it is displayed in the middle of the screen, on the left of the clock) and an annoying UX problem we have on Stretch: OpenPGP applet is in the middle of icons that share the exact same (modern, GNOME Shell-like) behaviour, which is disturbing when opening one of the modern menus and moving the mouse left/right to the others, because in the middle one icon won't react as expected, and the nice blue bottom border continuity is broken.
-
intrigeri authored
-
- 01 Oct, 2017 1 commit
-
-
intrigeri authored
Force Thunderbird to enable accessibility support even if no a11y feature is enabled in GNOME yet (refs: #14752, #9260). I did not check the source, but the reasoning from commit:a3346a75 probably applies here as well. In any case, the symptoms are the same, and the same fix works.
-
- 30 Sep, 2017 1 commit
-
-
intrigeri authored
Force Tor Browser to enable accessibility support even if no a11y feature is enabled in GNOME yet (refs: #14752, #9260). My understanding of the code in accessible/atk/Platform.cpp is: if this envvar is not set, Firefox will check via D-Bus at startup if accessibility is enabled in the Desktop, and if it's not it'll permanently disable accessibility, which breaks use cases like starting the screen keyboard or screen reader *after* Tor Browser.
-
- 25 Sep, 2017 2 commits
- 24 Sep, 2017 1 commit
-
- 22 Sep, 2017 2 commits
-