Verify (and Document?) Additional Software Feature behaviour with apt-key
Additionnal Software feature documents how to add a repository here https://tails.boum.org/doc/advanced_topics/additional_software/index.en.html.
However, lot of those repositories use additionnal PGP keys for integrity etc.
As the documentation does not mention anything about those keys and their use, I am wondering,
- How/If it will work without those keys
- If/How it won’t be wortly to document how to add those keys, if douable.
Blocked by Tails -
#3 Updated by sajolida 2018-07-02 12:03:52
- Status changed from New to Confirmed
- Assignee changed from sajolida to emmapeel
- Target version set to Tails_3.9
- Type of work changed from End-user documentation to Research
- Deliverable for set to 299
Indeed, that’s a valid point.
In the current version we are advertising adding additional repos to enable
non-free section and that doesn’t require additional APT key:
But in the version we are writing on
feature/14594-asp-gui we talk about non-Debian repositories, and these would require additional APT key.
Emma, can you check what it would take to make an additional APT key persistent in Tails?
- If that’s feasible, then I would adjust our new doc to mention this as well.
- If that’s not feasible, then I would adjust our new doc to make it clear that this will not be enough for non-Debian repos.
#9 Updated by sajolida 2018-08-19 19:56:24
- Assignee deleted (
- Target version deleted (
- QA Check deleted (
- Type of work changed from Research to Wait
- Deliverable for deleted (
I think that’s outside of the scope of SponorW_2017. Let’s wait some time after 3.9 to see how popular this use case is. Then we’ll have better argument to work on this (my bet is that it will be hard to support this use case well).
#10 Updated by intrigeri 2019-03-08 16:16:39
- Type of work changed from Wait to Research
> I think that’s outside of the scope of SponorW_2017. Let’s wait some time after 3.9 to see how popular this use case is. Then we’ll have better argument to work on this (my bet is that it will be hard to support this use case well).
@sajolida, maybe enough time after 3.9 has passed to do the next steps?
#11 Updated by sajolida 2019-03-13 12:53:49
- Assignee set to sajolida
- Target version set to Tails_3.13
- Parent task set to
If I have time, I’ll try to write a script to extract “=== content of /” from WhisperBack reports as part of
Feature #15979. This way we could have easy stats on both Additional Software usage and list of additional repos, if any.
#17 Updated by intrigeri 2019-08-30 17:07:29
- Target version deleted (
We’ve set up an automated process to ask our fellow contributors to update some tickets of theirs, in order to:
- better reflect your plans;
- bring down your amount of work-in-progress to a sustainable level;
- encourage team work and increase the chances that someone finishes the work;
- avoid a human doing ticket triaging and asking you the same questions on each such ticket.
In particular, this process identifies:
- Stalled work-in-progress
- Reviews waiting for a long time
However, in the current state of things, this process is not able to notice those tickets when their Target version has been repeatedly postponed by our Release Managers. Therefore, the ticket triaging team decided on
Feature #16545 to remove the Target version whenever in such cases, when it does not feel realistic. This is what I’m doing on this ticket.
You now have a few options, such as:
- Deassign yourself. That’s fine. If it really matters, someone else, possibly you, may pick it up later. Then, if this ticket is relevant for a Tails team, bring it to their attention; else, forget it and take care of yourself :)
- If you think you can realistically come back to it and finish the work in the next 6 months, say so on this ticket, for example by setting a suitable “Target version”. This will communicate your plans to the rest of the project and ensure the task pops up on your radar at a suitable time. Of course, you can still realize later that it is not going to work as planned, and revisit today’s choice.