diff options
| author |  Mesar Hameed <mesar.hameed@gmail.com> | 2014-07-19 23:57:04 +0100 |
|---|---|---|
| committer | Mesar Hameed <mesar.hameed@gmail.com> | 2014-07-19 23:57:04 +0100 |
| commit | 38d8e57b0e1898a9b55bb8626dd2acef40c1c98b (patch) | |
| tree | 1b7b364326792fd70a2ba743dc9b20d7b01651c3 /doc/tips | |
| parent | dac4c3e055d59ed67a088b0ea34a56011c757131 (diff) | |
fix typos.
Diffstat (limited to 'doc/tips')
2 files changed, 2 insertions, 2 deletions
diff --git a/doc/tips/fully_encrypted_git_repositories_with_gcrypt/comment_10_4440a80d64c60c7312d5c405d54e607a._comment b/doc/tips/fully_encrypted_git_repositories_with_gcrypt/comment_10_4440a80d64c60c7312d5c405d54e607a._comment index 4ee70bcd7..b1031646f 100644 --- a/doc/tips/fully_encrypted_git_repositories_with_gcrypt/comment_10_4440a80d64c60c7312d5c405d54e607a._comment +++ b/doc/tips/fully_encrypted_git_repositories_with_gcrypt/comment_10_4440a80d64c60c7312d5c405d54e607a._comment @@ -9,7 +9,7 @@ Sorry, I ment that the file containing the symmetric encryption key should obviously not be used to encrypt itself, it would be stored in the repository \"unencrypted\" (but protected with a passphrase) -> store a non-encrypted gpg key alongside the repsitory encrypted with it, but then you have to rely on a passphrase for all your security. +> store a non-encrypted gpg key alongside the repository encrypted with it, but then you have to rely on a passphrase for all your security. Exactly. I think such a mode be a great addition. It might not be as secure as encryption based on a private key - depending on the passphrase strength -, but it would certainly be a lot more convenient and portable (and still much more secure than the shared encryption method). """]] diff --git a/doc/tips/fully_encrypted_git_repositories_with_gcrypt/comment_9_3784e0c828cd60b6a9075c2d32d070cc._comment b/doc/tips/fully_encrypted_git_repositories_with_gcrypt/comment_9_3784e0c828cd60b6a9075c2d32d070cc._comment index 24e5f5b83..7a452e8f0 100644 --- a/doc/tips/fully_encrypted_git_repositories_with_gcrypt/comment_9_3784e0c828cd60b6a9075c2d32d070cc._comment +++ b/doc/tips/fully_encrypted_git_repositories_with_gcrypt/comment_9_3784e0c828cd60b6a9075c2d32d070cc._comment @@ -8,7 +8,7 @@ Then you would need to decrypt the repository in order get the key you need to decrypt the repository. The impossibility of this design is why I didn't do that! -It would certainly be possible to store a non-encrypted gpg key alongside the repsitory encrypted with it, but then you have to rely on a passphrase for all your security. +It would certainly be possible to store a non-encrypted gpg key alongside the repository encrypted with it, but then you have to rely on a passphrase for all your security. You should file a bug report for the bug you saw.. """]] |