tails issueshttps://gitlab.tails.boum.org/tails/tails/-/issues2021-10-26T18:09:53Zhttps://gitlab.tails.boum.org/tails/tails/-/issues/18389Link /anonymous_internet/no-wifi from /doc/advanced_topics/wireless_devices2021-10-26T18:09:53Zsajolidasajolida@pimienta.orgLink /anonymous_internet/no-wifi from /doc/advanced_topics/wireless_devicesRight now /doc/advanced_topics/wireless_devices is the 1st result on DuckDuckGo when searching for "wifi".
In 96b185d494, I'm moving the Wi-Fi troubleshooting instructions to a dedicated page.
We should check this DuckDuckGo search aga...Right now /doc/advanced_topics/wireless_devices is the 1st result on DuckDuckGo when searching for "wifi".
In 96b185d494, I'm moving the Wi-Fi troubleshooting instructions to a dedicated page.
We should check this DuckDuckGo search again after 4.20.
We should anyway link to /anonymous_internet/no-wifi from /doc/advanced_topics/wireless_devices after %"Tails_4.20".cbrownsteincbrownsteinhttps://gitlab.tails.boum.org/tails/tails/-/issues/18383Consider documenting https://tails.boum.org/support/known_issues/#wi-fi also ...2021-10-26T18:01:50ZgebConsider documenting https://tails.boum.org/support/known_issues/#wi-fi also applies when wifi fails to connect (firmware issues)Hi,
I somehow regularly see users that have issues to connect with Wifi, which looks like firmwares/drivers issues :
Contrary to https://tails.boum.org/support/known_issues/#wi-fi, the Wifi adapter appears. Users are able to enter para...Hi,
I somehow regularly see users that have issues to connect with Wifi, which looks like firmwares/drivers issues :
Contrary to https://tails.boum.org/support/known_issues/#wi-fi, the Wifi adapter appears. Users are able to enter parameters, but it fails to connect, even if the parameters are correct. When I as able to debug, I saw nice stack traces in `dmesg`, which were looking like firmwares issues.
It may be interesting to inform the user that if it is their case, it won't worth to spend hours trying to figure out what's going on, and to rely on backup solutions proposed on https://tails.boum.org/support/known_issues/#wi-fi.
This problem seems quite common with macs (at least macbook pro 2017+), so it may worth to add a note into https://tails.boum.org/support/known_issues/#mac.
@sajolida @help-desk, through ?cbrownsteincbrownsteinhttps://gitlab.tails.boum.org/tails/tails/-/issues/18235Document using Dino in Tails2021-06-17T22:32:17Zsajolidasajolida@pimienta.orgDocument using Dino in Tails- It's a candidate to replace Pidgin: #8573.
- Some of us started using it: https://gitlab.tails.boum.org/tails/tails/-/issues/8573#note_92075.
- Timo Hinrichs documented how to do this and I'm working on improvements with him: https://t...- It's a candidate to replace Pidgin: #8573.
- Some of us started using it: https://gitlab.tails.boum.org/tails/tails/-/issues/8573#note_92075.
- Timo Hinrichs documented how to do this and I'm working on improvements with him: https://t-hinrichs.net/DinoTails/DinoTails_recent.html.
We could point to Timo's tutorial from our website or copy it, if only to allow more of us to try out Dino and gather feedback from other early adopters.cbrownsteincbrownsteinhttps://gitlab.tails.boum.org/tails/tails/-/issues/18232Revise documentation on Additional Software for clarity and accuracy, especia...2021-06-18T09:18:25Zkdr4Revise documentation on Additional Software for clarity and accuracy, especially on risks of usingFollow up to my messages ([#1](https://lists.autistici.org/message/20210226.084700.ec428ca4.en.html) & [#2](https://lists.autistici.org/message/20210226.090300.532e14ff.en.html)) on the tails-dev list.
I think the [Documentation on Addi...Follow up to my messages ([#1](https://lists.autistici.org/message/20210226.084700.ec428ca4.en.html) & [#2](https://lists.autistici.org/message/20210226.090300.532e14ff.en.html)) on the tails-dev list.
I think the [Documentation on Additional Software](https://tails.boum.org/doc/first_steps/additional_software/index.en.html) should be revised so users can be more informed about using the Additional Software feature, especially any risks involved.
First:
This follows from a comment to tails-dev (see above) by @syster:
> Take in mind that installing additional software can reduce the security of Tails and could even deanonymize you.
The risk of deanonymization came as a shock, and my shock was not relieved by re-reading the documentation. I think this matter needs to be clarified for the benefit of users.
Second:
The section on 'Removing additional software' is confusing at present. After reading the section again I realized it should be headed '_Uninstalling_ additional software' because that's what it's referring to. The word remove in most of this section should be changed to 'uninstalling' I think.
The very end of that section talks about 'removing' additional software again, but this time it _does_ mean from the persistent storage completely and that doesn't need to be changed.
Could you also update this section or add a new one to advise users on the best way to identify and re-install uninstalled persistent software?cbrownsteincbrownsteinhttps://gitlab.tails.boum.org/tails/tails/-/issues/18160Improve the documentation of the Dotfiles feature2021-05-25T20:10:49ZKitchMImprove the documentation of the Dotfiles featureThe documentation shows that the dotfiles are located in /live/persistence/TailsData_unlocked/dotfiles, and is readily found thru the Files program.
With that said, we are left with a question about how to use it. As an example, if a p...The documentation shows that the dotfiles are located in /live/persistence/TailsData_unlocked/dotfiles, and is readily found thru the Files program.
With that said, we are left with a question about how to use it. As an example, if a program is installed and it creates a .myprogram directory under Home, does a person just copy that directory (with all its files and sub-directories to /live/persistence/TailsData_unlocked/dotfiles?
If a person gets that program to install automatically at start up, will it overwrite its existing data each time?
Based on the feedback provided on this issue, we should:
- [x] Clarify that the files are linked using Linux symbolic links.
- [x] Clarify that the shortcut is in the left pane of the *Files* browser.
- [x] Clarify that this feature only symlinks files but doesn't make an entire folder Persistent.
- For that people can use /live/persistence/TailsData_unlocked/persistence.conf but this is not document anywhere so far. It also looks a bit scary.
- For example, I have `/home/amnesia/org source=org` in my persistence.conf to persist all my org-mode files.
- [x] Rephrase "*Symlink into $HOME every file or directory found in the `dotfiles' directory*" as "*Symlink every file in the *Dotfiles* folder into the Home folder.*" as per https://gitlab.tails.boum.org/tails/blueprints/-/wikis/Persistent-Storage-redesign.cbrownsteincbrownsteinhttps://gitlab.tails.boum.org/tails/tails/-/issues/18130Update our doc to the new Persistent Storage2023-02-07T14:30:07Zsajolidasajolida@pimienta.orgUpdate our doc to the new Persistent StorageSee #17803.
- [x] Update the doc on changing the passphrase
- [x] Mention the Persistent Storage somewhere in "Encryption and Privacy". People might look there for ways to encrypt their files while the Persistent Storage is the best opt...See #17803.
- [x] Update the doc on changing the passphrase
- [x] Mention the Persistent Storage somewhere in "Encryption and Privacy". People might look there for ways to encrypt their files while the Persistent Storage is the best option for that.
- [x] Split "Creating" and "Configuring". I'm more and more inclined to believe that short pages for each topics are better than longer pages that cover more ground, for example when people do internal searches or are only interested in one of the topic.
- [x] Explain better the security of the deletion
- [x] Consider removing /doc/first_steps/persistence/warnings
- [x] Consider renaming the page to persistent_storage
- [x] Remove note about #18379
- [x] Remove section about Persistent Storage from installation instructions (after #15568)Tails_5.10sajolidasajolida@pimienta.orgsajolidasajolida@pimienta.orghttps://gitlab.tails.boum.org/tails/tails/-/issues/18113Document how to start Tails from an external hard drive or SSD2021-04-20T00:36:05ZintrigeriDocument how to start Tails from an external hard drive or SSDOn #16926 we reached the conclusion that it's worth documenting this (remove `live-media=removable`) until #6397 is implemented.
Incidentally, the same instructions would work for booting from a virtual or physical USB drive in VirtualBox.On #16926 we reached the conclusion that it's worth documenting this (remove `live-media=removable`) until #6397 is implemented.
Incidentally, the same instructions would work for booting from a virtual or physical USB drive in VirtualBox.Tails_4.16sajolidasajolida@pimienta.orgsajolidasajolida@pimienta.orghttps://gitlab.tails.boum.org/tails/tails/-/issues/18105Update doc for "Improvement 1: Configuration of Tor bridges"2021-06-01T00:24:42ZintrigeriUpdate doc for "Improvement 1: Configuration of Tor bridges"Quotes from the first usability tests:
- "Something that keeps you hidden"
- "Tor introduction point"
- "Bridge is something that you walk through in order to be
invisible. When you finish that bridge you are now invisible and
nobod...Quotes from the first usability tests:
- "Something that keeps you hidden"
- "Tor introduction point"
- "Bridge is something that you walk through in order to be
invisible. When you finish that bridge you are now invisible and
nobody can found you."
- "Relays are different layers that you need to walk through to have
this security."
- "Without bridges people will know that you are using Tor even if
they don't know who you are."
- "Bridges are not traced back to you"
- "Having bridges to your USB stick proves that you did something online with it"
Maybe have a diagram or infography that explains bridges.
# Subtasks
- [x] update doc for #17330
- [x] update doc for #17215
- [x] Write doc for "Improvement 3: Inclusion of default bridges"
- [x] update /doc/about/fingerprint
- [x] mention "The Proxy Server is refusing connections" as it confuses many people
- [x] update the reference to Tor Launcher in `wiki/src/support/known_issues.mdwn`Tails_4.20sajolidasajolida@pimienta.orgsajolidasajolida@pimienta.orghttps://gitlab.tails.boum.org/tails/tails/-/issues/18089Write a FAQ about Tails having old versions of software2021-04-19T21:14:58Zsajolidasajolida@pimienta.orgWrite a FAQ about Tails having old versions of softwareRelated to:
- https://tails.boum.org/support/faq/#older-version
- https://tails.boum.org/support/faq/#new-software
We're very strong at telling people only use the latest version of Tails but, at the same time, Tails includes old versi...Related to:
- https://tails.boum.org/support/faq/#older-version
- https://tails.boum.org/support/faq/#new-software
We're very strong at telling people only use the latest version of Tails but, at the same time, Tails includes old versions of its included software. This might be confusing for anybody who is not well-versed in the Debian release cycle:
- Most of the time, we are only able to include the version from Debian stable. We could include backports if they are available.
- Even if we include old versions, security issues are fixed through the Debian security mechanisms.cbrownsteincbrownsteinhttps://gitlab.tails.boum.org/tails/tails/-/issues/18066Document that Tails doesn't work on Apple M1 processors2021-05-15T00:14:48Zsajolidasajolida@pimienta.orgDocument that Tails doesn't work on Apple M1 processorshttps://tails.boum.org/doc/about/requirements/https://tails.boum.org/doc/about/requirements/cbrownsteincbrownsteinhttps://gitlab.tails.boum.org/tails/tails/-/issues/18063Add link to "Known issues with graphics cards" from Support page2020-12-22T20:31:54ZnumbatAdd link to "Known issues with graphics cards" from Support pageOn this page https://tails.boum.org/support/ we could add, under "Check if the problem is already known" a link to https://tails.boum.org/support/known_issues/graphics/On this page https://tails.boum.org/support/ we could add, under "Check if the problem is already known" a link to https://tails.boum.org/support/known_issues/graphics/cbrownsteincbrownsteinhttps://gitlab.tails.boum.org/tails/tails/-/issues/18059Unclear "one after the other" phrasing to ask the user to try several boot op...2020-12-17T19:19:32ZintrigeriUnclear "one after the other" phrasing to ask the user to try several boot options one-by-one & separatelyOn https://tails.boum.org/support/known_issues/graphics/ we have multiple instances of:
> Try adding to the [[boot
> options|doc/advanced_topics/boot_options]],
> one after the other:
>
> * <option 1>
> * <option 2>
> * etc.
Today we'v...On https://tails.boum.org/support/known_issues/graphics/ we have multiple instances of:
> Try adding to the [[boot
> options|doc/advanced_topics/boot_options]],
> one after the other:
>
> * <option 1>
> * <option 2>
> * etc.
Today we've seen a user misunderstanding this and adding all the options at once. Indeed, "one after the other" does not make
it 100% clear what one is supposed to do: one could very well add every option "one after the other" _on the same kernel command line_. This causes user confusion and extra Help Desk workload.
I wanted to propose a MR but could not find any solution I was really happy with.
What I came up with:
* "Try adding to the boot_options, one at a time:"
* "try to start Tails once for each of these boot options:"
I'm sure tech writers will find a better phrasing!
cc @sajolida, @cbrownsteincbrownsteincbrownsteinhttps://gitlab.tails.boum.org/tails/tails/-/issues/18001Explain why is a bad idea to use an old version of Tails in the FAQ2020-12-05T10:41:23ZemmapeelExplain why is a bad idea to use an old version of Tails in the FAQMany times, specially when facing a hardware support regression, users ask frontdesk for the previous version of Tails that is not found on the website anymore.
Maybe we could add a FAQ explaining why this is a bad idea? And title it: "...Many times, specially when facing a hardware support regression, users ask frontdesk for the previous version of Tails that is not found on the website anymore.
Maybe we could add a FAQ explaining why this is a bad idea? And title it: "Where can I get older version of Tails" so users looking for old versions see it.
In frontdesk we tell them:
It is not advisable to use older versions of Tails
because they contain publicly available vulnerabilities.
On each of our release notes there is also the message:
This release fixes many security vulnerabilities.
You should upgrade as soon as possible.
So maybe the FAQ could elaborate a bit more onto that.cbrownsteincbrownsteinhttps://gitlab.tails.boum.org/tails/tails/-/issues/18000Add an epiloge on the install instructions about creating a Tails backup2022-03-16T08:12:58ZemmapeelAdd an epiloge on the install instructions about creating a Tails backupSome issues faced by our users come in a very stressed tone because users lose private keys, electrum wallets, etc. because of the lack of backups.
Maybe we could add a paragraph about backups to the end of the install instructions, wit...Some issues faced by our users come in a very stressed tone because users lose private keys, electrum wallets, etc. because of the lack of backups.
Maybe we could add a paragraph about backups to the end of the install instructions, with links to https://tails.boum.org/doc/first_steps/persistence/backup/ and some comment about the insufferable levity of USB sticks ?
It may sound obvious to knowledgeable people, but many users don't realise their USB stick may fail somehow or forget to make the backups needed.cbrownsteincbrownsteinhttps://gitlab.tails.boum.org/tails/tails/-/issues/17986Update needed to Electrum docs2020-11-30T20:57:47ZemmapeelUpdate needed to Electrum docsIn the page wiki/src/doc/anonymous_internet/electrum.mdwn (https://tails.boum.org/doc/anonymous_internet/electrum/ ) there is a tip that should be updated:
```<div class="tip">
<p><span class="application">Electrum</span> uses <em>mBT...In the page wiki/src/doc/anonymous_internet/electrum.mdwn (https://tails.boum.org/doc/anonymous_internet/electrum/ ) there is a tip that should be updated:
```<div class="tip">
<p><span class="application">Electrum</span> uses <em>mBTC</em> as the
default base unit. 1 mBTC = 0.001 BTC. To change this setting choose
<span class="menuchoice">
<span class="guimenu">Tools</span> ▸
<span class="guimenuitem">Preference</span></span> and open the
<span class="guilabel">Appearance</span> tab.</p>
</div>
```
But the window has changed, and the option **Appearance** is not available now, see screenshot:
![Captura_de_pantalla_de_2020-10-27](/uploads/ac18a7b0b5240e7d04034bed1c808842/Captura_de_pantalla_de_2020-10-27.png)Tails_4.14cbrownsteincbrownsteinhttps://gitlab.tails.boum.org/tails/tails/-/issues/17966Write standard text to answer hardware support reports for which we can't do ...2022-10-13T12:53:36ZintrigeriWrite standard text to answer hardware support reports for which we can't do anything(Output of my residency at Help Desk with numbat.)
In the discussions that lead to creating tails/tails#17965, we agreed to stop putting Help Desk efforts into hardware support, apart of identifying regressions that affect a broad range...(Output of my residency at Help Desk with numbat.)
In the discussions that lead to creating tails/tails#17965, we agreed to stop putting Help Desk efforts into hardware support, apart of identifying regressions that affect a broad range of hardware, and documenting workarounds that our users discover themselves and report to us.
The main blocker for actually doing this is having a standard reply for other hardware support reports: without a nice and complete answer, it's just too tempting to keep doing the Help Desk work like in the good ol' days.
We could write this text right now, and Help Desk could link to it (or copy'n'paste it). There's no reason to wait for tails/tails#17935, which I'm afraid will take some time to become real.
This text could go somewhere on our website, so it is translated. @numbat proposes to add it to the Known Issues page (section V or other, at least linked from here). Once we have an auto-reply mechanism, some this text can probably be reused there, so this first iteration won't waste efforts.
Brainstorming the ideas this standard reply should convey:
- We lack resources to investigate and fix hardware support problems.
- Is the problem a regression?
- If you find a workaround, please let us know so we can document it on our website and everyone else benefits from it.
- Our best bet is that a future drivers update will fix it. Fingers crossed!
- If you want to dive deeper, you may want to try Debian Live images (+ link).
We could proceed like this:
- help-desk, are there are other ideas we need to convey in this standard reply? Please add to the brainstorming above.
- sajolida, would Technical Writers want to write this piece of text and put it wherever y'all see fit on our website? Else, I volunteer to do it: given the equivalent replies are currently written by Help Desk, IMO the first iteration does not necessarily need professional tech writing skills.intrigeriintrigerihttps://gitlab.tails.boum.org/tails/tails/-/issues/17964Link from doc/first_steps/bug_reporting/#no_internet_access to doc/anonymous_...2020-11-24T23:44:40ZintrigeriLink from doc/first_steps/bug_reporting/#no_internet_access to doc/anonymous_internet/networkmanager/It would be nice if https://tails.boum.org/doc/first_steps/bug_reporting/#no_internet_access linked to https://tails.boum.org/doc/anonymous_internet/networkmanager/, so that users who try to figure out how to report a problem about inter...It would be nice if https://tails.boum.org/doc/first_steps/bug_reporting/#no_internet_access linked to https://tails.boum.org/doc/anonymous_internet/networkmanager/, so that users who try to figure out how to report a problem about internet connection trouble have easy access to the corresponding troubleshooting doc.
Context: while doing support with Help Desk today, I sent a link to the former, only realizing later that we have much better troubleshooting doc elsewhere.cbrownsteincbrownsteinhttps://gitlab.tails.boum.org/tails/tails/-/issues/17956Deal with xmpp.riseup.net going away2023-03-13T10:24:03ZintrigeriDeal with xmpp.riseup.net going awayRiseup plans to stop their XMPP service in August 2021.
Our use of this service is the only reason why they have not done this earlier.
What should we do with our public XMPP chatrooms?
Blueprint: https://gitlab.tails.boum.org/tails/bl...Riseup plans to stop their XMPP service in August 2021.
Our use of this service is the only reason why they have not done this earlier.
What should we do with our public XMPP chatrooms?
Blueprint: https://gitlab.tails.boum.org/tails/blueprints/-/wikis/Migrate_from_xmpp.riseup.net/
- [x] Migrate our chat rooms to disroot.org: !550
- [x] Announce the migration on tails-dev@boum.org
- [x] Configure ACLs for the new chat rooms
- Wait for XMPP addresses (by end of August)
- [x] Update our test suite accordingly (!566)
- [x] Update test suite usage doc (`wiki/src/contribute/release_process/test/usage.mdwn`)
- Migrate the CI isotesters' XMPP accounts to another provider → sysadmin#17851
- [x] Announce to developers the should migrate their own test suite XMPP accounts (`features/config/local.yml`) to another providerTails_4.22intrigeriintrigerihttps://gitlab.tails.boum.org/tails/tails/-/issues/17944Avoid mirrors and rsync.lizard running out of disk space during the release p...2020-11-16T20:53:19ZanonymAvoid mirrors and rsync.lizard running out of disk space during the release process when upgrades to a beta/RC are presentWhile preparing 4.11 I was not able to upload all to_4.11.iuk:s because the /dev/vdb (mounted on /srv) on rsync.lizard is full: tails/sysadmin#17762
I think we haven't accounted for the fact that when preparing a major release, we'll ha...While preparing 4.11 I was not able to upload all to_4.11.iuk:s because the /dev/vdb (mounted on /srv) on rsync.lizard is full: tails/sysadmin#17762
I think we haven't accounted for the fact that when preparing a major release, we'll have to be able to store three sets of IUKs at the same time:
* for the still current stable release (currently 4.10)
* for the new version's release candidate (currently 4.11~rc1)
* for the new version (currently 4.11)
So we'll need to re-calculate how much we'll need for the remainder of the 4.x cycle. We already got 10 GiB, but it likely won't be enough if there is another major release + release candidate during 4.x.Tails_4.12intrigeriintrigerihttps://gitlab.tails.boum.org/tails/tails/-/issues/17869Merge and rephrase warning#confirmation and warning#global-adversary2020-12-17T19:43:26ZGhost UserMerge and rephrase warning#confirmation and warning#global-adversarycbrownsteincbrownstein