Releases: PowerShell/Win32-OpenSSH
v0.0.10.0
This is a pre-release (non-production ready)
Includes:
- Fix to remote commadline issue introduced in 0.0.9.0
- Various terminal related issues
Wiki added to help understand TTY/PTY implementation in Windows
List of closed issues here
v0.0.9.0
v0.0.8.0
v0.0.7.0
v0.0.6.0
_This is a pre-release (non-production ready)_
Includes fixes to regression in v0.0.5.0 and minor issues in scp and sftp.
v0.0.5.0
_This is a pre-release (non-production ready)_
Regression Alert - installation will be broken if installed in "Program Files"
This release integrates all the latest changes in OpenSSH-Portable master into Win32 port. As detailed in Project Status, all development is being done in https://github.com/PowerShell/openssh-portable. For any contributions, please submit pull requests to PowerShell/openssh-portable.
This release also includes general fixes to reliability issues in scp and sftp scenarios. Wild cards now work in sftp as well as Windows styled paths.
Note: Log files are now populated in a "logs" folder in bin root.
See other improvements here
v0.0.4.0
_This is a pre-release (non-production ready)_
This release integrates all the latest changes in OpenSSH-Portable V7.3 into Win32 port. As detailed in Project Status, all development is being done in https://github.com/PowerShell/openssh-portable. For any contributions, please submit pull requests to PowerShell/openssh-portable.
See other improvements here
v0.0.3.0
_This is a pre-release (non-production ready)_
This release adds Unicode support in interactive shell, scp and sftp.
- Interactive TTY ssh session now accurately transmits and renders Unicode characters (cmd.exe code page may need to be changed for the appropriate locale)
- sftp and scp now supports Unicode directories and file names.
See other improvements here
v0.0.2.0
_This is a pre-release (non-production ready)_
This release adds Unicode support improvements in Windows. The problem with Unicode differences between Unix (UTF-8) and Windows (UTF-16) is tackled by:
- Defining a Unicode entry point for each executable. The entry point (wmain) is implemented in a common Windows compat library. This takes in UTF-16 arguments/parameters and converts them to UTF-8 before feeding them to OpenSSH original code.
- Making all POSIX structures calls in our wrapper UTF-8 compliant, overriding Unicode differing clals (like fopen) with UTF-8 compliant ones.
The changes
- Kept the internals of OpenSSH code intact (UTF-8 based) including original "main" routines.
- Got rid of Windows specific UTF-16 based code around configuration and user profile structures.
With these changes, following are supported:
- Addressing Unicode targets
- Generating and consuming Unicode configuration and key files (UTF-8 files on Windows can include BOM)
- Using Unicode directories and file paths and user names
- Unicode console prompts and input
TBD:
- SFTP and SCP are not Unicode ported yet. This is current work in progress.
This release also includes the following fixes:
- removed previous restrictions on scp and sftp around running them from their root directory.
- support on Nano. Nano does not support server side PTY changes. A remote session to Nano can be opened without a TTY/PTY as follows:
- ssh user@nano cmd
- ssh user@nano powershell -File -
- relative sub-system paths. Relative Sub-system executables can now be picked up from installation root. Ex the following in sshd_config would work for sftp:
- SFTP sftp-server.exe //sftp-server.exe will be picked up from sshd.exe installation path
v0.0.1.0
_This is a pre-release (non-production ready)_
This release improves on the terminal experience by including a rewritten ANSI client side parser and an ANSI compliant server side PTY for Windows console applications. Direction keys, Tab (auto completion) and Ctrl+C should now be enabled. This means that many server side console applications will now work seamlessly over remote ssh sessions. Powershell has so far been launched as "Powershell -File -". These std io redirecting arguments are no longer required. You may launch Powershell.exe directly and should see its rich native experience.
When talking to an Unix target from Windows 10, use "Legacy Mode" in console to work around "vi" and "top" issues.
NOTE: The server side changes do not work on Nano yet.
See features/improvements here