Re:OpenPGP Forked into "LibrePGP" by GnuPG's Maintainer Wern...
by thayne on Thursday December 07, 2023 @09:09PM
(#38564555)
From a security point of view, absolutely. But there are logistical problems. Currently, a signal account has to be tied to a cell phone number. How does that work when you want it sent to a team instead of an individual? There isn't a sanctioned API, so it is difficult (and unsupported) to set up an integration with bug tracking software. Not to mention that the reporter may not have Signal set up yet.
[ Parent
| on HN ]
Re:OpenPGP Forked into "LibrePGP" by GnuPG's Maintainer Wern...
by tptacek on Thursday December 07, 2023 @09:44PM
(#38564795)
Most reporters don't have PGP set up, either --- far fewer than have Signal set up. But this is all kind of a moot point: the industry norm is to use plaintext email, and to make ad hoc arrangements (including voice calls) for the very rare cases where things are too scary to email.
Re:OpenPGP Forked into "LibrePGP" by GnuPG's Maintainer Wern...
by maximilianburke on Thursday December 07, 2023 @09:52PM
(#38564875)
Honestly these seem like pretty minor issues compared to the task of properly managing a GPG install.
How do you manage the keys? If you've shared them with a team, how do you ensure someone hasn't taken a copy? What if the key is lost? What if someone ends up replying to the thread without doing the encryption song and dance? It's just such a pain. I'd rather copy and paste something out of Signal and into my bug tracker a thousand times than have to deal with all the footguns of email encrypted with GPG.