Like promised my investigation here:
On the Debian 10 VPS I enabled the experimental repo and I've got some updates. After that step the Tor key import was possible and the Tor repo is working too. For "production purpose" the Debian experimental repo is disabled again. Problem solved. I assume it was a bug in the key handling chain. Gpg and libgcrypt are the same version like before.
gpg (GnuPG) 2.2.12 libgcrypt 1.8.4
Olaf
Am 20.10.19 um 13:25 schrieb Roger Dingledine:
On Thu, Oct 17, 2019 at 07:38:10PM +0200, Olaf Grimm wrote:
I updated my VPS with a fresh Debian 10 install. According procedure in the documentation
'curl https://deb.torproject.org/torproject.org/A3C4F0F979CAA22CDBA8F512EE8CBC9E88... | gpg --import'
I get the error message '2019-10-17 20:34:32 (1.01 MB/s) - ???A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89.asc??? saved [19665/19665] gpg: no valid OpenPGP data found. gpg: Total number processed: 0
Weird!
What is going wrong? Is this an invalid key? After weeks ago my other install on Debian 10 was ok.
I'd suggest breaking it up into pieces, and investigating each piece.
First, curl the file and make sure you get something that looks like the key on stdout.
Next, redirect that output to a file and make sure you have a key in that file.
Then gpg --import that file.
It's the "saved [19665/19665]" part that I find most interesting -- it's as though your version of curl is storing the output to a file rather than printing it on stdout.
Maybe somewhere out there is a curl that doesn't output the page to stdout by default?
--Roger
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays