Debian 13 – SSH Public Key Login Fails with StrictModes Errors – Permission Repair

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

SSH key authentication fails, forcing password fallback or full lockout.

Environment & Reproduction

Often occurs after home directory permission changes or user migration.

Root Cause Analysis

Insecure ownership or mode bits on home/.ssh/authorized_keys are rejected by sshd.

Quick Triage

Validate ownership and permissions on all key path components.

Step-by-Step Diagnosis

Correlate client verbose output with sshd journal entries.

Solution – Primary Fix

Apply correct ownership and file modes, then reload ssh service.

Solution – Alternative Approaches

Use centralized key management (e.g., AuthorizedKeysCommand) for large estates.

Verification & Acceptance Criteria

Key-based login succeeds without prompting for password.

Rollback Plan

Restore previous key files from backup if accidental overwrite occurred.

Prevention & Hardening

Enforce SSH file permissions through baseline compliance checks.

Related Errors & Cross-Refs

Authentication refused: bad ownership or modes for directory/file.

Related tutorial: View the step-by-step tutorial for Debian 13.

View all Debian 13 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

OpenSSH server hardening and Debian SSH administration docs.