You're not very clear on the why. What are the risks you're trying to mitigate?
Also, good fucking luck getting anyone in construction to generate and configure pgp. I had a hard enough time teaching some to unlock an iPad
You're not very clear on the why. What are the risks you're trying to mitigate?
Also, good fucking luck getting anyone in construction to generate and configure pgp. I had a hard enough time teaching some to unlock an iPad
As the other commenters have noted, what sort of adversary are you trying to protect against? There is no such thing as "security for its own sake" but rather security measures like E2EE are to protect against specific types of attacks. Do you believe a ticketing system is vulnerable to attacks that E2EE would mitigate?
As an aside, please do not consider PGP to be a pinnacle of signing or encryption. I've opined in another project before about why Late 20th Century PGP isn't that good in the 21st Century.
But even with a modern replacement for PGP, how would E2EE even work for a multi-user ticketing system? If everyone on the support side has the same key, then key management becomes (as usual) the most crucial part of the operation, and remains an unsolved problem at scale. This is no different than physical key management, when every member of the custodial team needs to have the "super key" that opens every door of a university campus.
not having to trust the server itself for data confidentiality
One of the main reasons to self-host is that you can trust the server, since its yours and you are the admin.
Oh no not another client app. Just use a web app. E2EE doesn't help much for this since there has to be stored decryption keys, probably held by multiple people. So those are targets too.
all 6 comments