Add recommendation for using a private repository

This commit is contained in:
Tim Byrne 2015-07-17 02:29:20 -05:00
parent 2ede46f5e4
commit 135ed8d4b7
2 changed files with 8 additions and 3 deletions

3
yadm.1
View File

@ -336,6 +336,9 @@ and provide the correct password.
After files are decrypted, permissions are automatically updated as described After files are decrypted, permissions are automatically updated as described
in the PERMISSIONS section. in the PERMISSIONS section.
.BR NOTE :
It is recommended that you keep confidential files in a private repository,
even though they are encrypted.
.SH PERMISSIONS .SH PERMISSIONS
When files are checked out of a Git repository, their initial permissions are When files are checked out of a Git repository, their initial permissions are
dependent upon the user's umask. This can result in confidential files with lax permissions. dependent upon the user's umask. This can result in confidential files with lax permissions.

View File

@ -214,6 +214,8 @@
provide the correct password. After files are decrypted, permissions provide the correct password. After files are decrypted, permissions
are automatically updated as described in the PERMISSIONS section. are automatically updated as described in the PERMISSIONS section.
NOTE: It is recommended that you keep confidential files in a private
repository, even though they are encrypted.
## PERMISSIONS ## PERMISSIONS
When files are checked out of a Git repository, their initial permis- When files are checked out of a Git repository, their initial permis-