Terminator not setting $SSH_AUTH_SOCK correctly
Bug #1623427 reported by
Jonas G. Drange
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Terminator |
Invalid
|
Undecided
|
Unassigned |
Bug Description
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_
DISTRIB_
DISTRIB_
Reproduce:
Open Terminator
Connect to a host which an agent will provide an ssh key for authentication.
What happens:
I'm asked to unlock key
What should happen:
There's an SSH agent running, I should connect and authenticate immediately.
Fix:
$ export SSH_AUTH_
Reason for this bug is that: before yakkety, this used to work just fine. And for gnome-terminal, this never broke. There are no special scripts in gnome-terminal.
To post a comment you must log in.
It is *not* the responsibility of Terminator to set SSH_AUTH_SOCK. This is something that gets configured in your bash startup scripts or is inherited from the environment.
You don't mention which version of Terminator you were using, but I just checked on my Xenial with the latest gtk3 code, and I'm seeing SSH_AUTH_SOCK passed to both gnome-terminal and terminator. If something is different in Yakkety then it is not terminator that has changed.