PowerShell / PowerShell/Win32-OpenSSH

I need one log file for each chrooted user to be created under ...\logs folder

Open
#1,957 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
8.3k
Forks
819
PR merge metrics
No merged PRs in 30d

Description

Hi all,

I am pretty new to Openssh/Sftp and I am managing to replicate the behaviour of a very old product (Platinum FTP), once installed on a 2K3 server.
When it comes to logging user activity, I've been able to only make it create the <ftp-server.log>, where the activity from all users is logged. I need to have a single logfile for each user. How could I possibly have that?

This is my current <sshd_config> settings

Logging

SyslogFacility LOCAL0
LogLevel Debug3

Match User xxxxxxxxxxx
ChrootDirectory D:\SFTP\xxxxxxxxxxx
AllowTcpForwarding no
X11Forwarding no
ForceCommand sftp-server.exe -l INFO -f LOCAL0

Thanks!


Troubleshooting steps
https://github.com/PowerShell/Win32-OpenSSH/wiki/Troubleshooting-Steps

Please answer the following

"OpenSSH for Windows" version
8.6.0.0

Server OperatingSystem
Windows Server 2019 Standard

Client OperatingSystem
Any
What is failing
One log file for each chrooted user is not created in Logs folder
Expected output

Actual output

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

Start with the sshd_config settings and the ForceCommand sftp-server.exe invocation shown in the issue, then review how Win32-OpenSSH handles SFTP logging and chrooted users on Windows. Determine whether per-user log files under each user's logs folder are supported and identify the relevant configuration or implementation entry point. Done means the behavior is documented or implemented and verified with separate user activity logs.

Written by the indexing model from the issue text.

Assessment

Domain
networking, operating-systems
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 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.