4 ms·

I wonder how this compares with https://github.com/PowerShell/Win32-OpenSSH https://github.com/PowerShell/Win32-OpenSSH feature and stability-wise.

nailer 9y ago
Compared to OpenSSH for Windows: - They're both native Windows apps - no Cygwin etc. OpenSSH is C, Pyrexecd is Python. - OpenSSH has a service, Pyrexecd is a system tray app (despite the 'd' in the name) - OpenSSH launches the normal shell, Pyerexecd launches cmd - Pyrexecd shows popups for incoming connections, OpenSSH doesn't have this feature. - Pyrexecd is for single users. Honestly it's hard to compete with Microsoft's OpenSSH port (particularly if the plan to merge it into the mainline OpenSSH code happens). It's cool code though - Python on Windows doing SSH stuff is useful as a systems management tool outside of this.
kodablah 9y ago
For reference, the work is done at https://github.com/PowerShell/openssh-portable 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#issuecomment-335313384 https://github.com/PowerShell/Win32-OpenSSH/issues/909#issue...
- nailer 9y ago
  This is an interesting perspective. I run sshd on nix through sysvinit or systemd, running it as a Windows service seems expected rather than 'hacky'. If you just ran sshd as an executable it would still be attached to the controlling terminal on a nix box. Likewise sshd is typically deployed via a package manager that calls Bourne shell or bash, posh seems a reasonable equivalent. What would you use instead?
  - kodablah 9y ago
    It should work both ways. I have run sshd locally w/ an sshd_config and I would expect that I can run it standalone. My project was to do a self-contained ssh-over-tor setup. So I could have an sshd_config like so: Port 5678 HostKey /home/myuser/sometempdir/ssh_host_rsa_key HostKey /home/myuser/sometempdir/ssh_host_dsa_key HostKey /home/myuser/sometempdir/ssh_host_ecdsa_key HostKey /home/myuser/sometempdir/ssh_host_ed25519_key PidFile /home/myuser/sometempdir/sshd.pid UsePam yes And run this: /usr/sbin/sshd -f /home/myuser/sometempdir/sshd_config -E /home/myuser/sometempdir/sshd.log Whether I run this manually, as a service daemon on the part of the OS, etc should not affect the core piece. For my project, I even considered going as far as statically linking Open SSH and Tor, but never completed it.

nailer 9y ago

Compared to OpenSSH for Windows: - They're both native Windows apps - no Cygwin etc. OpenSSH is C, Pyrexecd is Python. - OpenSSH has a service, Pyrexecd is a system tray app (despite the 'd' in the name) - OpenSSH launches the normal shell, Pyerexecd launches cmd - Pyrexecd shows popups for incoming connections, OpenSSH doesn't have this feature. - Pyrexecd is for single users. Honestly it's hard to compete with Microsoft's OpenSSH port (particularly if the plan to merge it into the mainline OpenSSH code happens). It's cool code though - Python on Windows doing SSH stuff is useful as a systems management tool outside of this.

kodablah 9y ago

For reference, the work is done at https://github.com/PowerShell/openssh-portable 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#issuecomment-335313384 https://github.com/PowerShell/Win32-OpenSSH/issues/909#issue...

nailer 9y ago
This is an interesting perspective. I run sshd on nix through sysvinit or systemd, running it as a Windows service seems expected rather than 'hacky'. If you just ran sshd as an executable it would still be attached to the controlling terminal on a nix box. Likewise sshd is typically deployed via a package manager that calls Bourne shell or bash, posh seems a reasonable equivalent. What would you use instead?
- kodablah 9y ago
  It should work both ways. I have run sshd locally w/ an sshd_config and I would expect that I can run it standalone. My project was to do a self-contained ssh-over-tor setup. So I could have an sshd_config like so: Port 5678 HostKey /home/myuser/sometempdir/ssh_host_rsa_key HostKey /home/myuser/sometempdir/ssh_host_dsa_key HostKey /home/myuser/sometempdir/ssh_host_ecdsa_key HostKey /home/myuser/sometempdir/ssh_host_ed25519_key PidFile /home/myuser/sometempdir/sshd.pid UsePam yes And run this: /usr/sbin/sshd -f /home/myuser/sometempdir/sshd_config -E /home/myuser/sometempdir/sshd.log Whether I run this manually, as a service daemon on the part of the OS, etc should not affect the core piece. For my project, I even considered going as far as statically linking Open SSH and Tor, but never completed it.