tyler.durden/Win32-OpenSSH
1
0
Fork 0
mirror of https://github.com/PowerShell/Win32-OpenSSH.git synced 2025-07-26 07:25:25 +02:00
Code Issues Packages Projects Releases Wiki Activity

Updated Project Status (markdown)

Manoj Ampalam 2016-11-15 10:30:35 -08:00
parent 730226b164
commit d06fa3a878
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Project-Status.md

@ -8,8 +8,8 @@ Refer to project scope [here](https://github.com/PowerShell/Win32-OpenSSH/wiki/P
- Secure ssh-agent: A different version of agent is authored for Windows to fit Windows security model and enable a Single Sign-On experience.
- VT100/ANSI TTY and PTY: Rewritten client side ANSI parser to accurately interpret and render VT100 stream on Windows console. Server side VT100 PTY that will support rich Windows console applications. Due to missing dependencies on Nano, this feature is only supported on full SKUs.
- Unicode support in Windows: Windows APIs are typically UTF-16 based while on Unix, its UTF-8. All ssh binaries willon Windows can now take in Unicode arguments, support Unicode (UTF-8 or UTF-16) based configuration, key and log files, accurately encode file names going over SCP and SFTP.
- POSIX File API support in Windows: SFTP and SCP code is cleaned up to effectively use original OpenSSH code on Windows.
- Syncing Win32 fork with the latest changes from OpenSSH main repo. All changes from OpenSSH 7.3 (latest stable source) are integrated in Win32 fork.
- POSIX File API support in Windows: SFTP and SCP code is cleaned up to effectively use original OpenSSH code on Windows.
- Syncing Win32 fork with the latest changes from OpenSSH main repo. All changes from OpenSSH 7.3 (latest stable source) are integrated in Win32 fork.
#### Work in progress
- Code cleanup and refactoring: In entire project specific logic has been ifdef'ed and spread out at various places in the project in an attempt to achieve a workable solution on Windows. These need to be cleaned up and refactored as per OpenBSD's coding guidelines in order to get to an acceptable state. Tracked [here] (https://github.com/PowerShell/Win32-OpenSSH/issues?q=is%3Aopen+is%3Aissue+label%3A%22Area-Code+Cleanup%22).