✨ Feature Suggestion | List PGP keys + proofs of recommendations somewhere? #1755
Labels
No Label
🔍🤖 Search Engines
approved
dependencies
duplicate
feedback wanted
high priority
I2P
iOS
low priority
OS
Self-contained networks
Social media
stale
streaming
todo
Tor
WIP
wontfix
XMPP
[m]
₿ cryptocurrency
ℹ️ help wanted
↔️ file sharing
⚙️ web extensions
✨ enhancement
❌ software removal
💬 discussion
🤖 Android
🐛 bug
💢 conflicting
📝 correction
🆘 critical
📧 email
🔒 file encryption
📁 file storage
🦊 Firefox
💻 hardware
🌐 hosting
🏠 housekeeping
🔐 password managers
🧰 productivity tools
🔎 research required
🌐 Social News Aggregators
🆕 software suggestion
👥 team chat
🔒 VPN
🌐 website issue
🚫 Windows
👁️ browsers
🖊️ digital notebooks
🗄️ DNS
🗨️ instant messaging (im)
🇦🇶 translations
No Milestone
No Assignees
1 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: privacyguides/privacytools.io#1755
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description
A bit like https://github.com/privacytoolsIO/privacytools.io/issues/1622, we have multiple recommendations who are using PGP in code/software signing, sign emails they send or support PGP encrypted emails. https://github.com/privacytoolsIO/privacytools.io/issues/1703 would bring more of them, so I wonder if we should have a list of the PGP fingerprints (with a big warning to not solely trust us and do your own research)?
I think this might carry a risk of us becoming a pseudo CA though, while git makes all changes transparent (at least for those who look).
As with #1622, I have a personal "project" doing similar except that I am not bothering with proofs there. README
This is my concern, especially because we will now be tasked with keeping it up to date with changes as well. If a project utilizes PGP they should also have a mechanism to securely transmit that key to the user on their own, IMO.