PowerShell / PowerShell/Win32-OpenSSH

Impersonating new binaries spawned by SSHD

Open
#1,827 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
8.3k
Forks
819
PR merge metrics
No merged PRs in 30d

Description

Troubleshooting steps
https://github.com/PowerShell/Win32-OpenSSH/wiki/Troubleshooting-Steps

Terminal issue? please go through wiki
https://github.com/PowerShell/Win32-OpenSSH/wiki/TTY-PTY-support-in-Windows-OpenSSH

Please answer the following

"OpenSSH for Windows" version
((Get-Item (Get-Command sshd).Source).VersionInfo.FileVersion)
8.6.0.0

Server OperatingSystem
((Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows nt\CurrentVersion\" -Name ProductName).ProductName)
Windows Server 2016 Datacenter

Client OperatingSystem
Linux Redhat

What is failing
Try to spawn a utility from Linux on Windows Server. The utility spawned has below security principals and groups. This utility is not able to create folders under C:\Program Files<product_name> folder due to Access Denied.

Expected output
From local windows sever it works fine. Therefore utility should work fine when spawned from Linux Client. Utility is part of DevOps.

Actual output
Access Denied

Is there any way, we can specify under which user account new utility should be spawned so it has all the rights.

SSHD_Daemon

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked Troubleshooting Steps and TTY/PTY support wiki pages, then review the reported OpenSSH for Windows version and the SSHD_Daemon security-principal details. No source file, test, or entry point is identified; done would require determining whether SSHD supports spawning the utility under a different account or documenting the supported limitation.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux
Domain
operating-systems, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.