mirror of
https://github.com/3proxy/3proxy.git
synced 2026-11-22 23:59:41 +08:00
Switch release signing to an RSA-4096 key
rpm 4.14 (RHEL/CentOS/Rocky 8) cannot import an Ed25519 public key at all: the import fails and package verification reports SIGNATURES NOT OK. RHEL 8 is supported until 2029 and is a realistic target for a signed package repo, so the Ed25519 key excludes a large part of the rpm audience. Publish an RSA-4096 signing key as 3proxy-release-key.asc and keep the old Ed25519 key as 3proxy-release-key-ed25519.asc so artifacts up to 0.9.9 stay verifiable. Workflows derive the key id from the imported secret key, so no workflow change is needed.
This commit is contained in:
1 parent
86ad7263a6
commit
1e019bad0e
3 files changed
+51
-8
No files matched your search
+15
-1
@@ -19,12 +19,26 @@ Release binaries are published with SHA256 checksums, an OpenPGP signature and
|
||||
a GitHub build provenance attestation.
|
||||
|
||||
The release signing key is `3proxy-release-key.asc` in the root of this
|
||||
repository. Import it once:
|
||||
repository, an RSA-4096 key:
|
||||
|
||||
```
|
||||
pub rsa4096 2026-08-21 [SC]
|
||||
FC12 2144 99FC C7BA 1CFF 6CDC 0312 384E 3A73 940B
|
||||
uid 3proxy release signing <3proxy@3proxy.org>
|
||||
```
|
||||
|
||||
Import it once:
|
||||
|
||||
```
|
||||
gpg --import 3proxy-release-key.asc
|
||||
```
|
||||
|
||||
Releases up to and including 0.9.9 were signed with an Ed25519 key, kept as
|
||||
`3proxy-release-key-ed25519.asc` for verifying those older files. Note that
|
||||
rpm 4.14 and earlier (RHEL/CentOS 8 and older) cannot import an Ed25519 key
|
||||
and will report `SIGNATURES NOT OK`; use the RSA key and 0.9.9.1 or later on
|
||||
those systems.
|
||||
|
||||
Checksums and the checksum file signature:
|
||||
|
||||
```
|
||||
|
||||
Reference in new issue
Block a user