From: Jeremy Davis <jeremy@turnkeylinux.org>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [TurnKey Linux] Looking to update our signing key... Advice?
Date: Wed, 22 Nov 2023 15:50:39 +1100 [thread overview]
Message-ID: <576a10b6-2a41-49b0-8bae-8abcb6786e93@turnkeylinux.org> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1287 bytes --]
Hi,
Apologies in advance if this is not the right place to post this. Please
redirect me to the appropriate forum if not. I'm also happy to discuss
off list if that is deemed more appropriate.
My name is Jeremy and I work with TurnKey Linux.
As a housekeeping matter, we're looking to update our GPG signing key -
that we sign the index file we provide for downloading our LXC templates
via the PVE UI (which includes hashes of our templates).
The current key recently expired (caught us a bit unawares). We updated
the expiry to keep it alive. And it doesn't seem to have caused any
issues (at least not in my local PVE servers).
However, the key is quite old and doesn't have current best practice
size (RSA-4098 AFAIK?). So I'd like to rotate it.
I was hoping that someone with some authoritative knowledge of the
relevant PVE components would be willing to give me some guidance on the
process (not generating the key itself, just the PVE integration
specific bits). Hopefully that can ensure that key rotation causes
minimal disruptions to users.
Also if there are any specific PVE recommendations/requirements re the
new GPG keypair to generate, that would also be great.
Thanks in advance.
Regards,
Jeremy Davis
TurnKey Linux
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next reply other threads:[~2023-11-22 4:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 4:50 Jeremy Davis [this message]
2023-11-22 8:19 ` Thomas Lamprecht
2023-11-23 2:04 ` Jeremy Davis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=576a10b6-2a41-49b0-8bae-8abcb6786e93@turnkeylinux.org \
--to=jeremy@turnkeylinux.org \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox