From 7e473046d8c77234db830b3ea34fee82e8be0b04 Mon Sep 17 00:00:00 2001 From: Manoj Ampalam Date: Mon, 14 Nov 2016 14:00:13 -0800 Subject: [PATCH] Updated About Win32 OpenSSH and Design Details (markdown) --- About-Win32-OpenSSH-and-Design-Details.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/About-Win32-OpenSSH-and-Design-Details.md b/About-Win32-OpenSSH-and-Design-Details.md index 8526861..6383da4 100644 --- a/About-Win32-OpenSSH-and-Design-Details.md +++ b/About-Win32-OpenSSH-and-Design-Details.md @@ -113,9 +113,12 @@ As detailed earlier, session isolation in Windows will be done using CreateProce End result of authentication in Windows is a Windows user token (if authentication succeeds). SSH sessions that need client user capabilities are hosted in processes running under the context of client user (launched using CreateProcess(user_token)). Ex. cmd.exe for terminal session, sftp_server.exe for sftp session and scp.exe for scp session. +Shown below is a high level overview of the various SSH components and access boundaries for various resources involved: ![HLA](https://cloud.githubusercontent.com/assets/14185020/20284248/367b1f76-aa71-11e6-9243-6034eae07ba8.JPG) + +