[ https://issues.apache.org/jira/browse/SSHD-1270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17555195#comment-17555195 ]
CY edited comment on SSHD-1270 at 6/16/22 5:02 PM: --------------------------------------------------- Sorry for typo: it's eval "$(ssh-agent -s)" && ssh-add And i think you're right. i never thought there is another thing like "gnome-keyring" could also act as ssh-agent. Before I think "ssh-agent" is the only agent. Now it can explain everything # Ubuntu 16.04 use "gnome-keyring" as default ssh-agent. Which can be check in the screenshot above. When authentication failed, the SSH_AUTH_SOCK is /run/user/1000/keyring/ssh # unset SSH_AUTH_SOCK makes it works again because it doesn't use gnome-keyring anymore # Or relaunch ssh-agent by `eval "ssh-agent" && ssh-add`. It also works because it changed SSH_AUTH_SOCK to ssh-agent. I will make a confirmation tomorrow. If everything is right above. Then the best solution should be [disabling gnome-keyring as ssh-agent.|https://wiki.gnome.org/Projects/GnomeKeyring/Ssh#:~:text=Gnome%20Keyring%20includes%20an%20SSH,variable%20when%20it%20starts%20up.] was (Author: JIRAUSER291093): Sorry for typo: it's eval "$(ssh-agent -s)" && ssh-add And i think you're right. i never thought there is another thing like "gnome-keyring" could also act as ssh-agent. Before I think "ssh-agent" is the only agent. Now it can explain everything # Ubuntu 16.04 use "gnome-keyring" as default ssh-agent. Which can be check in the screenshot above. When authentication failed, the SSH_AUTH_SOCK is /run/user/1000/keyring/ssh # unset SSH_AUTH_SOCK makes it works again because it doesn't use gnome-keyring anymore # Or relaunch ssh-agent by `eval "ssh-agent" && ssh-add`. It also works because it changed SSH_AUTH_SOCK to ssh-agent. I will make a confirmation tomorrow. If everything is right above. Then the base solution should be disable gnome-keyring as ssh-agent. > MINA-SSHD 2.8.0 break Ubuntu 16.04 users connection > --------------------------------------------------- > > Key: SSHD-1270 > URL: https://issues.apache.org/jira/browse/SSHD-1270 > Project: MINA SSHD > Issue Type: Bug > Affects Versions: 2.8.0 > Reporter: CY > Priority: Major > Attachments: 1, image-2022-06-16-23-02-11-970.png > > > steps to reproduce: > 1.upgrade Gerrit to 3.6 (which use 2.8.0 SSHD > 2.Ubuntu 16.04 user try to connect Gerrit via ssh > `ssh -p 29418 usern...@gerrit.mioffice.cn gerrit` > 3.Got "Permission denied (publickey)." > 4.execute eval "$(ssh-agent -s) && ssh-add" > 5.`ssh -p 29418 usern...@gerrit.mioffice.cn gerrit` now can connect to > Gerrit correctly. > 6.Reboot the PC, then cannot connect again, and need to execute "eval > "$(ssh-agent -s) && ssh-add"" again. > > Here is my client log with `ssh -vvv` > There is also a discussion on Gerrit community and there is server side log > on it > https://bugs.chromium.org/p/gerrit/issues/detail?id=15987#c_ts1655281861 -- This message was sent by Atlassian Jira (v8.20.7#820007) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org For additional commands, e-mail: dev-h...@mina.apache.org