Issue with opkssh setup on AWS EC2 #462
-
|
In AWS EC2 we already have a auth config file Way to reproduce:
Steps I used for the fix1. Remove EC2 drop-in that overrides the keys command2. Reload systemd to reflect the change3. Make sure ssh.service is directly enabled (not socket-activated)4. Restart the SSH server cleanly |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Yes, this is a known issue, but despite having copious notes on it, for some reason didn't have a github issue for it (1000 shames upon me). I've created a github issue at #465 to track it. SSHd only supports one authorized keys command so if authorized keys command is pointed to aws instance connect, opkssh can't use. Disabling aws instance connect as you have done is a reasonable fix by moving the If you want to use both aws instance connect and opkssh, you could create a script that calls opkssh and then calls aws instance connect. Would you be interested creating a PR to add this fix to the documentation? |
Beta Was this translation helpful? Give feedback.
For anyone who comes across this discussion, here is the documentation for solving this problem https://github.com/openpubkey/opkssh/blob/main/docs/aws-ec2.md
#467