You are not logged in.
Hey,
I work in a small bike messenger company in Berlin that operates as a collective, meaning that every "employee" has total access to all data, most accounts etc.
Right now, we are in the process of overhauling our complete IT infrastructure and I came up with the idea to implement some kind of digital signature infrastructure
based on gnupg to sign our outgoing e-mail traffic.
We use only one e-mailadress for communicating with our customers that is being taken care of by the persons in the office during business times.
Creating a gnupg key pair for that adress is an easy thing, but I'm a bit lost when it comes to protecting it from being compromised and could use
some help, being pointed in the right direction... you know.
Here's some things I already thought about:
commonly known passphrase: an obvious no-go, because any collective member that would leave us, would still know the password
no-passphrase key, stored encryptedly, file-system access on a per-user basis: users would still be able to copy the keyfiles and use them after they left the group
One keypair per user: probably the most clean solution but there's afaik no way to say: Wait, this guy's signature is still valid (as in technically valid, because the keys
security is not affected by the employment status of it's owner) but he's actually not working for this company any more.
So, you see it pretty much comes down to the question of how to invalidate keys, after their owners have left us.
I'm not pinned to gnupg, so I'm free to switch to other programs/paradigms/techniques, etc. but open-source is a pretty important criteria.
Moneywise it should be, of course, as cheap as possible, but not necessarily for free.
The company consists of about 25 Members, tendency rising ![]()
I'd appreciate any help!
Thanks,
Vrob
Offline