PowerShell / PowerShell/Win32-OpenSSH
Different result from ssh and powershell
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 8.3k
- Forks
- 819
- PR merge metrics
- No merged PRs in 30d
Description
"OpenSSH for Windows" version
OpenSSH_for_Windows_7.9p1, LibreSSL 2.6.5
Server OperatingSystem
Windows Server 2012 R2 Datacenter
Client OperatingSystem
Fedora 29 / Windows Server 2012 R2 Datacenter
What is failing
cmdlets Get-Hotfix
Expected output
Source Description HotFixID InstalledBy InstalledOn
SVRTMP Security Update KB3004365 NT AUTHORITY\SYSTEM
SVRTMP Hotfix KB3004545 NT AUTHORITY\SYSTEM
SVRTMP Update KB3012235 NT AUTHORITY\SYSTEM
SVRTMP Update KB3012702 NT AUTHORITY\SYSTEM
Actual output
get-hotfix : Access denied
At line:1 char:1
- get-hotfix
-
+ CategoryInfo : NotSpecified: (:) [Get-HotFix], ManagementExcept ion + FullyQualifiedErrorId : System.Management.ManagementException,Microsoft. PowerShell.Commands.GetHotFixCommand
The user is a domain user with standard user rigths (only remote desktop capability).
If i send the cmdlet from powershell connected in RDP it works without problem, when launched in ssh it respond with Access Denied.
It works in SSH only if the user was added to Local Administrators group on the remote machine (SVRTMP).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository files or tests are named. Start by reproducing Get-HotFix over SSH and over RDP with the same standard domain user, then compare the session permissions and error details; done means the access-denied discrepancy is explained and covered by an appropriate repository change or test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- authorization, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100