axw/pushy — Issue #18: implement Windows named pipe transport
Author: axw
Created: 2012-02-07 15:00:43+00:00
State: open
Labels: Fix Released, Medium

Pushy should be able to connect to remote Windows machines. This can be done at the moment by running an SSH daemon. Ideally, Pushy should not require anything non-standard on the Windows machine to be pre-existing.

Proposed solution is to implement a Windows service that runs a named-pipe server. The server will impersonate clients, and execute a command that is send to the named pipe, and then connect pipes to the standard I/O of the sub-process.

On the client (Pushy)-side, a connection to the named-pipe server will be made using Impacket, or some other Python SMB package. To support the "no pre-existing non-standard software" scenario, Pushy should support the ability to remotely create the service via the service control manager RPC interface.