On Tue, 14 Jun 2022 19:19:54 +0200
Peter Gerber wrote:
> Looks like the expiration date on the key was changed and the package
> deb.torproject.org-keyring only updates that key in
> /usr/share/keyrings/. I can't but wonder if everyone that doesn't
> have a signed-by is affected, which must be
wly installed, 0 to remove and 0 not upgraded.
[1] https://support.torproject.org/apt/tor-deb-repo/
Regards,
wurstsemmel
Ursprüngliche Nachricht
Von: Imre Jonk
Antwort an: tor-relays@lists.torproject.org
An: tor-relays@lists.torproject.org
Betreff: [tor-relays] EXPKEYSIG w
Hi Imre,
I also ran into this issue. Following the current instructions [1] and adding a
signed-by
in sources.list fixed this for me:
deb [signed-by=/usr/share/keyrings/tor-archive-keyring.gpg]
https://deb.torproject.org/torproject.org main
Looks like the expiration date on the key was
On Monday, June 13, 2022 7:11:32 PM CEST Imre Jonk wrote:
> Hi tor-relays,
>
> I'm getting this error when running 'apt update':
mee too ;-)
> Err:4 https://deb.torproject.org/torproject.org bullseye InRelease
> The following signatures were invalid: EXPKEYSIG 74A941BA219EC810
>
Hi tor-relays,
I'm getting this error when running 'apt update':
Err:4 https://deb.torproject.org/torproject.org bullseye InRelease
The following signatures were invalid: EXPKEYSIG 74A941BA219EC810
deb.torproject.org archive signing key
The signing key in
