PowerShell / PowerShell/Win32-OpenSSH
After logging in as a standard user on Windows 2012, there is no shell.
Open
Nobody has claimed this yet.
Investigate
- Dominant language
- No language data
- Stars
- 8.3k
- Forks
- 819
- PR merge metrics
- No merged PRs in 30d
Description
Prerequisites
- Write a descriptive title.
- Make sure you are able to repro it on the latest version
- Search the existing issues.
Steps to reproduce
sshd_config
PubkeyAuthentication yes
AuthorizedKeysFile .ssh/authorized_keys
PasswordAuthentication no
Subsystem sftp sftp-server.exe
AllowGroups administrators bisync
Using ssh -vvv, refer to the image for information with and without shell.
bisync
administrators
Expected behavior
shell
Actual behavior
no shell
Error details
Environment data
Name Value
---- -----
PSVersion 5.1.14409.2001
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.14409.2001
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
Version
v9.8.3.0p2-Preview
Visuals
No response
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
Reproduce the issue on Windows 2012 using the provided sshd_config and v9.8.3.0p2-Preview, then compare the ssh -vvv output for the bisync and administrators groups. Trace the differing login behavior and verify that a standard bisync user receives an interactive shell while retaining the shown group restrictions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- authentication, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100