restart ssh after keys are updated #945
Merged
+2
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
marcoieni
force-pushed
the
restart-ssh-after-keys-are-updated
branch
from
62b7b40 to
4dcfce6
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If we don't run
sudo systemctl restart ssh, I can't ssh from my user.AI review
Standard behavior for
authorized_keysIn ansible/roles/common/tasks/ssh.yml:
Standard sshd behavior is to read the AuthorizedKeysFile path upon every connection attempt. It is highly unusual to require a service restart for updated keys to take effect.
While this might solve the symptom described, double-check if permissions or SELinux contexts on the /etc/ssh/authorized_keys/ directory are correct, as those are more
likely root causes for keys not being accepted immediately.
My response to AI review
Probably we should check what AI suggests, but I'm not doing this because from my test reloading ssh worked.