You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Make sure you are able to repro it on the latest version
Search the existing issues.
Steps to reproduce
After KB5044281 update, we cannot see username in eventlog for SFTP uploads or any other commands. Before update, real username was listed in USER field. Now there is only SYSTEM as a user for all operations. SFTP Server is configured as chrooted (users cannot move away from their home directories).
The big guestion is, is this a new feature, or will it be fixed? Solving integration (sftp) related problems is almost impossible, without knowing which user is doing what.
Expected behavior
Logging (to eventlog, which is the recommended way) should include username, who did the operation (upload, download rename etc).
Actual behavior
In eventlog entries all operation are made by User: SYSTEM
Prerequisites
Steps to reproduce
After KB5044281 update, we cannot see username in eventlog for SFTP uploads or any other commands. Before update, real username was listed in USER field. Now there is only SYSTEM as a user for all operations. SFTP Server is configured as chrooted (users cannot move away from their home directories).
The big guestion is, is this a new feature, or will it be fixed? Solving integration (sftp) related problems is almost impossible, without knowing which user is doing what.
Expected behavior
Logging (to eventlog, which is the recommended way) should include username, who did the operation (upload, download rename etc).
Actual behavior
In eventlog entries all operation are made by User: SYSTEM
Error details
No response
Environment data
Version
PS C:\Windows\system32> ssh -V OpenSSH_for_Windows_9.5p1, LibreSSL 3.8.2
Visuals
No response
The text was updated successfully, but these errors were encountered: