From 3dec39a487add7d07f8e3a8bbbe5757d40d5cb4e Mon Sep 17 00:00:00 2001 From: Manoj Ampalam Date: Fri, 2 Jun 2017 22:24:05 -0700 Subject: [PATCH] Updated Security protection of various files in Win32 OpenSSH (markdown) --- Security-protection-of-various-files-in-Win32-OpenSSH.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Security-protection-of-various-files-in-Win32-OpenSSH.md b/Security-protection-of-various-files-in-Win32-OpenSSH.md index c85c359..82713d4 100644 --- a/Security-protection-of-various-files-in-Win32-OpenSSH.md +++ b/Security-protection-of-various-files-in-Win32-OpenSSH.md @@ -1,5 +1,7 @@ Various OpenSSH resource files are integral to secure working of both server and client stacks. Here we discuss how to protect these resources, how OpenSSH for Windows enforces permission checks and individual case studies on how to fix any permission related issues. +Improper file permissions will likely result in a broken configuration (OpenSSH fails to work). [Utility scripts](https://github.com/PowerShell/Win32-OpenSSH/wiki/OpenSSH-utility-scripts-to-fix-file-permissions) included in release payload can help with fixing any permissions related issues. + 2 fundamental reasons leading to the differences between how these permission checks work on Unix vs Windows: - SuperUser on Unix maps to either [System (SY)](https://msdn.microsoft.com/en-us/library/windows/desktop/ms684190(v=vs.85).aspx) or AdministratorsGroup (AG) on Windows. - Permission controlling in Windows is more granular than in Unix.