Hi Jason,
Do you have an update on the experiments with signing control files with
the old and new key? Is that currently working and how will the new
public key be disseminated?
You may have a look at the news.admin.hierarchies where Russ published
on March 14th an article to mention the beginning of the experiments.
<news:
[email protected]>
I think it contains the responses to your questions.
Next step is the official confirmation of the new key (announcement,
update in the Big-8 site...) and hope we're done for 10+ years :-)
And then maybe other hierarchies will also update their key (it.*, de.*, uk.*...).
%%
I have finally done the work to create a new modern GnuPG signing key for control messages for the Big Eight hierarchies and wired it into the
machinery that sends those control messages. I have sent one experimental checkgroups message signed with that key:
<cmsg-20210314174844$
[email protected]>
To test the automation, tomorrow the normal monthly checkgroups will be
issued, which should result in two control messages, one signed with the
new key and one with the old key.
I've used the same key ID for the new key as the old key so that updating
will be as simple as importing the new key.
This key is currently EXPERIMENTAL and I reserve the right to reissue the
key if anyone uncovers any problems. If you are in a position to do so,
please try verifying the control messages with the new key and check that
the work properly. I plan on making this new key official some time next
month and will post a more general announcement to news.announce.newgroups
and news.admin.announce at that time.
To avoid binary filters dropping this message, I haven't included the new signing key in this post. You can get it from:
https://www.eyrie.org/~eagle/big-8/key.asc
%%
--
Julien ÉLIE
« La vraie paresse, c'est de se lever à 6 heures du matin pour avoir
plus longtemps à ne rien faire. » (Tristan Bernard)
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)