PowerShell / PowerShell/Win32-OpenSSH

The description for Event ID 4 from source OpenSSH cannot be found

Open
#2,265 0 comments 0 reactions 1 assignee View on GitHub

@anmenaga is already working on this.

Since Aug 26, 2024.

Area-Install Issue-Bug
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
  1. Uninstall windows built-in openssh server and client
  2. winget install Microsoft.OpenSSH.Beta
  3. Start openssh server
  4. view openssh eventlog
Expected behavior
sshd
Connection closed by authenticating user user_name ip_address port port_number [preauth]
Actual behavior
The description for Event ID 4 from source OpenSSH cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

sshd
Connection closed by authenticating user user_name ip_address port port_number [preauth]
Error details

No response

Environment data
Name                           Value
----                           -----
PSVersion                      7.4.5
PSEdition                      Core
GitCommitId                    7.4.5
OS                             Microsoft Windows 10.0.20348
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0
Version

OpenSSH_for_Windows_9.5p1, LibreSSL 3.8.2

Visuals

Using built-in openssh server without the above issue, but it's too old.

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.