<feed xmlns='http://www.w3.org/2005/Atom'>
<title>delta/gitlab/gitlab-shell.git, branch jv-ssh-sidechannel</title>
<subtitle>gitlab.com: gitlab-org/gitlab-shell.git
</subtitle>
<link rel='alternate' type='text/html' href='http://91.123.203.49/cgit/delta/gitlab/gitlab-shell.git/'/>
<entry>
<title>Optionally use SSHUploadPackWithSidechannel</title>
<updated>2022-01-21T11:05:19+00:00</updated>
<author>
<name>Jacob Vosmaer</name>
<email>jacob@gitlab.com</email>
</author>
<published>2022-01-21T11:05:19+00:00</published>
<link rel='alternate' type='text/html' href='http://91.123.203.49/cgit/delta/gitlab/gitlab-shell.git/commit/?id=d005af25ab3224efa0d23be53858710f77e672c6'/>
<id>d005af25ab3224efa0d23be53858710f77e672c6</id>
<content type='text'>
If the GitLab API returns an allowed response with use_sidechannel set
to true, gitlab-shell will establish a sidechannel connection and use
SSHUploadPackWithSidechannel instead of SSHUploadPack. This is an
efficiency improvement.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
If the GitLab API returns an allowed response with use_sidechannel set
to true, gitlab-shell will establish a sidechannel connection and use
SSHUploadPackWithSidechannel instead of SSHUploadPack. This is an
efficiency improvement.
</pre>
</div>
</content>
</entry>
<entry>
<title>Update gitaly/v14/client to 2e398afa0490ccdf5a82e1a7c7d824ae491eba16</title>
<updated>2022-01-21T10:40:19+00:00</updated>
<author>
<name>Jacob Vosmaer</name>
<email>jacob@gitlab.com</email>
</author>
<published>2022-01-21T10:31:41+00:00</published>
<link rel='alternate' type='text/html' href='http://91.123.203.49/cgit/delta/gitlab/gitlab-shell.git/commit/?id=bc25e92dd824591688cbe88cbbeb891b6459b9a9'/>
<id>bc25e92dd824591688cbe88cbbeb891b6459b9a9</id>
<content type='text'>
This updates the Gitaly client go.mod dependency to Gitaly commit
2e398afa0490ccdf5a82e1a7c7d824ae491eba16. This causes a grpc-go
version bump, and hence a minor change in some of our test code.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This updates the Gitaly client go.mod dependency to Gitaly commit
2e398afa0490ccdf5a82e1a7c7d824ae491eba16. This causes a grpc-go
version bump, and hence a minor change in some of our test code.
</pre>
</div>
</content>
</entry>
<entry>
<title>Support parsing `use_sidechannel` API response field</title>
<updated>2022-01-21T10:39:16+00:00</updated>
<author>
<name>Jacob Vosmaer</name>
<email>jacob@gitlab.com</email>
</author>
<published>2022-01-21T10:37:27+00:00</published>
<link rel='alternate' type='text/html' href='http://91.123.203.49/cgit/delta/gitlab/gitlab-shell.git/commit/?id=3384ce876de3fa8ac0c8fd4efd471e7fba8e43b9'/>
<id>3384ce876de3fa8ac0c8fd4efd471e7fba8e43b9</id>
<content type='text'>
This field will act as a feature flag that controls whether
gitlab-shell uses the old SSHUploadPack RPC or the new
SSHUploadPackWithSidechannel.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This field will act as a feature flag that controls whether
gitlab-shell uses the old SSHUploadPack RPC or the new
SSHUploadPackWithSidechannel.
</pre>
</div>
</content>
</entry>
<entry>
<title>Refactor client response tests</title>
<updated>2022-01-20T16:32:59+00:00</updated>
<author>
<name>Jacob Vosmaer</name>
<email>jacob@gitlab.com</email>
</author>
<published>2022-01-20T15:36:28+00:00</published>
<link rel='alternate' type='text/html' href='http://91.123.203.49/cgit/delta/gitlab/gitlab-shell.git/commit/?id=2cf1af8e042f7e30d1e9f81c368e00fa0348a51e'/>
<id>2cf1af8e042f7e30d1e9f81c368e00fa0348a51e</id>
<content type='text'>
This reduces coupling between tests in
internal/gitlabnet/accessverifier/client_test.go, and will make it
easier to add new test cases in the future.

