On 16/11/2022 13:55, Thomas George wrote:
I am giving up and will proceed with the netinst. Thanks everyone for
the many helpful comments and recommendations.
I stripped the spaces from the fingerprint and equated it RSA key. They
matched. So every thing is correct until the last step
Good to let users of gpg know credentials have no web of trust so
verification of credentials will remain limited until further public and
official notice. Public and official notice ought to include an
announcement email to all debian email lists in the event these
credentials are ever added to
I am giving up and will proceed with the netinst. Thanks everyone for
the many helpful comments and recommendations.
I stripped the spaces from the fingerprint and equated it RSA key. They
matched. So every thing is correct until the last step
Dragonette:/home/tom/Downloads/debian# gpg2
Hi,
i managed to produce a rare self-misattribution by copy+paste:
-
the program gpg writes about the Debian CD signing key DA87E80D6294BE9B :
> > > WARNING: This key is not certified with a trusted signature!
> > > There is
Hi,
the program gpg writes about the Debian CD signing key DA87E80D6294BE9B :
> > > WARNING: This key is not certified with a trusted signature!
> > > There is no indication that the signature belongs to the owner
I wrote:
> > This is a security usability problem. How is a non-expert to know
Hi Thomas,
Here's some feedback while looking at things from 10,000 feet. There
are several problems with processes and documentation.
On Wed, Nov 16, 2022 at 3:14 AM Thomas Schmitt wrote:
>
> Thomas George wrote:
> > I am going to erase every thing I have done and start over.
>
> There's no
On 11/16/22 09:13, Thomas Schmitt wrote:
Hi,
Thomas George wrote:
I am going to erase every thing I have done and start over.
There's no need for starting over. The SHA512SUM file is meanwhile
authenticated by your run of:
gpg2 --verify SHA512SUMS.sign SHA512SUMS
[...]
gpg: Good
Hi,
Thomas George wrote:
> I am going to erase every thing I have done and start over.
There's no need for starting over. The SHA512SUM file is meanwhile
authenticated by your run of:
> > gpg2 --verify SHA512SUMS.sign SHA512SUMS
> > [...]
> > gpg: Good signature from "Debian CD signing key
Am 15.11.2022 um 19:20 schrieb Jeffrey Walton:
> It's not you. The whole key server architecture is a mess nowadays.
>
> Jeff
Thank you, Jeff, for your explanation and hints.
Just one additional viewpoint from me (an afficionado for data
protection) ;-)
As i see it, the european law suffers
On Tue, Nov 15, 2022 at 1:01 PM DdB
wrote:
> ...
> i just experienced the same problem, same difficulty understanding the
> man pages. Googling suggested to try a different keyserver.
> I had to try several ... until i found one, that succeeded.
> Apparently, the cause was found to be in the
Am 14.11.2022 um 23:17 schrieb Thomas George:
> I am still trying to do a fully verified installation of debian-11.5.0.
>
> gpg --verify SHA512SUMS.sign SHA512SUMS responded with DF98...BE9B
>
> gpg --recv-keys DF98...BE9B responded key DF98...BE9B: new key but
> contains no user ID - skipped.
>
Hi,
Thomas George wrote:
> gpg2 --verify SHA512SUMS.sign debian-11.5.0-amd64-netinst.iso
> ...gpg: BAD signature from "Debian CD signing key
Consider to re-read my mail of yesterday:
Date: Mon, 14 Nov 2022 09:19:29 +0100
Subject: Re: No Public Key
On Tue, Nov 15, 2022 at 12:22 PM Thomas George wrote:
>
> Close, almost there. At the end something goes wrong. Here is the output:
>
> gpg2 keyserver keyring.debian.org --recv DF98...BE9B
>
> gpg: /root/.gnupg/trustdb.gpg: trust.db created
>
> gpg: key DA87E80D6294BE9B: public key
Close, almost there. At the end something goes wrong. Here is the output:
gpg2 keyserver keyring.debian.org --recv DF98...BE9B
gpg: /root/.gnupg/trustdb.gpg: trust.db created
gpg: key DA87E80D6294BE9B: public key "Debian CD signing key
" imported
gpg: Total number processed: 1
On Mon, Nov 14, 2022 at 05:17:25PM -0500, Thomas George wrote:
> I am still trying to do a fully verified installation of debian-11.5.0.
>
> gpg --verify SHA512SUMS.sign SHA512SUMS responded with DF98...BE9B
>
> gpg --recv-keys DF98...BE9B responded key DF98...BE9B: new key but contains
> no
On debian, have you got a gpg2 executable? If so, that executable may be
more current and if so possibly work better.
Jude "There are four boxes to be used in
defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
.
On Mon, 14 Nov 2022,
I am still trying to do a fully verified installation of debian-11.5.0.
gpg --verify SHA512SUMS.sign SHA512SUMS responded with DF98...BE9B
gpg --recv-keys DF98...BE9B responded key DF98...BE9B: new key but
contains no user ID - skipped.
Another source suggested gpg --key-server
17 matches
Mail list logo
