Summary: | ASTERISK-29333: Can't use SSH with gerrit | ||
Reporter: | Brian J. Murrell (brian_j_murrell) | Labels: | |
Date Opened: | 2021-03-09 06:12:18.000-0600 | Date Closed: | 2021-03-09 06:35:04.000-0600 |
Priority: | Major | Regression? | Yes |
Status: | Closed/Complete | Components: | General |
Versions: | 18.2.2 | Frequency of Occurrence | Constant |
Related Issues: | |||
Environment: | Attachments: | ||
Description: | Apologies for opening this issue here but I could not find any other means of contact for Gerrit issues.
I have my account set up and have submitted patches before, however my SSH access no longer seems to be working, despite my having an SSH key uploaded to my profile. Here's my .ssh/config: {noformat} Host asterisk HostName gerrit.asterisk.org Port 29418 User brian_j_murrell PubkeyAcceptedKeyTypes +ssh-dss {noformat} and here is what trying to ssh to Gerrit says: {noformat} debug1: Authenticating to gerrit.asterisk.org:29418 as 'brian_j_murrell' debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: algorithm: ecdh-sha2-nistp256 debug1: kex: host key algorithm: rsa-sha2-512 debug1: kex: server->client cipher: aes256-ctr MAC: hmac-sha2-256-etm@openssh.com compression: none debug1: kex: client->server cipher: aes256-ctr MAC: hmac-sha2-256-etm@openssh.com compression: none debug1: kex: ecdh-sha2-nistp256 need=32 dh_need=32 debug1: kex: ecdh-sha2-nistp256 need=32 dh_need=32 debug1: expecting SSH2_MSG_KEX_ECDH_REPLY debug1: Server host key: ssh-rsa SHA256:pK8Lib9M6vzy49IUucoMkd3KNnsXIidqC0KN4v9aFuE debug1: Host '[gerrit.asterisk.org]:29418' is known and matches the RSA host key. debug1: Found key in /home/brian/.ssh/known_hosts:706 debug1: rekey out after 4294967296 blocks debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: rekey in after 4294967296 blocks debug1: Will attempt key: /home/brian/.ssh/id_ed25519 ED25519 SHA256:Kq5F1/gDZUfmovUWcJfF5aQBtmYDtXHSpIZzqUFVkSs agent debug1: Will attempt key: /home/brian/.ssh/id_rsa RSA SHA256:pnmnK9RPpG5wiIAq+lTRVr2Ojoct9f3/013zKgVmh+w agent debug1: Will attempt key: /home/brian/.ssh/id_dsa DSA SHA256:evtsThdrqDDuHGTHsdo0xJRO/gn4g9A6XHlDyhUQYLs agent debug1: Will attempt key: /home/brian/.ssh/id_ecdsa debug1: Will attempt key: /home/brian/.ssh/id_ecdsa_sk debug1: Will attempt key: /home/brian/.ssh/id_ed25519_sk debug1: Will attempt key: /home/brian/.ssh/id_xmss debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey debug1: Next authentication method: publickey debug1: Offering public key: /home/brian/.ssh/id_ed25519 ED25519 SHA256:Kq5F1/gDZUfmovUWcJfF5aQBtmYDtXHSpIZzqUFVkSs agent debug1: Authentications that can continue: publickey debug1: Offering public key: /home/brian/.ssh/id_rsa RSA SHA256:pnmnK9RPpG5wiIAq+lTRVr2Ojoct9f3/013zKgVmh+w agent debug1: Authentications that can continue: publickey debug1: Offering public key: /home/brian/.ssh/id_dsa DSA SHA256:evtsThdrqDDuHGTHsdo0xJRO/gn4g9A6XHlDyhUQYLs agent debug1: Authentications that can continue: publickey debug1: Trying private key: /home/brian/.ssh/id_ecdsa debug1: Trying private key: /home/brian/.ssh/id_ecdsa_sk debug1: Trying private key: /home/brian/.ssh/id_ed25519_sk debug1: Trying private key: /home/brian/.ssh/id_xmss debug1: No more authentication methods to try. brian_j_murrell@gerrit.asterisk.org: Permission denied (publickey). {noformat} So as you can see, even though it is sending ssh keys, ultimately my ssh client is denied. It's the first key: {noformat} debug1: Offering public key: /home/brian/.ssh/id_ed25519 ED25519 SHA256:Kq5F1/gDZUfmovUWcJfF5aQBtmYDtXHSpIZzqUFVkSs agent {noformat} that I have uploaded to my profile in Gerrit. | ||
Comments: | By: Asterisk Team (asteriskteam) 2021-03-09 06:12:19.807-0600 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur. Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/]. By: Joshua C. Colp (jcolp) 2021-03-09 06:25:17.916-0600 Your username appears to be "brian_j_miurrell". Note the "i" in "miurrell". If you use that, does it work? By: Brian J. Murrell (brian_j_murrell) 2021-03-09 06:32:41.067-0600 ~sigh~ And here I was thinking that that was a typo in my {{.ssh/config}} and removed the erroneous {{i}}. It does work if I put that erroneous {{i}} back in. Thanks. |