On Freitag, 6. September 2024 08:47:14 CEST eff_03675...@posteo.se wrote:
OK,
looks like TorProject (Gus) renamed the key and resolved
tor-archive-keyring.gpg vs. deb.torproject.org-keyring.gpg mismatch.
https://gitlab.torproject.org/tpo/web/support/-/issues/368
Then I can update my sources list
Hi...
Uhmmm shouldn't we exactly the opposite change
your quote :
wget
-qO-https://deb.torproject.org/torproject.org/A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89.asc
| gpg --dearmor | tee /usr/share/keyrings/*tor*-archive-keyring.gpg >/dev/null
to
*
On Montag, 2. September 2024 19:01:16 CEST code9n via tor-relays wrote:
> I know I should have sorted this some weeks ago but can anyone tell me a
> simple method of dealing with the:
As root, one line:
wget -qO-
https://deb.torproject.org/torproject.org/A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89
Hi
Check out https://support.torproject.org/apt/tor-deb-repo/ , the path
to gpg keys you have to put in /etc/apt/sources.list.d/tor.list has
changed and is now /usr/share/keyrings/deb.torproject.org-keyring.gpg
.
regards,
trinity-1686a
On Tue, 3 Sept 2024 at 10:25, code9n via tor-relays
wrote:
Hi,
I know I should have sorted this some weeks ago but can anyone tell me a simple
method of dealing with the:
bullseye InRelease: The following signatures were invalid: EXPKEYSIG
74A941BA219EC810 deb.torproject.org archive signing key
issue, please?
Thanks.__
