sshconfig-lint
Include cannot be read
← All checksAn included file exists in the resolution path but cannot be read.
Why it matters
Permissions, encoding, or filesystem errors prevent the full configuration from being checked.
How to fix it
Expand ~ and inspect the exact path with ls -l. Correct a typo or move the Include to the real file; if the file exists, grant your user read access without making a private SSH configuration world-readable, then rerun the linter.
Before and after
Include ~/.ssh/conf.d/private.confInclude ~/.ssh/conf.d/work.conf