New Big-8 Newsgroup

[Julien ÉLIE]

Hi Nigel,

Adding news.admin.hierarchies in the discussion because it may be time
to generate new PGP keys for still active hierarchies.

https://ftp.isc.org/pub/pgpcontrol/PGPKEYS
and just run gpg --import on it.

Doh, totally missed that bit right at the end. Is it expected that most
of the keys wont import?
gpg: Total number processed: 103
gpg: skipped PGP-2 keys: 87
gpg: imported: 16

The 16 keys still recognized by current GnuPG releases are the ones of
the Big-Eight, aioe, bofh, fr, grisbi, hacktic, hr, ie, mensa,
microsoft, pbinfo, perl, pgsql, sfnet, szaf, us.

belwue, bln, de, ffm, fido7, hun, it, ka, linux, openwatcom, uk and
z-netz have sent control articles these last 10 years, and still have
PGP-2 keys...

[Thomas Hochstein]

Post by Julien ÉLIE
Adding news.admin.hierarchies in the discussion because it may be time
to generate new PGP keys for still active hierarchies.

Still on the ever-growing todo list ...

[Julien ÉLIE]

Just a ping :-)
Finding a packaged old version of GnuPG to verify old keys will be more
and more difficult year by year...

Post by Julien ÉLIE

Is it expected that most of the keys wont import?
gpg: Total number processed: 103
gpg:     skipped PGP-2 keys: 87
gpg:               imported: 16

The 16 keys still recognized by current GnuPG releases are the ones of
the Big-Eight, aioe, bofh, fr, grisbi, hacktic, hr, ie, mensa,
microsoft, pbinfo, perl, pgsql, sfnet, szaf, us.
belwue, bln, de, ffm, fido7, hun, it, ka, linux, openwatcom, uk and
z-netz have sent control articles these last 10 years, and still have
PGP-2 keys...

I hope hierarchy administrators will manage to find a bit of time; news
admins will be grateful for that :-)

[Jesse Rehmer]

Post by Julien ÉLIE
The 16 keys still recognized by current GnuPG releases are the ones of
the Big-Eight, aioe, bofh, fr, grisbi, hacktic, hr, ie, mensa,
microsoft, pbinfo, perl, pgsql, sfnet, szaf, us.

Does https://ftp.isc.org/pub/pgpcontrol/PGPKEYS need updating? You
mention newer keys for Big-Eight, aioe, and others, but I only see the
old key after importing:

[***@spool1 ~/src]$ gpg --list-keys --homedir=/usr/local/news/etc/pgp
news.announce.newgroups
pub 1024R/B88DA9C1 1996-04-10
uid news.announce.newgroups

[Russ Allbery]

Post by Jesse Rehmer
Does https://ftp.isc.org/pub/pgpcontrol/PGPKEYS need updating? You
mention newer keys for Big-Eight, aioe, and others, but I only see the
news.announce.newgroups
pub 1024R/B88DA9C1 1996-04-10
uid news.announce.newgroups

Yeah, sorry, this has been on my list for forever and I kept forgetting to
do it. I've updated the source for ftp.isc.org and hopefully it should
update in the next few days.

[Nigel Reed]

On Sat, 11 Jun 2022 16:38:32 -0700

Post by Russ Allbery

Post by Jesse Rehmer
Does https://ftp.isc.org/pub/pgpcontrol/PGPKEYS need updating? You
mention newer keys for Big-Eight, aioe, and others, but I only see
--homedir=/usr/local/news/etc/pgp news.announce.newgroups
pub 1024R/B88DA9C1 1996-04-10
uid news.announce.newgroups

Yeah, sorry, this has been on my list for forever and I kept
forgetting to do it. I've updated the source for ftp.isc.org and
hopefully it should update in the next few days.

When I try to import those keys I get a lot of


gpg: skipped PGP-2 keys:

messages. Is there a workaround before I go searching? A quick look
didn't give anything overly useful.

Thanks,

[Thomas Hochstein]

Post by Nigel Reed
When I try to import those keys I get a lot of
messages.

Do you use gpg1 (i.e. 1.x) or gpg2 (i.e. 2.x)?

GnuPG 2.1.18 and newer won't import those keys; you'll need to use GnuPG
1.x (and gpg, not gpgv for verification).

-thh

[Jesse Rehmer]

Post by Thomas Hochstein

Post by Nigel Reed
When I try to import those keys I get a lot of
messages.

Do you use gpg1 (i.e. 1.x) or gpg2 (i.e. 2.x)?
GnuPG 2.1.18 and newer won't import those keys; you'll need to use GnuPG
1.x (and gpg, not gpgv for verification).
-thh

You could mess around trying to get a version of GnuPG 2.x working, but
in the end I also found the path of least resistance to be using GnuPG
1.4.x. Not ideal, but covers the most keys still in use on Usenet.

[Nigel Reed]

On Sun, 12 Jun 2022 16:02:20 -0500

Post by Jesse Rehmer

Post by Thomas Hochstein

Post by Nigel Reed
When I try to import those keys I get a lot of
messages.

Do you use gpg1 (i.e. 1.x) or gpg2 (i.e. 2.x)?
GnuPG 2.1.18 and newer won't import those keys; you'll need to use
GnuPG 1.x (and gpg, not gpgv for verification).
-thh

You could mess around trying to get a version of GnuPG 2.x working,
but in the end I also found the path of least resistance to be using
GnuPG 1.4.x. Not ideal, but covers the most keys still in use on
Usenet.

That's about the conclusion I had come to. Thanks for confirming. I'll
go install gpg1.

Thanks,
Nigel

[Thomas Hochstein]

Post by Julien ÉLIE
Just a ping :-)
Finding a packaged old version of GnuPG to verify old keys will be more
and more difficult year by year...

Yep. <https://lists.debian.org/debian-qa/2022/04/msg00008.html>

Post by Julien ÉLIE
I hope hierarchy administrators will manage to find a bit of time; news
admins will be grateful for that :-)

Still on the to-do list ...

-thh