the documentation makes people download a gpg key to /usr/share/keyrings/tor-archive-keyring.gpg, and require signatures from that key for the repo. It also recommands installing the packet deb.torproject.org-keyring which should update that key before it expires.
However that packet actually writes to /usr/share/keyrings/deb.torproject.org-keyring.gpg. This causes people to get errors when the key they downloaded expires, and the configuration still looks at that key, not the one being auto-updated.
Designs
Child items ...
Show closed items
Linked items 0
Link issues together to show that they're related.
Learn more.
When adding an OpenPGP key that's used to sign an APT repository to /etc/apt/trusted.gpg or /etc/apt/trusted.gpg.d, the key is unconditionally trusted by APT on all other repositories configured on the system that don't have a signed-by option, even the official Debian / Ubuntu repositories. As a result, any unofficial APT repository which has its signing key added to /etc/apt/trusted.gpg or /etc/apt/trusted.gpg.d can replace any package on the system.
Not that I don't trust the TorProject key. It increases the desire of attackers to compromise the key or deb.torproject.org.
I have no idea if that is the correct thing to do, but I wonder about the impossibility of creating new tickets and noticed that the parent project does allow to create tickets. Gitlb can be confusing, and some repositories have ticketing disabled so all the tickets are on the same place.
Hi @emmapeel, I've taken a closer look and it seems like peter has disabled issues.
I can create issues for 'debian/tor-pristine-upstream' but not '/debian/tor'
This issue has been waiting for information two
weeks or more. It needs attention. Please take care of
this before the end of
2024-10-10. ~"Needs
Information" tickets will be moved to the Icebox after
that point.
(Any ticket left in Needs Review, Needs Information, Next, or Doing
without activity for 14 days gets such
notifications. Make a comment describing the current state
of this ticket and remove the Stale label to fix this.)
To make the bot ignore this ticket, add the bot-ignore label.
... there are at least two things in there16:56 <+weasel> the two names in /usr are a documentation bug; should be fixed.16:57 <+weasel> and I agree that the thing should not ship /etc/apt, but I don't have the cycles to think of how to do a transition.
This issue has been waiting for information two
weeks or more. It needs attention. Please take care of
this before the end of
2024-11-21. ~"Needs
Information" tickets will be moved to the Icebox after
that point.
(Any ticket left in Needs Review, Needs Information, Next, or Doing
without activity for 14 days gets such
notifications. Make a comment describing the current state
of this ticket and remove the Stale label to fix this.)
To make the bot ignore this ticket, add the bot-ignore label.