diff options
author | root <root@localhost> | 2013-03-03 09:02:43 +0100 |
---|---|---|
committer | root <root@localhost> | 2013-03-03 09:02:43 +0100 |
commit | 5f7f1afc85a9d8660d204c500042c5399221d426 (patch) | |
tree | 1405dba2aae165da27e3e3c222995c25ef7e272a | |
parent | e1f60d45bbaca68179459944f5a518ceb6f4700d (diff) | |
download | git-remote-gcrypt-5f7f1afc85a9d8660d204c500042c5399221d426.zip git-remote-gcrypt-5f7f1afc85a9d8660d204c500042c5399221d426.tar.gz git-remote-gcrypt-5f7f1afc85a9d8660d204c500042c5399221d426.tar.bz2 |
Use a longer pack key
There should be no difference if we use 32 random bytes or more, since
GPG's longest symmetric key is 32 bytes, but to just remove any doubt we
use a longer random passphrase.
-rwxr-xr-x | git-remote-gcrypt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/git-remote-gcrypt b/git-remote-gcrypt index e0b1133..c31416e 100755 --- a/git-remote-gcrypt +++ b/git-remote-gcrypt @@ -17,7 +17,7 @@ Localdir="${GIT_DIR:=.git}/remote-gcrypt" export GITCEPTION="${GITCEPTION:-}+" # Reuse $Gref except when stacked Gref="refs/gcrypt/gitception$GITCEPTION" Gref_rbranch="refs/heads/master" -Packkey_bytes=33 # 33 random bytes for passphrase, still compatible if changed +Packkey_bytes=63 # nbr random bytes for packfile keys, any >= 256 bit is ok Hashtype=SHA256 # SHA512 SHA384 SHA256 SHA224 supported. Manifestfile=91bd0c092128cf2e60e1a608c31e92caf1f9c1595f83f2890ef17c0e4881aa0a Hex40="[a-f0-9]" |