I maintain my own OpenSSH distribution and wonder if ssh-rs could be more than a library, and also include a drop-in replacement for the OpenSSH client ("ssh" executable) supporting the original command-line interface. This could become very useful in specific scenarios like PowerShell Remoting over SSH where the OpenSSH client CLI is expected.
usage: ssh [-46AaCfGgKkMNnqsTtVvXxYy] [-B bind_interface]
[-b bind_address] [-c cipher_spec] [-D [bind_address:]port]
[-E log_file] [-e escape_char] [-F configfile] [-I pkcs11]
[-i identity_file] [-J [user@]host[:port]] [-L address]
[-l login_name] [-m mac_spec] [-O ctl_cmd] [-o option] [-p port]
[-Q query_option] [-R address] [-S ctl_path] [-W host:port]
[-w local_tun[:remote_tun]] destination [command]
There are a lot of options in the command-line interface, but this would also require parsing the same configuration files, etc. However, by making an OpenSSH compatibility layer over ssh-rs, it would make it much easier to try without tweaking and building the current samples.
I maintain my own OpenSSH distribution and wonder if ssh-rs could be more than a library, and also include a drop-in replacement for the OpenSSH client ("ssh" executable) supporting the original command-line interface. This could become very useful in specific scenarios like PowerShell Remoting over SSH where the OpenSSH client CLI is expected.
There are a lot of options in the command-line interface, but this would also require parsing the same configuration files, etc. However, by making an OpenSSH compatibility layer over ssh-rs, it would make it much easier to try without tweaking and building the current samples.