Each person whose private key is listed in
responsible for keeping their secret key safe from prying eyes, and
safely backed up. It is a good idea to generate a new key specifically
for use with
regpg - see "revocation" below.
regpg requires the use of
gpg-agent, which reduces the need to
retype passphrases, which makes it more reasonable to have long random
The contents of
pubring.gpg determine who has access to
regpg is designed to be used with version control, so that changes
pubring.gpg are recorded and audited like any other code or
regpg, change reviews are important to protect against
elevation of privilege by an attacker who gains write access to
pubring.gpg. To make this easier,
regpg init git installs a
git diff hook for
regpg does not try to hide secrets; we assume their existence is
equally sensitive as any unencrypted code or configuration that shares
the same repository.
We assume that
gpg encryption is strong enough that we can
promiscuously distribute encrypted secrets via version control and
backups, to keep them safe from accidental lossage.
If all the private decryption keys are lost then access to the secrets
is lost. It is therefore vital to keep
gpg private keys safe.
We try to help
regpg users maintain situational awareness of their
Encryption and decryption are explicit.
There are conventional filenames for encrypted secrets.
There are configuration management idioms for deploying decrypted secrets.
check subcommand lets you verify your mental model matches
regpg takes a couple of measures to reduce the consequences of a
gpg-agent is required (see "decryption keys" above)
helper subcommands avoid writing secrets to disk
This is one of the weak points of
regpg's setup. If you have access
to the private part of a key previously included in
access to the repository, you can still decrypt secrets stored in old
Revoking access to
regpg secrets requires destroying the private
part of the key that was removed from
pubring.gpg. Hence it is a
good idea to use a
If you can't be sure that someone no longer has access to their private key after you revoked their access, you will have to replace all the secrets.
Another weak point.
regpg supports distributed access to secrets.
The only point of audit is access to revision control, but that does
not tell anyone when secrets are decrypted.
Written by Tony Finch email@example.com firstname.lastname@example.org
at Cambridge University Information Services.
You may do anything with this. It has no warranty.