tails issueshttps://gitlab.tails.boum.org/groups/tails/-/issues2023-07-19T01:41:20Zhttps://gitlab.tails.boum.org/tails/tails/-/issues/18224Test the verification JavaScript with Firefox Beta and Chrome Beta, 2021 edition2023-07-19T01:41:20Zsajolidasajolida@pimienta.orgTest the verification JavaScript with Firefox Beta and Chrome Beta, 2021 edition- [x] Firefox Beta
- [x] Good image
- [x] Truncated image
- [x] Rogue image
- [x] Chrome Beta
- [x] Good image
- [x] Truncated image
- [x] Rogue image
- [x] Create an issue for next year
See https://tails.boum.org/contribute...- [x] Firefox Beta
- [x] Good image
- [x] Truncated image
- [x] Rogue image
- [x] Chrome Beta
- [x] Good image
- [x] Truncated image
- [x] Rogue image
- [x] Create an issue for next year
See https://tails.boum.org/contribute/release_process/verification_javascript.html to generate truncated and rogue USB images.Tails_4.19cbrownsteincbrownsteinhttps://gitlab.tails.boum.org/tails/tails/-/issues/18278Have our own domain name2022-09-09T12:56:12Zsajolidasajolida@pimienta.orgHave our own domain nameMoved to https://gitlab.tails.boum.org/tails/tails/-/issues/18289 to avoid domain squatting.Moved to https://gitlab.tails.boum.org/tails/tails/-/issues/18289 to avoid domain squatting.Tails_4.19sajolidasajolida@pimienta.orgsajolidasajolida@pimienta.orghttps://gitlab.tails.boum.org/tails/tails/-/issues/18230Define acceptable bounds for non-user-initiated non-Tor Internet activity2021-11-24T10:20:50ZintrigeriDefine acceptable bounds for non-user-initiated non-Tor Internet activityFor #10491 we want to allow ourselves to do some non-user-initiated activity on the Internet without going through Tor, for users who have chosen "Configure Tor automatically" (https://gitlab.tails.boum.org/tails/blueprints/-/wikis/netwo...For #10491 we want to allow ourselves to do some non-user-initiated activity on the Internet without going through Tor, for users who have chosen "Configure Tor automatically" (https://gitlab.tails.boum.org/tails/blueprints/-/wikis/network_connection#consent-question) and don't want/need to hide they're using Tails.
So far we have forbidden ourselves to do so. We have to define where we want to move that limit: it's OK to move that limit to a different place than where we've put it since 10+ years; it's not OK to entirely remove that limit.
This issue is about defining general guidelines, e.g. "it's OK to do non-Tor network activity that
looks like Ubuntu" or "don't talk to Google services without
going through Tor".
Our conclusions should probably go in the design doc.
# Done
## How close do we have to be to a regular Tor Browser or tor client?
See https://gitlab.tails.boum.org/tails/tails/-/issues/18230#note_167559.
# Resources
- https://tails.boum.org/contribute/design/Time_syncing/Tails_4.19sajolidasajolida@pimienta.orgsajolidasajolida@pimienta.orghttps://gitlab.tails.boum.org/tails/tails/-/issues/18295Add noindex to all inlines2021-08-17T10:52:50Zsajolidasajolida@pimienta.orgAdd noindex to all inlinesRight new they are indexed by search engines and this might be problematic in most cases.
[[!meta robots="noindex"]]Right new they are indexed by search engines and this might be problematic in most cases.
[[!meta robots="noindex"]]Tails_4.19sajolidasajolida@pimienta.orgsajolidasajolida@pimienta.orghttps://gitlab.tails.boum.org/tails/tails/-/issues/18324TLS certificate issue prevents tails-upgrade-frontend to check for updates : ...2021-06-25T14:51:49ZgebTLS certificate issue prevents tails-upgrade-frontend to check for updates : Error while downloading the signing keyHi,
I have an error similar to #18184, #18127, while launching Tails 4.18.
![Screenshot.cleaned](/uploads/02bbed9094f2a87e4877cdc7864e2be3/Screenshot.cleaned.png)
It may be related to the fact, the certificate for tails.boum.org seems...Hi,
I have an error similar to #18184, #18127, while launching Tails 4.18.
![Screenshot.cleaned](/uploads/02bbed9094f2a87e4877cdc7864e2be3/Screenshot.cleaned.png)
It may be related to the fact, the certificate for tails.boum.org seems to have been renewed yesterday. The error message explicitly mentions TLS errors :
`Could not download 'https://tails.boum.org/tails-signing-minimal.key', request failed (SSL peer certificate or SSH remote key was not OK): server certificate verification failed. CAfile: /usr/local/etc/ssl/certs/tails.boum.org-CA.pem CRLfile: none`
I was however unable to fix it following solutions on #18184, #18127Tails_4.19intrigeriintrigerihttps://gitlab.tails.boum.org/tails/tails/-/issues/18206Write release notes for 4.192021-06-01T15:52:52Zsajolidasajolida@pimienta.orgWrite release notes for 4.19Tails_4.19sajolidasajolida@pimienta.orgsajolidasajolida@pimienta.orghttps://gitlab.tails.boum.org/tails/tails/-/issues/18284Upgrade to Tor Browser based on Firefox 78.112021-05-31T07:13:20ZintrigeriUpgrade to Tor Browser based on Firefox 78.11Tails_4.19intrigeriintrigerihttps://gitlab.tails.boum.org/tails/tails/-/issues/18311Build environment is not installable on sid since python2 2.7.18-7 was uploaded2021-05-25T17:55:00ZintrigeriBuild environment is not installable on sid since python2 2.7.18-7 was uploadedHere we go with tails/tails#17858 again. We should update the equivs-generated packages (see `config/equivs/`) in the relevant suite of our custom APT repo.
Note that it seems we could do with fewer such equivs-generated packages: https...Here we go with tails/tails#17858 again. We should update the equivs-generated packages (see `config/equivs/`) in the relevant suite of our custom APT repo.
Note that it seems we could do with fewer such equivs-generated packages: https://gitlab.tails.boum.org/tails/tails/-/issues/17858#note_166710Tails_4.19intrigeriintrigerihttps://gitlab.tails.boum.org/tails/tails/-/issues/18288Communicate about the downtime last week2021-05-18T14:51:20ZNeil AndersonCommunicate about the downtime last weekTails_4.19sajolidasajolida@pimienta.orgsajolidasajolida@pimienta.orghttps://gitlab.tails.boum.org/tails/tails/-/issues/18070Improve Help Desk standard replies2021-05-17T16:14:15ZintrigeriImprove Help Desk standard repliesThis was originally proposed on https://gitlab.tails.boum.org/tails/tails/-/issues/17935#note_160485.
1. [x] Move existing standard replies ("templates") to a place where people who are not Help Desk members can propose improvements
...This was originally proposed on https://gitlab.tails.boum.org/tails/tails/-/issues/17935#note_160485.
1. [x] Move existing standard replies ("templates") to a place where people who are not Help Desk members can propose improvements
→ https://gitlab.tails.boum.org/tails/help-desk-shared/-/wikis/templates
1. [x] Help Desk start using this standard reply, we get used to improving & updating it.
1. [x] Write new standard replies as needed, for situations not covered by the existing ones.
- [x] "This is not Tails specific, we have limited resources, you'll find the answer yourself using your favorite search engine" (some users clearly ask Help Desk before they search the web)
- [x] "We're aware of this problem, we're working on it, see $ISSUE"
1. [x] Triage the existing standard replies
1. [x] Move the most common/relevant standard replies to our website
- Done: https://tails.boum.org/support/help_desk_standard_replies/
1. ~~Teach numbat how to propose changes to templates hosted on our website i.e. how to do a MR, presumably via the GitLab web interface~~ → cancelled
1. [x] Decide whether it's worth automating the process of sending this standard reply
- If it is, see you on #17935.
1. [x] @sdibella has a look at the content and improves it
Also see https://tails.boum.org/blueprint/Helpdesk_Auto-reply/.Tails_4.19sdibella (prolixpost)sdibella (prolixpost)https://gitlab.tails.boum.org/tails/tails/-/issues/18312Make sponsors page translatable2021-05-15T00:11:31Zsajolidasajolida@pimienta.orgMake sponsors page translatableTails_4.19sajolidasajolida@pimienta.orgsajolidasajolida@pimienta.orghttps://gitlab.tails.boum.org/tails/sysadmin/-/issues/17822Retire the Gitolite setup at immerda2021-05-14T13:48:23ZintrigeriRetire the Gitolite setup at immerda# Blocked by
- [x] tails/sysadmin#17605
- [x] summit#11
# Actions
- [x] Ask immerda to delete this setup
- [x] Tell accounting about the retirement date# Blocked by
- [x] tails/sysadmin#17605
- [x] summit#11
# Actions
- [x] Ask immerda to delete this setup
- [x] Tell accounting about the retirement dateTails_4.19intrigeriintrigerihttps://gitlab.tails.boum.org/tails/tails/-/issues/18222Clarify how much Help Desk should try to reproduce issues before reporting them2021-05-04T08:12:12Zsajolidasajolida@pimienta.orgClarify how much Help Desk should try to reproduce issues before reporting themSee https://gitlab.tails.boum.org/tails/tails/-/issues/18157#note_165510See https://gitlab.tails.boum.org/tails/tails/-/issues/18157#note_165510Tails_4.19intrigeriintrigerihttps://gitlab.tails.boum.org/tails/tails/-/issues/18144Hide RecentChanges, History, and Preferences buttons on our website2021-04-28T21:56:15ZintrigeriHide RecentChanges, History, and Preferences buttons on our websiteInitially proposed on #17453, agreed there by intrigeri & sajolida.Initially proposed on #17453, agreed there by intrigeri & sajolida.Tails_4.19sajolidasajolida@pimienta.orgsajolidasajolida@pimienta.orghttps://gitlab.tails.boum.org/tails/tails/-/issues/18260Release Tails 4.19~beta12021-04-28T05:53:27ZintrigeriRelease Tails 4.19~beta1This includes a first batch of S8 & S10 improvements:
- !326
- !375
# To Do
- [x] blog post:
- [x] needs input from @boyska to tell what needs testing
- [x] writing (@sajolida)
- [x] Tell Help Desk that anything about the beta...This includes a first batch of S8 & S10 improvements:
- !326
- !375
# To Do
- [x] blog post:
- [x] needs input from @boyska to tell what needs testing
- [x] writing (@sajolida)
- [x] Tell Help Desk that anything about the beta should go to sajolida (@sajolida)
- [x] Release management (@anonym)
- [ ] Tear down /home/testing (@sajolida)Tails_4.19sajolidasajolida@pimienta.orgsajolidasajolida@pimienta.org2021-04-22https://gitlab.tails.boum.org/tails/sysadmin/-/issues/17605Migrate most remaining Git repositories to GitLab2021-04-22T11:49:37ZintrigeriMigrate most remaining Git repositories to GitLab_Originally created by @intrigeri on [#17605 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/17605)_
As part of the initial migration (tails/sysadmin#15878) we migrated a subset of our
Git repos, exceeding what we p..._Originally created by @intrigeri on [#17605 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/17605)_
As part of the initial migration (tails/sysadmin#15878) we migrated a subset of our
Git repos, exceeding what we promised the sponsor, but not covering all
our Git repos.
Our contributors will better understand the setup if all our
repos were migrated to GitLab, with only a handful of exceptions when
there’s a good reason.
Another goal is to stop using the gitolite setup at immerda, so they can shut down https://git.tails.boum.org/: not only this is good resource hygiene, but having 2 places where we host Git repositories, instead of 3, will also be easier for contributors to cope with.
# Delete
- [x] accounting/donations (empty) [intrigeri]
- [x] mac-compatibility (empty) [intrigeri]
- [x] xmpp-internal (empty) [intrigeri]
- [x] ux (already migrated) [intrigeri]
- [x] debian-paris-201705 (if it needs to be revived, it can be uploaded to Debian infra) [intrigeri]
- [x] tails at immerda [intrigeri]
- We have another public mirror at https://salsa.debian.org/tails-team/tails/ already.
1. [x] Review, merge, and deploy tails/puppet-tails!40
2. [x] Delete on immerda
- [x] gitlab-config at lizard (already migrated)
# Migrate from immerda
- [x] check_puppetdb_nodes, monitor-limesurvey-releases [intrigeri]
1. [x] Manually push mirror to GitLab
2. [x] Review, merge, and deploy tails/puppet-tails!39
3. [x] Delete on immerda
- [x] ci [intrigeri]
- [x] download-and-verify-extension (& archive) [intrigeri]
- [x] frontdesk [intrigeri]
- [x] frontdesk-shared [intrigeri]
- [x] greeter (& archive) [intrigeri]
- [x] icedove (& rename to `thunderbird`) [intrigeri]
- [x] iuk (& archive) [intrigeri]
- [x] live-build [intrigeri]
- [x] otf-2017-2018 (& archive) [intrigeri]
- [x] perl5lib (& archive) [intrigeri]
- [x] persistence-setup (& archive) [intrigeri]
- [x] press [intrigeri]
- [x] pythonlib (& archive) [intrigeri]
- [x] internal [intrigeri]
- [x] security-tracker [intrigeri]
- [x] summit-2014 (& archive)
- [x] summit-2015 (& archive)
- [x] summit-2016 (& archive)
- [x] summit-2017 (& archive)
- [x] summit-2018 (& archive)
- [x] sysadmin [intrigeri]
- [x] translate-server [intrigeri]
- [x] workers-handbook [intrigeri]
# Migrate from lizard
- [x] uui-binary (delete mirror at immerda & archive) [intrigeri]
# Migrate on demand
Announcement: https://lists.autistici.org/message/20210118.113444.823ec7e6.en.html
After 2021-04-18, we can delete the Git hosting setup at immerda.
⇒ **Done** on 2021-04-22.
# Migrate from immerda to lizard
Once everything else is done, these should be the only repositories left at immerda, that block shutting down https://git.tails.boum.org/:
- [x] fundraising: we need direct access to reset git-remote-gcrypt when it gets too painful
- [ ] summit (unless tails/summit#11 is done by then already)
- [x] myprivatekeyispublic/testing [intrigeri]
1. [x] Delete mirror on GitLab: there, SSH access is much more powerful than on Gitolite, so it's not a good place to host a user whose SSH private key is public
1. [x] Manually push mirror to lizard
1. [x] Grant access on lizard repo to existing SSH public key
1. [x] Prepare tails/tails MR that switches to the lizard remote (tails/tails!344)
1. [x] Review, merge, and deploy this MR (tails/tails!344)
1. [x] Delete on immerda
# Leave on lizard
- accounting: we need direct access to reset git-remote-gcrypt when it gets too painful
- sysadmin stuff: gitolite-admin, gitlab-migration-private, jenkins-lizard-config, weblate-gatekeeper, puppet repos
- isos, torbrowser-archive: need to be next to our web server and to Jenkins
- local mirrors: mirror-pool, mirror-pool-dispatcher, etcher-binary, promotion-material, tailsTails_4.19intrigeriintrigerihttps://gitlab.tails.boum.org/tails/sysadmin/-/issues/17821Grant moire write access to tails.git2021-04-20T07:30:59Zsajolidasajolida@pimienta.orgGrant moire write access to tails.gitThe sysadmin side of fundraising#17727.
See the discussion on tails@boum.org
@moire :small_red_triangle:The sysadmin side of fundraising#17727.
See the discussion on tails@boum.org
@moire :small_red_triangle:Tails_4.19intrigeriintrigeri