On 2019-10-15 20:37, Jeremy Lin wrote: > On Tue, Oct 15, 2019 at 4:02 PM Demi M. Obenour <demiobenour@xxxxxxxxx> wrote: >> >> [...snip...] Essentially, this tool would be an “SSH >> subsystem” ― it would provide all of the forwarding features of >> sshd(8), but without encryption or authentication. This is similar >> to how sftp-server(8) expects an already secure and authenticated >> connection. > > You might want to investigate HPN-SSH (https://www.psc.edu/hpn-ssh), > which among other things, is supposed to support disabling encryption > and authentication, though this support isn't enabled by default. > That is amazing, thanks! I would love to see their networking patches upstreamed. As far as disabling the crypto, it would be nice if the insecure version built separate binaries. mux-client(1) and mux-server(1) anyone? Would building such binaries from the same source tree be acceptable to the OpenSSH maintainers? Sincerely, Demi
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ openssh-unix-dev mailing list openssh-unix-dev@xxxxxxxxxxx https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev
