| Commit message (Collapse) | Author | Age |
|
|
|
| |
git-annex. Closes https://github.com/blake2-ppc/git-remote-gcrypt/issues/3
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Otherwise gpg may prompt to verify if we want to encrypt to users who
do not have a defined trust level. But, the participants setting
explicitly listed them, so we know we want to encrypt to them.
closes #3
|
|/ |
|
| |
|
| |
|
|
|
|
|
| |
We need to remove this since git handles ssh:// URLs already. With this
change, we now use the git backend for these.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Using a standard directory for temporaries buys us performance when the
user wants it (has configured tmpfs for /tmp) and configurability
(accepts TMPDIR=).
Moving /pack to a temporary directory gives safe concurrent remote
repacks.
|
| |
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Use echo_kill for when echo_die is not enough.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
If found a bug in mksh, where it would not split "$@" if IFS is null
(reported).
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|