this post was submitted on 09 Jan 2026
4 points (100.0% liked)
Privacy
4613 readers
649 users here now
Welcome! This is a community for all those who are interested in protecting their privacy.
Rules
PS: Don't be a smartass and try to game the system, we'll know if you're breaking the rules when we see it!
- Be civil and no prejudice
- Don't promote big-tech software
- No apathy and defeatism for privacy (i.e. "They already have my data, why bother?")
- No reposting of news that was already posted
- No crypto, blockchain, NFTs
- No Xitter links (if absolutely necessary, use xcancel)
Related communities:
Some of these are only vaguely related, but great communities.
- !opensource@programming.dev
- !selfhosting@slrpnk.net / !selfhosted@lemmy.world
- !piracy@lemmy.dbzer0.com
- !drm@lemmy.dbzer0.com
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Let's say I had a primary key that has a validity of 1 year & I didn't want to share that & instead sign messages with my sub-keys for let's say 4 months & use different sets of Subkeys with a validity of 4 months.
What purpose does (certifying with) the primary key serve there if you don't disclose it prior to rotation? What do you gain by not disclosing it when its only used in this context? It may be you haven't thought it through fully but otherwise sounds like you can get what you want by separate primary keys which you then manually
--sign-keybetween on demand.