Skip to content

Conversation

mkj
Copy link
Contributor

@mkj mkj commented Nov 21, 2024

In c1206e1 ("ssh-tpm-agent: use SSH_AUTH_SOCK") ssh-tpm-agent started using SSH_AUTH_SOCK as the default path. That is problematic because it will overwrite the existing socket, so -A won't work any more. Instead use a distinct environment variable passed from the .service file.

In c1206e1 ("ssh-tpm-agent: use SSH_AUTH_SOCK")
ssh-tpm-agent started using SSH_AUTH_SOCK as the default path. That is
problematic because it will overwrite the existing socket, so -A won't
work any more. Instead use a distinct environment variable passed from
the .service file.

Signed-off-by: Matt Johnston <matt@ucc.asn.au>
@Foxboron
Copy link
Owner

Right, I thought it would be a good idea to reuse the ssh-agent auth socket paths as it would enable ssh-tpm-agent to just be a drop-in to the existing ssh-agent. As it works as a proxy as well that seems like a reasonable solution.

I need to think a little bit if I'm happy just accepting a new environment or if there is a compromise to be made here.

@Foxboron Foxboron merged commit dd3f5f4 into Foxboron:master Nov 27, 2024
@Foxboron
Copy link
Owner

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants