- Sep 09, 2024
-
-
Archish Thakkar authored
-
- Jan 19, 2024
-
-
Patrick Bajao authored
-
- Jul 10, 2023
-
-
Ash McKenzie authored
-
Ash McKenzie authored
-
- Jun 20, 2023
-
-
- Jan 23, 2023
-
-
- Jul 05, 2022
-
-
Patrick Steinhardt authored
While gitlab-shell currently has a major version of v14, the module path it exposes is not using that major version like it is required by the Go standard. This makes it impossible for dependents to import gitlab-shell as a dependency without using a commit as version. Fix this by changing the module path of gitlab-shell to instead be `gitlab.com/gitlab-org/gitlab-shell/v14` and adjust all imports accordingly. Changelog: fixed
-
- May 19, 2022
-
-
Igor Drozdov authored
- If an integer is specified, we assume that these are seconds - A duration of format "500ms", "10s", "1m", etc... accepted
-
- Mar 07, 2022
-
-
Igor Drozdov authored
When gitlab-sshd has been introduced we've started running our own SSH server. In this case we're able to cache and reuse Gitaly connections and Registry. It helps to reduce memory usage.
-
- Sep 15, 2021
-
-
Igor Drozdov authored
It adds correlation ids wherever possible
-
- Aug 04, 2021
-
-
Nick Thomas authored
- We start supporting the "color" format for logs. - We now respond to SIGHUP by reopening the log file. - We now respect the log format when no log filename is specified. Output to syslog in the event of logging system setup is preserved in OpenSSH mode. Changelog: added
-
- Jul 27, 2021
-
-
Igor Drozdov authored
-
- Jul 26, 2021
-
-
Stan Hu authored
-
- Jul 22, 2021
-
-
Igor Drozdov authored
-
- Jul 19, 2021
-
-
Igor Drozdov authored
They are going to be used to determine whether a server is alive and ready to accept traffic
-
- Jul 15, 2021
-
-
Igor Drozdov authored
When interruption signal is sent, we are closing ssh listener to prevent it from accepting new connections Then after configured grace period, we cancel the context to cancel all ongoing operations
-
- May 17, 2021
-
-
Nick Thomas authored
Previously, opentracing (if configured) was initialized late in the gitlab-shell process's lifespan, coming just before making a gRPC call to Gitaly. By moving the opentracing initialization to be at process startup, we make it available for the whole process lifecycle, which is very useful to gitlab-sshd, as it means we'll only call tracing.Initialize() once on process startup, rather than once per SSH connection. To get this working, we need to introduce a context to gitlab-sshd. This carries the client/service name, but also carries an initial correlation ID. The main outcome of this is that all calls to the authorized_keys endpoint from a given gitlab-sshd process will now share a correlation ID. I don't have a strong opinion about this either way. Changelog: fixed
-
- Apr 30, 2021
-
-
Nick Thomas authored
Changelog: fixed
-
- Feb 16, 2021
-
-
Ben Kochie authored
Add a basic monitoring endpoint to the sshd command. * Listen on localhost port 9122 by default. * Integrate build/version info. * Update example config. https://gitlab.com/gitlab-org/gitlab-shell/-/issues/121 Signed-off-by:
Ben Kochie <superq@gmail.com>
-
Ben Kochie authored
Use "omitempty" to allow defaults in the config file to be correctly passed. Without this, explicitly setting an empty default like an empty string will not work. Needed in order to allow explicitly disabling some settings. Related to: https://gitlab.com/gitlab-org/gitlab-shell/-/issues/121 Signed-off-by:
Ben Kochie <superq@gmail.com>
-
- Jan 18, 2021
-
-
Lorenz Brun authored
-