Re: Suggestions of standards added to openpgp/Gnupg/LibrePgp
Hakun_the_eril via Gnupg-users <[email protected]> Tue, 31 Mar 2026 17:09:08 +0200
| Newsgroups | gmane.comp.encryption.gpg.user |
|---|---|
| Message-ID | <CACnSDUtE6gJ_FjfbUY=FHkEz-5K4dYfKWLJzdNUZCPe4T5WiVw@mail.gmail.com> |
Oh I was not aware of that. My arguments are: Shamirs secret has been around since 1979,- I find it odd that it is not included in Openpgp. It could add things like distributed key custody, hardware enforced split custody. Right now,- if someone with a key leaves or dies important encrypted data gets lost. That would cause issues for any organization. It could also fix the plausible "only one person knows the password" to a " K of N can cooperate" situation. That would also work for a encrypted file system,- split into parts. If a hardware token has , say 256 GB space.. Then it can be a part of a Shamirs secret scheme. 4 out of 6 keys could be used to recreate the shared encrypted file system on a empty drive. Ephemeral signed elliptic curve diffie hellman is usable, because it will solve a forward security issue. If you encrypt say radio transmissions with the same key over long periods anyone who gets hold of that key can decrypt old transmissions. TLS 1.3 , the signal protocol and versions of openssh that is never than 5.7 supports this. I have no business relations with Baochip,- I just think its interesting and neat. tir. 31. mars 2026 kl. 16:27 skrev Robert J. Hansen via Gnupg-users < [email protected]>: > Hakun, this list overwhelmingly prefers plain text, not HTML. Some list > members (including Werner!) simply don't read HTML-composed emails. And > sometimes, HTML emails render in a format that makes it impossible to read. > > > As the Baochip-x1 has the hardware to do a lot of cryptographic > > functions like active zeroisation, Ed25519 signed boot, Glitch sensors, > > security mesh, PV sensor, ECC-protected RAM,Algorithm-agnostic engine > > etc I think that these could be added to standards. > > Why? > > That's the basic question here. What is the use case for LibrePGP that > isn't being adequately addressed by the spec, and how would these > changes mitigate that shortcoming? > > If you can give a good and terse answer to that question I'll be happy > to consider this proposal. > > > The baochips specs can be found here: https://www.baochip.com/ > > Do you have any business relationship to this vendor? > > _______________________________________________ > Gnupg-users mailing list > [email protected] > https://lists.gnupg.org/mailman/listinfo/gnupg-users > _______________________________________________ Gnupg-users mailing list [email protected] https://lists.gnupg.org/mailman/listinfo/gnupg-users