From c19c8f9e1c879ed8193307f7cd43ef31be3f1b9f Mon Sep 17 00:00:00 2001 From: Manoj Ampalam Date: Thu, 25 May 2017 11:35:11 -0700 Subject: [PATCH] Updated Security protection of various files in Win32 OpenSSH (markdown) --- Security-protection-of-various-files-in-Win32-OpenSSH.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Security-protection-of-various-files-in-Win32-OpenSSH.md b/Security-protection-of-various-files-in-Win32-OpenSSH.md index 37e07ae..7c09634 100644 --- a/Security-protection-of-various-files-in-Win32-OpenSSH.md +++ b/Security-protection-of-various-files-in-Win32-OpenSSH.md @@ -1,6 +1,6 @@ -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 tips on how to fix any permission related issues. +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 tips on individual case studies on how to fix any permission related issues. -The are 2 fundamental reasons leading to the differences between how these permission checks work on Unix vs Windows. +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.