summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar http://joeyh.name/ <http://joeyh.name/@web>2013-12-12 19:27:23 +0000
committerGravatar admin <admin@branchable.com>2013-12-12 19:27:23 +0000
commitec1317bbff9785eade8a8a07624e99a5ef5ebeae (patch)
treee4efe584d8b3ad6d94c04d0960ac8dbf1039452d
parent12e68a4a8cf558aa787c1b26a9d9d9d9d2d60299 (diff)
Added a comment
-rw-r--r--doc/tips/fully_encrypted_git_repositories_with_gcrypt/comment_12_b697b2ab10705b090a78e7717ec59b18._comment10
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/tips/fully_encrypted_git_repositories_with_gcrypt/comment_12_b697b2ab10705b090a78e7717ec59b18._comment b/doc/tips/fully_encrypted_git_repositories_with_gcrypt/comment_12_b697b2ab10705b090a78e7717ec59b18._comment
new file mode 100644
index 000000000..182b5eabb
--- /dev/null
+++ b/doc/tips/fully_encrypted_git_repositories_with_gcrypt/comment_12_b697b2ab10705b090a78e7717ec59b18._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="http://joeyh.name/"
+ ip="209.250.56.87"
+ subject="comment 12"
+ date="2013-12-12T19:27:23Z"
+ content="""
+@Peter, in your example, it *is* going to use your gpg key to encrypt files. gpg is being used to generate a 256 bit random value (not a key), which will be used as a random seed for HMAC scrambling of the keys stored in the encrypted special remote.
+
+If that's taking too long to generate for your liking, you can pass --fast, which will make gpg use /dev/urandom to generate it rather than /dev/random.
+"""]]