From f6184d7edf7cfb4b899e5408258a646dc3889038 Mon Sep 17 00:00:00 2001 From: Kevin Day Date: Fri, 30 Jan 2026 21:48:27 -0600 Subject: [PATCH] Update: Checksum text, correcting old key descriptions and fix grammar. --- checksum.html | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/checksum.html b/checksum.html index c6d2a44..e53fd15 100644 --- a/checksum.html +++ b/checksum.html @@ -139,19 +139,21 @@

The key identified by 76E903396DAD0A83 is authenticated via the key identified by 02E939B8F7EFE597. - This key will expire near the start of 2024 and will not be used again. This followed the old, and perhaps lazy, practice of using the master key for signing everything. This also utilizes older and less trusted algorithms. + This key expired in 2024 and will not be used again.

The key identified by 02E939B8F7EFE597 for the 2023 to 2024 year range is signed via the key identified by 76E903396DAD0A83. This key has been created near the start of 2023 and will be used until such time a replacement comes about. This follows the newer practice of signing using subkeys, making the master key unavailable. This key utilizes algorithms available as of 2024. + This key expired in 2024 and will not be used again.

The key identified by 02E939B8F7EFE597 for the 2023 to 2027 year range is signed via its own key. - This key has is the same as the 2023 to 2024, but has the year extended. + This key is the same as the 2023 to 2024, except that the year is extended. + This key will expire near the start of 2027 and will not be used again after that.

These public keys should be downloaded imported into your own key chain to perform integrity checking and authentication. -- 1.8.3.1