[slug] Re: Ohhhh jeeee: ... this is a bug

[David Shaw]

--vOmOzSkFvhd7u8Ms
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Mar 29, 2003 at 11:13:28PM -0500, Nori Heikkinen wrote:
> on Sat, 29 Mar 2003 10:52:00PM -0500, David Shaw insinuated:
> > On Sat, Mar 29, 2003 at 10:09:36PM -0500, Nori Heikkinen wrote:
> >=20
> > > > What happens if you do that export using your keyid rather than
> > > > letting GnuPG try to pattern match off your email address?
> > >=20
> > > argh.  i was doing this on my old key, i guess, and forgot about that
> > > possibility.  okay, here's better:
> > >=20
> > > orange:~/.gnupg> gpg --no-comment --export-secret-key 7ede5499 | gpg
> > > --list-packets | grep public
> > >=20
> > > ... produces nothing.
> > >=20
> > > so i guess i *don't* have a public key in there.
> >=20
> > You probably do, but under a different keyid.  You can assemble a
> > good secret keyring with just the keys you want there.  Just do the
> > above command line for each and collect the output into a file -
> > i.e.:
> >
> >    gpg --export-secret-key 7ede5499 > new_secring.gpg
> >    gpg --export-secret-key xxxxxxxx >> new_secring.gpg
> >    gpg --export-secret-key yyyyyyyy >> new_secring.gpg
> >=20
> >    etc.
> >=20
> > You should be able to do 'gpg new_secring.gpg' and see no "pub" or
> > "sub" lines. =20
>=20
> i should?  i *only* get a "sec" line on my own key!  on *anyone*=20
> else's, i get the "pub" and "sub" lines!

This is your *secret* keyring.  Only put your own secret keys in
there.  If you have only one secret key, then just put that secret key
in there.

David

--vOmOzSkFvhd7u8Ms
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2rc1 (GNU/Linux)
Comment: http://www.jabberwocky.com/david/keys.asc

iD8DBQE+hwk94mZch0nhy8kRAqx5AJoDWv+ujhhR1IGWXcmexgU2SEoKBQCeN6G2
ty/TejBucIEC5yxQr5y4AEU=
=fEcq
-----END PGP SIGNATURE-----

--vOmOzSkFvhd7u8Ms--