NAS-143402 / 27.0.0-BETA.1 / Stricter user SSH public key validation to match OpenSSH behavior (by themylogin) - #19726
Merged
Merged
Conversation
(cherry picked from commit a59f719)
Contributor
Author
themylogin
approved these changes
Sep 15, 2026
Contributor
Author
|
This PR has been merged and conversations have been locked. |
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
sshd opens the
authorized_keysfile as the user itself, so every directory leading to the home directory has tobe traversable by the account.
On top of that
StrictModesmakes sshd refuse to use the file when the home directory is world-writable or isowned neither by the user nor by root.
A public key that is stored under any of those conditions silently never authenticates anyone, so it should be rejected up front.
Original PR: #19652