.SH"Usage: Setting up git\-secret in a repository"
These steps cover the basic process of using \fBgit\-secret\fR:
.
.IP"1."4
@ -35,7 +35,7 @@ Later you can decrypt files with the \fBgit secret reveal\fR command, or just sh
.
.IP""0
.
.SS"I want to add someone to the repository"
.SS"Usage: Adding someone to a repository using git\-secret"
.
.IP"1."4
Get their \fBgpg\fR public\-key\.\fBYou won\'t need their secret key\.\fR
@ -68,8 +68,17 @@ The settings available to be changed are:
.
.IP""0
.
.SH"Internals \-\- the <code>\.gitsecret</code> folder"
This folder contains all the information about the data encrypted in this repo, and about which public/private key sets can access the encrypted data\. Use the various \'git secret\' commands to manipulate the files in \fB\.gitsecret\fR, you should not change the data in these files directly\.
.SH"The <code>\.gitsecret</code> folder"
This folder contains information about the files encrypted by git\-secret, and about which public/private key sets can access the encrypted data\.
.
.P
Use the various \'git secret\' commands to manipulate the files in \fB\.gitsecret\fR, you should not change the data in these files directly\.
.
.P
Exactly which files exist in the \.gitsecret folder and what their contents are vary slightly across different versions of gpg\. Thus it is best to use git\-secret with versions of gpg that interoperate well\.
.
.P
Specifically, there is an issue between gpg version 2\.1\.20 and later versions which can cause problems reading and writing keyring files between systems (this shows up in errors like \'gpg: skipped packet of type 12 in keybox\')\.
.
.P
The git\-secret internal data is separated into two directories: