Skip to content

keychain 2.9.5: Ignoring SSH_AUTH_SOCK -- this is a forwarded socket #181

@danielrobbins

Description

@danielrobbins

In testing keychain, we sometimes get incorrect forwarded socket debug messages:

 * keychain ##VERSION## ~ https://www.funtoo.org/Funtoo:Keychain
 * Warning: Keychain dir has lax permissions. Use chmod -R go-rwx '/home/drobbins/.keychain' to fix.
 debug> SSH_AGENT_PID in quick is invalid; ignoring it
 debug> Ignoring SSH_AUTH_SOCK -- this is a forwarded socket
 debug> SSH_AGENT_PID in quick is invalid; ignoring it
 debug> Ignoring SSH_AUTH_SOCK -- this is a forwarded socket
 * Note: Quick start unsuccessful -- no agent found...
 debug> SSH_AGENT_PID in pidfile is invalid; ignoring it
 debug> Ignoring SSH_AUTH_SOCK -- this is a forwarded socket
 * Starting ssh-agent...
 * Adding 2 ssh key(s): /home/drobbins/.ssh/id_ed25519 /home/drobbins/.ssh/id_rsa
Enter passphrase for /home/drobbins/.ssh/id_rsa:
 * ssh-add: Identities added: /home/drobbins/.ssh/id_ed25519
/home/drobbins/.ssh/id_rsa

Calling command:
eval $( ~/development/keychain/keychain.sh --extended --quick --eval sshk:id_rsa sshk:id_ed25519 --debug)

Just because a socket is invalid doesn't mean it is forwarded.

Note that I had a line in my ~/.bash_profile which I unfortunately commented out:

#echo previous SSH_AUTH_SOCK was $SSH_AUTH_SOCK

This would make a good debug statement, because afterwards we can then investigate the path and see if it exists and where it came from.

A bit more troubleshooting/reproduction is needed here.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions