Manoj Ampalam

Issue: While UPN based user names passed on ssh commandline (ssh user@domain@target) work in the general case, they do not work when passed in via URIs [(scp|ssh|sftp)://[user@]host[:port][/path]]. Root cause is...

Normalize incoming user before processing username relying logic

1

Issue: SSHD processes user based security rules (like AllowUsers, DenyUsers, Match blocks defined in sshd_config) based on incoming user name. User names when qualified with a domain can be given...

POSIX headers need to use #pragma once consistently to avoid name clashes, since a handful of these headers share the same as those in VS CRT.

This is to ensure that Win32 code gets accurately processed through VS static analysis.

Add a test case for https://github.com/PowerShell/Win32-OpenSSH/issues/658 Changes needed- - Add generate.pl and check.pl to repo - Install Perl as part of Install-TestDependencies - Add following test cases - E:\temp\perl\generate.pl |...

Tracked TODO in code: openssh-portable\loginrec.c(533): /* TODO - implement last_login_entry in Windows*/

A fundamental issue exists on the Unicode data transition boundary, when the data travels as a stream. This may manifest as ssh remote sessions breaking down with rare and random...

As reported in https://github.com/PowerShell/openssh-portable/pull/252

In Unix, shell access to a specific user can be disabled at the OS level Ex. https://unix.stackexchange.com/questions/55106/disable-user-shell-for-security-reasons We need similar functionality for Windows to support the relevant security scenarios.