SSH Agent Issue on 1Password Beta

Forum|Forum|2 years ago
August 19, 2023
4 replies
121 views

I updated to the Beta version of 1Password (1Password for Mac 8.10.12 (81012010)) and I'm experiencing an issue with the SSH agent.
Whenever attempting to login to a Git Remote (GitLab) the SSH agent will first prompt for the Commit Signing key, which If I authorize authentication will fail.
The only way around this is to press esc when the commit signing key prompt comes up and it will then offer me the authentication key.

1Password Version: 8.10.12
Extension Version: Not Provided
OS Version: macOS 13.5
Browser: Not Provided

SSH

floris_1P

1Password Employee

Does this happen with a GitLab.com remote or a self-hosted GitLab instance?

A

Anonymous

@floris_1P A self-hosted GitLab instance

floris_1P

1Password Employee

There is a bug where GitLab's sshd server on self-hosted instances incorrectly accepts signing keys which then still get rejected (as they should).

To work around that, you can configure the SSH agent to first offer the auth key and then the signing key. To do this, you can create an SSH agent config file.

A

Anonymous

That fixed it. Thanks @floris_1P ! Looks like GitLab has closed that issue though which is unfortunate.

Sign up

1Password employees: Sign in with SSO

Login to the community

1Password employees: Sign in with SSO

Scanning file for viruses.

This file cannot be downloaded