summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Rename Tor Browser bookmarkswip/feature/15028-rename-tor-browserAlan2019-04-051-2/+2
| | | | Will-fix: #15028
* Move hooks to drop-in config file snippetssegfault2019-04-044-19/+5
|
* Design doc: add link to implementation (refs: #11729)intrigeri2019-04-041-0/+1
|
* Merge remote-tracking branch 'origin/feature/14556-show-suspend-button' into ↵intrigeri2019-04-043-68/+90
|\ | | | | | | stable (Fix-committed: #11729, #14556)
| * Document that emergency shutdown is disabled during suspend (refs: #11729)segfault2019-04-041-0/+6
| |
| * status-menu-helper: Fix order of buttons (refs: #14556)segfault2019-04-041-18/+18
| |
| * Disable emergency shutdown during suspend (refs: #11729)segfault2019-04-041-0/+11
| |
| * status-menu-helper: Refactor (refs: #14556)segfault2019-03-231-55/+47
| |
| * status-menu-helper: Show poweroff and reboot buttons when locked (refs: ↵segfault2019-03-231-6/+17
| | | | | | | | #14556, #15640)
| * status-menu-helper: Clean up code (refs: #14556)segfault2019-03-231-3/+5
| |
| * status-menu-helper: Remove unnecessary code (refs: #14556)segfault2019-03-231-18/+0
| | | | | | | | | | | | | | | | * Remove unused imports * Remove bind to 'open-state-changed'. This code was from the original author of the suspend-button extension and makes the restart and poweroff buttons visible when the menu opens - but in fact the buttons are always visible, so this code has no effect.
| * Add suspend button to status-menu-helper (refs: #14556)segfault2019-03-231-0/+18
| |
* | Merge remote-tracking branch 'origin/bugfix/16020-fix-cache-shrinking' into ↵anonym2019-04-021-1/+1
|\ \ | | | | | | | | | | | | | | | stable Fix-committed: #16020
| * | Fix apt-cacher-ng cache shrinking (refs: #16020).Cyril Brulebois2019-03-211-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | The “acngtool shrink” command never fails (at least with apt-cacher-ng 2-2, in stretch), which might explain why the missing sudo call was missed for so long: the insufficient rights as an unprivileged user don't lead to an non-zero exit code, and to the printing of a warning message.
* | | Merge remote-tracking branch ↵anonym2019-04-021-12/+1
|\ \ \ | | | | | | | | | | | | 'origin/test/10774-disable-mac-spoofing-notification-tests' into stable
| * | | Test suite: disable tests about notifications in case of MAC spoofing ↵intrigeri2019-03-251-12/+1
| | |/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | failure (refs: #10774) These notifications are not always displayed, which seems to be a real bug and not a test suite robustness issue. This bug has been here for more than three years. In the last 5 full test suite runs on the stable branch, these steps failed 5/3×5 = 40% of the time. This does not give us any useful information, other than confirming the bug, so let's drop these steps, which incidentally allows us to remove the @fragile tags on the corresponding scenarios ⇒ greater chances we detect issues in the "fail closed" property, which is great.
* | | Merge remote-tracking branch ↵anonym2019-04-022-2/+2
|\ \ \ | |/ / |/| | | | | 'origin/test/10442-webm-video-update-fragile-status' into stable
| * | Test suite: clarify what WebM scenarios are fragile (refs: #10442)intrigeri2019-03-252-2/+2
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | There's been some confusion going on wrt. #10442 and WebM test cases. AFAICT, currently: 1. Browsing the web using the Tor Browser → Watching a WebM video: I don't think it's fragile anymore. At least it hasn't failed in the last 5 full test suite runs on the stable branch. Let's re-enable it and if it proves to still be fragile, mark it as such and reference a new, dedicated ticket. 2. Using Totem → Watching a WebM video over HTTPS: well, it's not just "fragile", it fails (almost?) every single time on lizard these days. That's what #10442 is about, let's make this clear in the test suite.
* | Add dummy changelog entry for 3.14.intrigeri2019-03-231-0/+6
| |
* | Merge remote-tracking branch 'origin/web/release-3.13.1'intrigeri2019-03-2354-174/+1941
|\ \
| * \ Merge remote-tracking branch 'origin/master' into web/release-3.13.1intrigeri2019-03-239-81/+96
| |\ \
| * | | Releasing version 3.13.1intrigeri2019-03-238-0/+1759
| | | |
| * | | Update various website source files for 3.13.1intrigeri2019-03-2312-46/+28
| | | |
| * | | Update IDF file for Tails Verification.intrigeri2019-03-221-5/+5
| | | |
| * | | Update upgrade-description files.intrigeri2019-03-2218-53/+113
| | | |
| * | | Mark Tails 3.13.1 as released.3.13.1intrigeri2019-03-221-2/+2
| | | |
| * | | Merge remote-tracking branch 'origin/master' into stableintrigeri2019-03-223-19/+24
| |\ \ \
| * \ \ \ Merge branch 'bugfix/16606-tor-browser-8.0.8+force-all-tests' into stable ↵intrigeri2019-03-222-26/+26
| |\ \ \ \ | | | | | | | | | | | | | | | | | | (Fix-committed: #16606)
| | * | | | Fetch Tor Browser from our own archive.intrigeri2019-03-221-1/+1
| | | | | |
| | * | | | Upgrade Tor Browser to 8.0.8-build1.intrigeri2019-03-222-26/+26
| | | |_|/ | | |/| |
| * | | | Reference MFSA.intrigeri2019-03-221-1/+1
| | | | |
| * | | | Update version and date for 3.13.1.intrigeri2019-03-2210-10/+10
| | | | |
| * | | | Update changelog for 3.13.1.intrigeri2019-03-221-3/+5
| | | | |
| * | | | Merge remote-tracking branch 'origin/master' into stableintrigeri2019-03-229-92/+88
| |\ \ \ \ | | |/ / / | |/| | |
| * | | | Merge branch 'master' into stableCyril Brulebois2019-03-2098-979/+3786
| |\ \ \ \
| * | | | | Remove unreleased versions' UDFs.Cyril Brulebois2019-03-204-42/+0
| | | | | |
| * | | | | Add dummy changelog entry for 3.14.anonym2019-03-201-0/+6
| | | | | |
* | | | | | Manual test suite: test the Upgrader in a way that's closer to production ↵intrigeri2019-03-231-1/+1
| |_|_|_|/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | behavior. Interestingly, this allows me to reproduce #16603, while the previous way hid the problem.
* | | | | Manual test suite: add missing "sudo".intrigeri2019-03-231-1/+1
| | | | |
* | | | | Release process: add intermediary commit (refs: #16585).intrigeri2019-03-231-0/+6
| | | | |
* | | | | Manual test suite: remove test for unsupported use case.intrigeri2019-03-231-4/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We explicitly document the Unsafe Browser as supported only in order to connect to captive portals ⇒ let's not spend any time on testing other use cases.
* | | | | Manual test suite: give actual URL so testers don't need to guess.intrigeri2019-03-231-2/+4
| | | | |
* | | | | Manual test suite: measure boot time without re-partitioning.intrigeri2019-03-231-11/+18
| | | | |
* | | | | Manual test suite: clarify test.intrigeri2019-03-231-1/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Here we want to check that no default password works. If one sets an administration password, any such default password is replaced by the one chosen by the user, so this test is moot.
* | | | | Manual test suite: use HTTPS URL.intrigeri2019-03-231-1/+1
| | | | |
* | | | | Manual test suite: use Onion Service v3 for Thunderbird tests.intrigeri2019-03-231-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Let's exercise functionality that is more likely to break and is not exercised anywhere else in our manual & automated test suites.
* | | | | Drop impractical option in Thunderbird manual test suite (refs: #15914)intrigeri2019-03-231-6/+5
| | | | | | | | | | | | | | | | | | | | | | | | | It's pretty hard to find SMTP relays that support delivery over cleartext SMTP these days (thankfully). Let's focus on the most realistic option.
* | | | | Remove manual Thunderbird test that's been automated (refs: #15914)intrigeri2019-03-231-7/+0
| | | | | | | | | | | | | | | | | | | | | | | | | The corresponding automated tests have the check_tor_leaks tag so a proxy and firewall bypass would be noticed.
* | | | | Updating trace file after uploading the IUKs for 3.13.1.intrigeri2019-03-231-1/+1
| | | | |
* | | | | Release process: don't do wasteful work.intrigeri2019-03-221-0/+4
| | | | |