aboutsummaryrefslogtreecommitdiffhomepage
path: root/git-remote-gcrypt
Commit message (Collapse)AuthorAge
* rename new config keySean Whitton2020-07-24
| | | | Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
* avoid bashismSean Whitton2020-07-24
| | | | | | git-remote-gcrypt is POSIX sh. Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
* add some blank lines back inSean Whitton2020-07-24
| | | | Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
* git config to request abort if --force not passedJay Colson2020-07-24
| | | | | | Default to emit a warning if the git config flag is not set. Signed-off-by: Jay Colson <jay@karma.net>
* Add git-config option to set rsync put flagsTravis Chen2020-02-08
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Provide the ability to pass flags to `rsync` when uploading. There are two ways to set the configuration: - `gcrypt.rsync-put-flags` - `remote.<name>.gcrypt-rsync-put-flags` The flags will be applied to `rsync` during uploading when using the `rsync://` backend. If `remote.<name>.gcrypt-rsync-put-flags` is set, the flags set in `gcrypt.rsync-put-flags` will not be applied to the remote `<name>`. This change also includes documentation. We have tested with the following configurations: 1. none set 2. `git config gcrypt.rsync-put-flags "--perms --chmod=g+rX"` 3. `git config remote.<name>.rsync-put-flags "--perms --chmod=o+rX"` 4. both (2) and (3) All local files start with only owner permissions set, and umask is set to 077. In (1), no change in behavior as before, as expected. In (2), the remote files have the group permissions set, as expected. In (3), the remote files have the other permissions set, as expected. In (4), the remote files have the other permissions set, but do not have the group permissions set, as expected. Signed-off-by: Travis Chen <travis.chen@everchanging.dev>
* don't echo external command errors unless repo ID is setSean Whitton2018-11-26
| | | | | | | Otherwise you'll get the error output whenever you push to a new remote. Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
* bump copyright yearsSean Whitton2018-11-24
|
* output stderr from other commands when the repository is not foundSean Whitton2018-11-24
| | | | | | Closes: #914059 Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
* tweak & move experimental warning msgSean Whitton2018-04-28
| | | | | | Move it to where the repository format notice used to be. Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
* Add support for several cloud storage remotes using rcloneBeren Minor2018-04-28
| | | | | | | | | | rclone is an open-source command-line too to get and put files to several cloud storage services that aren't supported by rsync. git-remote-gcrypt can now push encrypted repositories to any configured rclone remote using gcrypt::rclone://<rclone-repo>:<folder> URLs. Signed-off-by: Beren Minor <beren.minor+git@gmail.com>
* on mingw64, 'mkdir -m 700' does not workSteven R. Loomis2017-09-28
| | | | * workaround: skip the '-m 700' on mingw64/32 and msys
* fix bug when using several options in gpg-argsEtienne Brodu2017-03-23
|
* add authorship to script headerSean Whitton2016-07-05
|
* suppress warning about keyid matching multiple fpsSean Whitton2016-07-04
| | | | | Based on commit a72eb5d9520a8d7fa23478aeb1c14a14e66c19a2 by Raphaël Droz's fork -- thanks.
* pass gcrypt.gpg-args most robustlySean Whitton2016-07-04
|
* Fix #20.Sebastian Reuße2016-07-04
| | | | | | | | | | | | | 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)
* GCRYPT_GPG_ARGS env var -> gcrypt.gpg-args confSean Whitton2016-07-04
|
* Merge remote-tracking branch 'chrysn/master' into develSean Whitton2016-01-17
|\
| * Use git's the gpg.program if configuredchrysn2015-12-21
| | | | | | | | | | | | | | | | | | | | 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.
* | implement GCRYPT_GPG_ARGSSean Whitton2016-01-17
| |
* | changelog entry for version 1.0.0!Sean Whitton2016-01-17
|/
* added gcrypt.publish-participants configurationJoey Hess2014-07-15
| | | | Fixes https://github.com/blake2-ppc/git-remote-gcrypt/issues/9
* fix on OSXJoey Hess2014-05-19
| | | | | | | | | | | | | | | | 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-15
| | | | | | | 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-27
| | | | The gcrypt-id is cached to there when running --check
* stop passing --fast-listJoey Hess2013-09-26
| | | | | For unknown reasons, it makes --list-keys sometimes not show fingerprints of certian keys.
* Merge branch 'better_signature_validation' of ↵Joey Hess2013-09-19
|\ | | | | | | https://github.com/jburnham/git-remote-gcrypt
| * Better signature validation for subkeys.Justin Burnham2013-09-18
| |
* | --check option to see if a repo exists and can be decryptedJoey Hess2013-09-19
| | | | | | | | | | | | | | | | 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-17
| | | | | | | | | | | | | | | | | | | | | | | | 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-16
|/ | | | | | | | 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
* Remove deprecated /G.XxX.. repository "url fragments" (previously autofixed)root2013-03-08
|
* Remove deprecated gcrypt::ssh:// (use rsync instead, previously autofixed)root2013-03-05
| | | | | 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-14
|
* Simplify by replacing echo_kill with a pipefail functionroot2013-03-09
|
* Use directory in /tmp for temporary filesroot2013-03-10
| | | | | | | | | 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-03
|
* Use a longer pack keyroot2013-03-03
| | | | | | 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-25
|
* Simplify the use of the object list fileroot2012-11-26
|
* Introduce xfeed output functionroot2013-01-07
|
* Combine tempfile naming into one functionroot2013-02-03
|
* Guard verify-pack and pack-objects and die on errorroot2013-02-22
| | | | Use echo_kill for when echo_die is not enough.
* Use pathname expansion only where neededroot2013-02-22
|
* Fix GCRYPT_FULL_REPACK to also repack when target has only 1 packroot2012-12-25
|
* Simplify PRIVENCRYPTroot2013-02-23
|
* Simplify line_count and pick_fieldsroot2013-01-06
|
* remove splitcolon useroot2013-02-14
|
* use gpg_hashroot2013-01-23
|
* Refactor fetch and repackroot2012-11-10
|
generated by cgit v1.2.3 (git 2.39.1) at 2024-05-01 18:31:19 +0000