From dd255fc4f65053900cf25ccaff4d26f82a6d6117 Mon Sep 17 00:00:00 2001 From: Yanbing Date: Thu, 11 May 2017 11:37:02 -0700 Subject: [PATCH] Updated Troubleshooting Steps (markdown) --- Troubleshooting-Steps.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/Troubleshooting-Steps.md b/Troubleshooting-Steps.md index e8c15bf..d431b11 100644 --- a/Troubleshooting-Steps.md +++ b/Troubleshooting-Steps.md @@ -1,6 +1,10 @@ If sshd cannot start * Check that sshd_config is in place - * Check that host keys are generated + * Check that host keys are generated and have correct file permission: + * Check if private host keys are protected: + * The file owner of private host key files cannot be other accounts than current user, Administrators group, Local system account, or an user account in local Administrators group + * Other accounts than current user, Administrators group, Local system account, or an user account in local Administrators group should not have any access to private key file + * Check if "NT service\sshd" have read access to public key files Trouble shooting steps for typical connection issues: - Server side - run sshd in debug mode