Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow setting destination constraints for each ssh key #9801

Open
mat813 opened this issue Aug 28, 2023 · 1 comment · May be fixed by #10252
Open

Allow setting destination constraints for each ssh key #9801

mat813 opened this issue Aug 28, 2023 · 1 comment · May be fixed by #10252

Comments

@mat813
Copy link

mat813 commented Aug 28, 2023

Summary

OpenSSH 8.9 includes the ability to control how and where keys in ssh-agent may be used, both locally and when forwarded (subject to some limitations).

Examples

From https://www.openssh.com/agent-restrict.html:

These extensions allow the user to add destination constraints to keys they add to a ssh-agent and have ssh enforce them. For example, this command:

$ ssh-add -h "perseus@cetus.example.org" \
          -h "scylla.example.org" \
          -h "scylla.example.org>medea@charybdis.example.org" \
          ~/.ssh/id_ed25519

Adds a key that can only be used for authentication in the following circumstances:

  • From the origin host to cetus.example.org as user perseus.
  • From the origin host to scylla.example.org as any user.
  • Through scylla.example.org to host charybdis.example.org as user medea.

It would be great if the "SSH Agent" panel in an entry had the possibility to add a list of restrictions

Context

This would allow me to forward my agent to more hosts than the restricted "safe" set that I currently have, while keeping my keys in KeePassXC.

@kgraefe
Copy link
Contributor

kgraefe commented Sep 22, 2023

see also #1721 and dlech/KeeAgent#296

@kgraefe kgraefe linked a pull request Feb 1, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants