Mailing List Archive: Importing non-self-signed keys

Importing non-self-signed keys

Sep 10, 1999, 4:39 PM

Post #1 of 5 (2582 views)

I am having major problems importing public PGP keys with GnuPG
(version 1.0.0.) Importing keys created with GnuPG works just fine
however. PGP 2.6.X keys do not work at all, but I guess this is a known
fact due to licensing troubles?

I have had no luck importing PGP 4 and 5 keys neither, GnuPG tells me this
can be due to the fact that these keys are not self-signed. Is there a way
around this, or can only self-signed keys be imported? Lots of people seam
to forget to sign their own keys, it's a good thing it's done automatically
with GnuPG:-)

I also tried importing a RSA and a DSS/Diffie-Hellman key, but then I got
the message "invalid armor header". What does this mean?

Thankful for any help.

André

Re: Importing non-self-signed keys [ In reply to ]

mroth at nessie

Sep 11, 1999, 7:26 AM

Post #2 of 5 (2524 views)

Permalink

On Sat, 11 Sep 1999, André Dahlqvist wrote:

> I have had no luck importing PGP 4 and 5 keys neither, GnuPG tells me this
> can be due to the fact that these keys are not self-signed. Is there a way
> around this, or can only self-signed keys be imported? Lots of people seam
> to forget to sign their own keys, it's a good thing it's done automatically
> with GnuPG:-)

--allow-non-selfsigned-uid

cu
Michael

Re: Importing non-self-signed keys [ In reply to ]

graham at barnowl

Sep 11, 1999, 10:55 AM

Post #3 of 5 (2528 views)

Permalink

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Michael Roth <mroth@nessie.de> writes:

> On Sat, 11 Sep 1999, André Dahlqvist wrote:
>
> > I have had no luck importing PGP 4 and 5 keys neither, GnuPG tells me this
> > can be due to the fact that these keys are not self-signed. Is there a way
> > around this, or can only self-signed keys be imported? Lots of people seam
> > to forget to sign their own keys, it's a good thing it's done automatically
> > with GnuPG:-)
>
> --allow-non-selfsigned-uid

I am having the same problem, and I *have* tried this solution and it
does *not* work.

The following output shows the problem:-

> gpg --allow-non-selfsigned-uid --import sher.asc
gpg: key 34D6A5FD: no valid user IDs
gpg: this may be caused by a missing self-signature
gpg: Total number processed: 1
gpg: w/o user IDs: 1

subsequent to this, gpg --list-keys does not list the key.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.0 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.4 and Gnu Privacy Guard <http://www.gnupg.org/>

iD8DBQE32pelEhN/ETQwnEERAnboAJ0ZIzmKW0xRF5cOI0HTASfyE/hdgQCfXeTc
DpYv97nw+pxKa64mBPl19Yw=
=BqXM
-----END PGP SIGNATURE-----

Re: Importing non-self-signed keys [ In reply to ]

dlh at zns

Sep 11, 1999, 12:15 PM

Post #4 of 5 (2533 views)

Permalink

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 11 Sep 1999, Graham Murray wrote:

> > --allow-non-selfsigned-uid
>
> I am having the same problem, and I *have* tried this solution and it
> does *not* work.
>
> The following output shows the problem:-
>
> > gpg --allow-non-selfsigned-uid --import sher.asc
> gpg: key 34D6A5FD: no valid user IDs
> gpg: this may be caused by a missing self-signature
> gpg: Total number processed: 1
> gpg: w/o user IDs: 1
>

I tried the same thing, and it /did/ work. I got the key straight from
the server, and used the key ID that was seen in your post. I also have
the 'allow..' line in my ~/.gnupg/optins file. I don't know if maybe that
is difference enough. Command and output follow:

dlh@zns:~> gpg --keyserver pgp.ai.mit.edu --allow-non-selfsigned-uid
- --recv-key 34D6A5FD
gpg: requesting key 34D6A5FD from pgp.ai.mit.edu ...
gpg: key 34D6A5FD: accepted non self-signed user ID 'Sherilyn
<sherilyn@sidaway.
demon.co.uk>'
gpg: key 34D6A5FD: accepted non self-signed user ID 'Sherilyn
<sherilyn@sidaway.
screaming.net>'
gpg: key 34D6A5FD: public key imported
gpg: Total number processed: 1
gpg: imported: 1 (RSA: 1)

> subsequent to this, gpg --list-keys does not list the key.

Again, mine does. (probably simply because the above worked for me)

dlh@zns:~> gpg --list-key 34D6A5FD
pub 1024R/34D6A5FD 1999-07-17 Sherilyn <sherilyn@sidaway.demon.co.uk>
uid Sherilyn <sherilyn@sidaway.screaming.net>

- -dave

~~~~~~~~~~~~~~~~~~~~~~
dlh@acu.cs.umb.edu
http://www.cs.umb.edu
~~~~~~~~~~~~~~~~~~~~~~
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.0 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE32qpDkk29ehvsO3kRAttYAKChWO7JMNb6C8w7siSAEn9OZZSxawCfeq7y
xSD0kZUtXHZvMXhqCKLqEr4=
=PjXA
-----END PGP SIGNATURE-----

Re: Importing non-self-signed keys [ In reply to ]

graham at barnowl

Sep 11, 1999, 12:41 PM

Post #5 of 5 (2519 views)

Permalink

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dave Harvill <dlh@zns.acu.cs.umb.edu> writes:

> I tried the same thing, and it /did/ work. I got the key straight from
> the server, and used the key ID that was seen in your post. I also have
> the 'allow..' line in my ~/.gnupg/optins file. I don't know if maybe that
> is difference enough. Command and output follow:

Thanks, fetching from the keyserver now work. However, trying to use
the ASC file still fails.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.0 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.4 and Gnu Privacy Guard <http://www.gnupg.org/>

iD8DBQE32rB9EhN/ETQwnEERAuv7AJ0UbIdDjYZ957pL7Jr3G+zhtGyUZQCgk+mj
NcRf/6PBhJNkc1O3Bk/KiwQ=
=J9Bw
-----END PGP SIGNATURE-----