| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
|
|
|
| |
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
|
|
|
|
|
|
| |
We removed SSH support in https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/3553,
so we no longer need the ability to show all refs for Geo nodes.
Closes #115
|
| |
|
|
|
|
|
|
|
| |
Git For Windows 2.14 has a patch that changes `git-upload-pack` to `git upload-pack`.
To make this work for gitlab-shell, just map this to `git-upload-pack`.
Closes gitlab-org/gitlab-ce#36028
|
| |
|
|
|
|
|
|
| |
By default, we hide certain refs (e.g. keep-around/XXX) to save user
download time. We need to preserve these references on secondary Geo
nodes to have a true copy.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
- Wire up gitaly-*-pack to Gitaly. Don't pass git-*-pack to go
- Disable tests for go1.5 & 1.6
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
git_trace_log_file config key
The value of the variable if present must be a writable absolute path. If it’s
not the case we log a proper message and not enable tracing to not throw output to the users.
|
| |
|
| |
|
| |
|
|
|
|
| |
- Required changes to GitLab Shell include the actual handling of the `git-lfs-authenticate` command and the retrieval of the correct credentials.
|
| |
|
| |
|
| |
|
|
|
|
| |
fallback value
|
|
|
|
| |
hooks via SSH
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| | |
Stricter exec cmd
In response to the gitlab-shell 2.6.6-2.6.7 remote code execution
vulnerability.
See merge request !33
|
| | |
|
| |
| |
| |
| |
| | |
Hoping this makes it more obvious when code touches the very
unsafe contents of this variable.
|
| |
| |
| |
| | |
Passing strings to Kernel::exec leads to remote code execution.
|
|\ \
| |/
|/|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Pass $HOME to git as well
[ this patch has the same rationale and reasoning as
https://gitlab.com/gitlab-org/gitlab-workhorse/commit/0d0bd209
details follow ]
Git has 3 places for configs:
- system
- global (per user), and
- local (per repository)
System config location is hardcoded at git compile time (to usually
$prefix/etc/gitconfig). Local configuration is usually picked because we
pass full repo path to subcommand. But global configuration is currently not
picked at all, because HOME env variable is not passed to git.
Pass $HOME through and let git see it's "global" config.
Currently GitLab omnibus stores gitlab user name/email + "autocrlf =
true" in global config, so missing it should not be a blocker for
receive/send-pack operations. But having it is more correct and can be
handy in the future if/when more git operations are done from-under
gitlab-shell.
Having $HOME properly set is also needed when one cannot change system
git config and have to put site-wide configuration into global git
config under $HOME.
That was the case I've hit and the reason for this patch.
/cc @dzaporozhets, @jacobvosmaer
See merge request !32
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
[ this patch has the same rationale and reasoning as
https://gitlab.com/gitlab-org/gitlab-workhorse/commit/0d0bd209
details follow ]
Git has 3 places for configs:
- system
- global (per user), and
- local (per repository)
System config location is hardcoded at git compile time (to usually
$prefix/etc/gitconfig). Local configuration is usually picked because we
pass full repo path to subcommand. But global configuration is currently not
picked at all, because HOME env variable is not passed to git.
Pass $HOME through and let git see it's "global" config.
Currently GitLab omnibus stores gitlab user name/email + "autocrlf =
true" in global config, so missing it should not be a blocker for
receive/send-pack operations. But having it is more correct and can be
handy in the future if/when more git operations are done from-under
gitlab-shell.
Having $HOME properly set is also needed when one cannot change system
git config and have to put site-wide configuration into global git
config under $HOME.
That was the case I've hit and the reason for this patch.
|
|/
|
|
|
|
| |
This reverts commit 8449979ff029af51be0c675c5b6262bc4adc8b3d.
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
|\
| |
| |
| | |
no-init-on-gcryptsetup
|
| |\
| | |
| | |
| | | |
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
| | | |
|
| |/
| |
| |
| |
| |
| | |
through the SSH-protocol
When cleaning this environment variable can be problems with the processing of non-ASCII data
|
|/
|
|
|
| |
'gcryptsetup' is a special git-annex feature that does its own
initialization.
|
| |
|
| |
|
| |
|
| |
|
| |
|