aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* new versionHEADmasterWolfgang Wiedmeyer2016-03-171-0/+7
| | | | Signed-off-by: Wolfgang Wiedmeyer <wolfgit@wiedmeyer.de>
* remove joeyh patchWolfgang Wiedmeyer2016-03-172-261/+0
| | | | | | It's already his version, so patch is not needed. Signed-off-by: Wolfgang Wiedmeyer <wolfgit@wiedmeyer.de>
* add debian folder from latest debian release (0.20130908-8)Wolfgang Wiedmeyer2016-03-1711-0/+394
| | | | Signed-off-by: Wolfgang Wiedmeyer <wolfgit@wiedmeyer.de>
* Use git's the gpg.program if configuredchrysn2016-02-051-2/+3
| | | | | | | | | | Keyrings managed with gpg2 can contain secret keys whose public part is unavailable to classic gpg; on the other hand, gpg2 won't see keys created in gpg after an initial import. Situations in which error messages like "gpg: error reading key: public key not found" pop up can now be circumvented by setting the gpg.program git configuration entry to gpg2.
* Fix #20.Sebastian Reuße2016-01-221-1/+6
| | | | | | | | | | | | | When a gcrypt remote is not available, for any reason (network being down, the drive containing it not being mounted, etc), pushing to the remote causes a new repository ID to be created. Instead, we now fail loudly when a remote is unavailable and when the remote ID is already set. https://github.com/bluss/git-remote-gcrypt/issues/20 (cherry picked from commit b46d48af15e0f8b89f2666aff2c045c9306305d6)
* added gcrypt.publish-participants configurationJoey Hess2014-07-152-1/+21
| | | | Fixes https://github.com/blake2-ppc/git-remote-gcrypt/issues/9
* fix on OSXJoey Hess2014-05-191-2/+4
| | | | | | | | | | | | | | | | set -e causes the xecho to not run if the xgrep fails. At least with OSX's /bin/sh, which is: GNU bash, version 3.2.51(1)-release (x86_64-apple-darwin13) This didn't happen on Linux with: GNU bash, version 4.3.11(1)-release (x86_64-pc-linux-gnu) Possibly a bug in bash, or an OSX-specific bug. However, disabling set -e in the subshell seems a good idea anyway. fixes https://github.com/blake2-ppc/git-remote-gcrypt/issues/15
* Fix to work when there is no controlling terminal, but GPG_AGENT_INFO is ↵Joey Hess2014-05-151-8/+19
| | | | | | | set. Pass --no-tty to gpg in this situation. This is needed to interoperate with the git-annex assistant, which often runs without a controlling terminal, and will in a new version always do so. Conflicts: debian/changelog
* remove any git config for dummy-gcrypt-check remoteJoey Hess2013-09-271-0/+1
| | | | The gcrypt-id is cached to there when running --check
* stop passing --fast-listJoey Hess2013-09-261-1/+1
| | | | | For unknown reasons, it makes --list-keys sometimes not show fingerprints of certian keys.
* Merge branch 'better_signature_validation' of ↵Joey Hess2013-09-191-5/+10
|\ | | | | | | https://github.com/jburnham/git-remote-gcrypt
| * Better signature validation for subkeys.Justin Burnham2013-09-181-5/+10
| |
* | improve docsJoey Hess2013-09-191-2/+2
| |
* | --check option to see if a repo exists and can be decryptedJoey Hess2013-09-192-8/+36
| | | | | | | | | | | | | | | | This is to allow programs to determine if a repo uses gcrypt, per #6. Since this program already knows the name of the manifest file and how to download it and decrypt it, it makes sense to do the check here rather than in, eg, git-annex.
* | add remote.<name>.gcrypt-signingkey configJoey Hess2013-09-172-4/+8
| | | | | | | | | | | | | | | | | | | | | | | | This is needed by git-annex assistant when it sets up a gcrypt repository, to ensure that the gpg key it was asked to use to encrypt the repo is the same key used to sign it. If it's not, pulling from the repo won't work, due to git-remote-gcrypt's "Only accepting signatories" check. The user may have a global user.signingkey setting (I do), but be setting up a different special-purpose key for encrypting their git repo. The git-annex assistant cannot mess with the global value, so needs this to override it.
* | set --trust-model=always when encryptingJoey Hess2013-09-161-2/+2
|/ | | | | | | | 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
* README: Don't mention keyring files, it's not relevant anymoreroot2013-03-121-3/+1
|
* Remove deprecated /G.XxX.. repository "url fragments" (previously autofixed)root2013-03-081-14/+0
|
* Remove deprecated gcrypt::ssh:// (use rsync instead, previously autofixed)root2013-03-051-8/+0
| | | | | We need to remove this since git handles ssh:// URLs already. With this change, we now use the git backend for these.
* Remove deprecated config gcrypt.keyring (use gcrypt.participants or default)root2013-03-141-10/+1
|
* Simplify by replacing echo_kill with a pipefail functionroot2013-03-091-12/+11
|
* Use directory in /tmp for temporary filesroot2013-03-101-23/+24
| | | | | | | | | 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.
* Add license header and the text of the GNU GPLroot2013-03-033-9/+691
|
* Use a longer pack keyroot2013-03-031-1/+1
| | | | | | 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.
* Encrypt and hash the new packfile streaminglyroot2013-01-251-5/+9
|
* Simplify the use of the object list fileroot2012-11-261-7/+8
|
* Introduce xfeed output functionroot2013-01-071-13/+17
|
* Combine tempfile naming into one functionroot2013-02-031-23/+31
|
* Guard verify-pack and pack-objects and die on errorroot2013-02-221-3/+6
| | | | Use echo_kill for when echo_die is not enough.
* Use pathname expansion only where neededroot2013-02-221-2/+4
|
* Fix GCRYPT_FULL_REPACK to also repack when target has only 1 packroot2012-12-251-1/+1
|
* Simplify PRIVENCRYPTroot2013-02-231-11/+5
|
* Simplify line_count and pick_fieldsroot2013-01-061-15/+10
|
* remove splitcolon useroot2013-02-141-40/+30
|
* use gpg_hashroot2013-01-231-4/+1
|
* Refactor fetch and repackroot2012-11-101-132/+101
|
* More specific pattern for manifest filterroot2012-11-191-2/+2
|
* Use $1, $2 instead of $@ hereroot2013-02-011-1/+1
| | | | | If found a bug in mksh, where it would not split "$@" if IFS is null (reported).
* Fixup cleanup at exitroot2013-01-141-1/+2
|
* Cleanup use of "quotes"root2013-01-221-4/+4
|
* Rename main manifest globals for consistency and symmetryroot2013-02-071-12/+12
|
* Unify filter_to and its negation, also make it faster by direct appendroot2013-02-031-28/+17
|
* Edit wording in READMEroot2013-01-211-7/+7
|
* Code and naming conventions around return variablesroot2013-01-051-64/+68
|
* Use filter_to for pruning Packlist after repackroot2013-01-281-2/+12
|
* Replace wc -l with line_countroot2012-12-171-7/+16
|
* Use filter_to for key_lineroot2012-11-221-1/+2
|
* Fix checking for multiple keysroot2013-01-041-1/+1
|
* Update Branchlist using filter_removeroot2012-11-231-15/+20
|
* Introduce filter_to, pick_fieldsroot2012-12-091-26/+78
|
generated by cgit v1.1 at 2024-12-22 03:55:25 +0000