Note that the test server had a special behavior for the username
"second", but this was never used. So we removed that behavior in this
commit.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This reduces coupling between tests in
internal/gitlabnet/accessverifier/client_test.go, and will make it
easier to add new test cases in the future.

Note that the test server had a special behavior for the username
"second", but this was never used. So we removed that behavior in this
commit.
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge branch 'id-deprecate-self-signed-cert' into 'main'</title>
<updated>2022-01-13T02:13:00+00:00</updated>
<author>
<name>Ash McKenzie</name>
<email>amckenzie@gitlab.com</email>
</author>
<published>2022-01-13T02:13:00+00:00</published>
<link rel='alternate' type='text/html' href='http://91.123.203.49/cgit/delta/gitlab/gitlab-shell.git/commit/?id=da719e7d9abe52e56b3b03ffa34b0ede5090ce99'/>
<id>da719e7d9abe52e56b3b03ffa34b0ede5090ce99</id>
<content type='text'>
Deprecate self_signed_cert config setting

See merge request gitlab-org/gitlab-shell!552</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Deprecate self_signed_cert config setting

See merge request gitlab-org/gitlab-shell!552</pre>
</div>
</content>
</entry>
<entry>
<title>Deprecate self_signed_cert config setting</title>
<updated>2022-01-12T14:19:44+00:00</updated>
<author>
<name>Igor Drozdov</name>
<email>idrozdov@gitlab.com</email>
</author>
<published>2022-01-12T14:15:18+00:00</published>
<link rel='alternate' type='text/html' href='http://91.123.203.49/cgit/delta/gitlab/gitlab-shell.git/commit/?id=537f8e192908172863e93a97871409a8f043c292'/>
<id>537f8e192908172863e93a97871409a8f043c292</id>
<content type='text'>
The option isn't required to accept self-signed certs

On the other hand, if the option set to true it makes
machine-in-the-middle attack possible

Let's clarify it in the code that the option is deprecated
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The option isn't required to accept self-signed certs

On the other hand, if the option set to true it makes
machine-in-the-middle attack possible

Let's clarify it in the code that the option is deprecated
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge branch 'wc-intern-err' into 'main'</title>
<updated>2022-01-05T11:01:22+00:00</updated>
<author>
<name>Igor Drozdov</name>
<email>idrozdov@gitlab.com</email>
</author>
<published>2022-01-05T11:01:22+00:00</published>
<link rel='alternate' type='text/html' href='http://91.123.203.49/cgit/delta/gitlab/gitlab-shell.git/commit/?id=4989011bedc7c33aa49cdac3c230ae9fdcdb49fd'/>
<id>4989011bedc7c33aa49cdac3c230ae9fdcdb49fd</id>
<content type='text'>
Suppress internal errors in client output

See merge request gitlab-org/gitlab-shell!549</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Suppress internal errors in client output

See merge request gitlab-org/gitlab-shell!549</pre>
</div>
</content>
</entry>
<entry>
<title>Suppress internal errors in client output</title>
<updated>2021-12-28T21:06:19+00:00</updated>
<author>
<name>Will Chandler</name>
<email>wchandler@gitlab.com</email>
</author>
<published>2021-12-10T14:55:07+00:00</published>
<link rel='alternate' type='text/html' href='http://91.123.203.49/cgit/delta/gitlab/gitlab-shell.git/commit/?id=3a8bab437d8d0fd9bfa29bc5edd07ae5903af84d'/>
<id>3a8bab437d8d0fd9bfa29bc5edd07ae5903af84d</id>
<content type='text'>
Until recently, Gitaly was silently swallowing any errors returned by
SSH `git upload-pack` processes. Clients would still receive stderr
output and a non-zero return code, but Gitlab-Shell would receive error
as nil and log success.

With 9deaf47f1ecb00f0f36d18ee4a0fb1576f5a0efe Gitaly will now return an
error when git fails, but this causes Gitlab-Shell to print out the
GRPC error code as a message to the client:

&gt; fatal: couldn't find remote ref not-a-real-ref
&gt; fatal: the remote end hung up unexpectedly
&gt; remote:
&gt; remote:
&gt; ========================================================================
&gt; remote:
&gt; remote: rpc error: code = Internal desc = SSHUploadPack: exit status 128
&gt; remote:
&gt; remote:
&gt; ========================================================================
&gt; remote:

The `remote:` text gives no additional context for the user and adds
clutter.

This commit suppresses the additional message added by Gitlab-Shell on
failure when the error type is `Internal`, returning client output to
the format it was prior to the Gitaly change.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Until recently, Gitaly was silently swallowing any errors returned by
SSH `git upload-pack` processes. Clients would still receive stderr
output and a non-zero return code, but Gitlab-Shell would receive error
as nil and log success.

With 9deaf47f1ecb00f0f36d18ee4a0fb1576f5a0efe Gitaly will now return an
error when git fails, but this causes Gitlab-Shell to print out the
GRPC error code as a message to the client:

&gt; fatal: couldn't find remote ref not-a-real-ref
&gt; fatal: the remote end hung up unexpectedly
&gt; remote:
&gt; remote:
&gt; ========================================================================
&gt; remote:
&gt; remote: rpc error: code = Internal desc = SSHUploadPack: exit status 128
&gt; remote:
&gt; remote:
&gt; ========================================================================
&gt; remote:

The `remote:` text gives no additional context for the user and adds
clutter.

This commit suppresses the additional message added by Gitlab-Shell on
failure when the error type is `Internal`, returning client output to
the format it was prior to the Gitaly change.
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge branch 'wc-sshd-upload-pack' into 'main'</title>
<updated>2021-12-28T10:09:52+00:00</updated>
<author>
<name>Igor Drozdov</name>
<email>idrozdov@gitlab.com</email>
</author>
<published>2021-12-28T10:09:52+00:00</published>
<link rel='alternate' type='text/html' href='http://91.123.203.49/cgit/delta/gitlab/gitlab-shell.git/commit/?id=3038ae450383e63d9672f1b1d2f27995d2160bbc'/>
<id>3038ae450383e63d9672f1b1d2f27995d2160bbc</id>
<content type='text'>
Send full git request/response in SSHD tests

See merge request gitlab-org/gitlab-shell!550</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Send full git request/response in SSHD tests

See merge request gitlab-org/gitlab-shell!550</pre>
</div>
</content>
</entry>
<entry>
<title>Send full git request/response in SSHD tests</title>
<updated>2021-12-22T19:00:15+00:00</updated>
<author>
<name>Will Chandler</name>
<email>wchandler@gitlab.com</email>
</author>
<published>2021-12-22T18:30:21+00:00</published>
<link rel='alternate' type='text/html' href='http://91.123.203.49/cgit/delta/gitlab/gitlab-shell.git/commit/?id=922bb8ff61578a68126ba215e94e0c3d4c34bbf9'/>
<id>922bb8ff61578a68126ba215e94e0c3d4c34bbf9</id>
<content type='text'>
Before 9deaf47f1ecb00f0f36d18ee4a0fb1576f5a0efe, Gitaly would return
success for `SSHUploadPack` and `SSHUploadArchive` regardless of the
exit code of the `git upload-pack|archive` process. As a result, the
gitlab-sshd acceptance tests could rely on no errors being returned from
Gitaly.

Currently these tests send the minimum request needed to start a
session, causing the server git process to fail as the `0000` flush
packet to end the session is never sent.

This commit fixes the tests by sending the full request/response needed
for a successful git operation.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Before 9deaf47f1ecb00f0f36d18ee4a0fb1576f5a0efe, Gitaly would return
success for `SSHUploadPack` and `SSHUploadArchive` regardless of the
exit code of the `git upload-pack|archive` process. As a result, the
gitlab-sshd acceptance tests could rely on no errors being returned from
Gitaly.

Currently these tests send the minimum request needed to start a
session, causing the server git process to fail as the `0000` flush
packet to end the session is never sent.

This commit fixes the tests by sending the full request/response needed
for a successful git operation.
</pre>
</div>
</content>
</entry>
</feed>
