3 ms·
This looks cool, the only thing I don't like is that it uses (from what I understand) a single key, not one per developer. Is that planned at all?
by ukd1 13y ago
This looks cool, the only thing I don't like is that it uses (from what I understand) a single key, not one per developer. Is that planned at all?
- agwa 13y agoYes, it is planned. I have most of the design figured out and just need to work out a few issues with revoking a developer's access. You're the first person to ask specifically about this feature, which is good motivation to take it off the back burner :-). In the meantime, you can accomplish this by storing the git-crypt key in the repository, but encrypted using GPG with multiple recipients (much like your approach). Then you wrap `git-crypt init` in a script that first decrypts the key using GPG before feeding it to `git-crypt init`. To add a new developer, you just re-encrypt the git-crypt key with an additional recipient.