PowerShell / PowerShell/Win32-OpenSSH

Inquiry Regarding Automatic Log Folder Permission Handling in OpenSSH v9.4 and Later

Open
#2,345 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Issue-Question
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

We are currently using OpenSSH version 9.4.0.0p1 and later on Windows Server 2019/2022 systems.

Recently, we encountered issues related to log folder permissions (C:\ProgramData\ssh\logs) following Windows security updates. We have come across unofficial information stating that, starting from OpenSSH v9.4, permissions for the log folder are applied automatically to prevent service crashes.

Could you please confirm whether this is accurate? Additionally, is this behavior officially documented in any release notes or Microsoft documentation?

Thank you in advance for your support.

Best regards,

Expected behavior
OpenSSH service should be able to start without manual permission adjustments on recent versions.
Actual behavior
Behavior seems stable in 9.4, but the lack of official documentation makes validation difficult.
Error details
-
Environment data
- OpenSSH version: 9.4.0.0p1
- OS: Windows Server 2019 / 2022
- Install method: Built-in or manually installed from GitHub releases
Version

9.4.0.0p1

Visuals

No response

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

The issue names no source file or test. Start by verifying OpenSSH 9.4 and later Windows log-folder permission handling against the release notes and Microsoft documentation. Done means the behavior is confirmed and the relevant official documentation is identified or added.

Written by the indexing model from the issue text.

Assessment

Domain
documentation, operating-systems
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.