Menu

#28 No ssh-agent could be contacted

open
nobody
None
5
2018-09-17
2018-09-16
sergio
No
$ sudo ls  # works
...

/var/log/auth.log:
sudo: pam_ssh_agent_auth: Beginning pam_ssh_agent_auth for user sergio
sudo: pam_ssh_agent_auth: Attempting authentication: `sergio' as 
`sergio' using /etc/ssh/sudo_authorized_keys
sudo: pam_ssh_agent_auth: Contacted ssh-agent of user sergio (1000)

$ /usr/bin/sudo ls # does not work
...

/var/log/auth.log:
sudo: pam_ssh_agent_auth: Beginning pam_ssh_agent_auth for user sergio
sudo: pam_ssh_agent_auth: Attempting authentication: `sergio' as 
`sergio' using /etc/ssh/sudo_authorized_keys
sudo: pam_ssh_agent_auth: No ssh-agent could be contacted

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902056

Discussion

  • sergio

    sergio - 2018-09-16

    Really I'm already not sure if this is a bug as sudo is alias to sudo -E, and $ /usr/bin/sudo -E ls works.

     

    Last edit: sergio 2018-09-16
  • sergio

    sergio - 2018-09-16

    But at leas I'm not able to run user shell with user's home.
    sudo -su user doesn't work and sudo -Esu user saves my $HOME (and all my other env).

     
  • sergio

    sergio - 2018-09-17

    This is a bug!

    /usr/bin/sudo -s --preserve-env=SSH_AUTH_SOCK preserves $SSH_AUTH_SOCK but still requires password.

     

Log in to post a comment.