openssh-portable

> The Microsoft version of OpenSSH ships an SSH agent that doesn't use Unix sockets, but uses a named pipe instead. Looks like there is work on this at https://github.com/PowerShell/openssh-portable/pull/674 and eventually take advantage of https://devblogs.microsoft.com/commandline/af_unix-comes-to-...

PuTTY is fine of course, but just FYI to those who don’t realize it: Microsoft has worked for a while to port OpenSSH to Windows proper. I think they are even shipping it with Windows nowadays. https://github.com/PowerShell/openssh-portable

At the link below I believe. https://github.com/PowerShell/openssh-portable

just saw this pull req https://github.com/PowerShell/openssh-portable/pull/360

Even right now, you can install sshd and/or use the client by adding them as a feature, or by installing manually. https://github.com/PowerShell/Win32-OpenSSH and https://github.com/PowerShell/openssh-portable

> The service itself sometimes controls which user can access which data, Sure, but ssh-agent does not. That's what I was alluding to with "major surgery". Also, while the encrypted keys are stored in the file system or registry, the agent process necessarily has them in unencrypted form. That's the reason for loading keys into the agent in the first place. To have an ssh-agent that can run as a privileged system service with multiple unprivileged clients, you need to extend it to have some notion of client identity and per-user key space. The standard OpenSSH ssh-agent doesn't have that. Users run their own instance each and if you can connect to it, you can use the keys loaded into it. All of them. The agent code at github.com/PowerShell/openssh-portable doesn't look any different to me, at least from a cursory glance. Thus, the decisio

> I have no idea how the original author soleblaze figured out the correct format of the binary data, but I am so thankful he did and shared. Good time to point out that we open sourced [0] all of this so I have some guesses as to how soleblaze might have "reverse engineered" it :-) 0. https://github.com/PowerShell/openssh-portable

Hey there, everyone! I'm the PM for this project, and it looks like I'm a little late to the party, but I wanted to drop in some notes to add to the discussion: * we also shipped OpenSSH's sshd server, but it's a little tricky to configure right now. Expect a blog post this week. * This is not production-ready in the current version of Windows 10 (hence the "(Beta)" in the label), but we hope to be soon. * All of this is being done in open-source out of a fork at https://github.com/powershell/Win32-OpenSSH (code work is technically checked into https://github.com/powershell/openssh-portable/ first, but those will be consolidated at some point). Check the Wiki there for a ton of info. * We've been working closely with the official OpenSSH Portable maintainers to get upstream at some point in the future. They've been awesome to work with so

For reference, the work is done at https://github.com/PowerShell/openssh-portable even though the wiki, issues, etc happen there. I will say, from my limited experience w/ MS's fork, they take a bit of a hacky approach. For instance, I just wanted standalone sshd, but they really want you to run it as a service and install/uninstall with PowerShell scripts [0]. In general though, the open SSH fork seems to support pluggable shells and has decent pty support (it fires up a separate shellhost.exe process per client) 0 - https://github.com/PowerShell/Win32-OpenSSH/issues/909#issue...