From 8e17b527a9375ec28b5e04a46331e425e1d9fc1c Mon Sep 17 00:00:00 2001 From: Manoj Ampalam Date: Thu, 25 May 2017 13:51:01 -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, 1 insertion(+), 1 deletion(-) diff --git a/Security-protection-of-various-files-in-Win32-OpenSSH.md b/Security-protection-of-various-files-in-Win32-OpenSSH.md index ab46dab..c85c359 100644 --- a/Security-protection-of-various-files-in-Win32-OpenSSH.md +++ b/Security-protection-of-various-files-in-Win32-OpenSSH.md @@ -1,7 +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. 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. +- 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.