if i wanted to make a tiny C server to run on *bsd, and have its network traffic go over an ssh connection, would it be better to make the server with libressl compiled in, or somehow route its traffic over existing ssh connections? (not sure how that'd work)
music.. why not just use stdin/stdout?
you can multiplex with existing connectinos, or create connections with keys
or if you receive connections, execute program and the program sees it nroaml
you can also do magic with pipes
which i tried once
so that you output to a pipe on one machine, that goes into pipe on the other
i was using it to start remote terminals etc, as proof of concept rather than really necessary
well i finally got word that truecrypt is dead
like official word?
mus1cb0x: The other standard approach, from what mercutio described, is to simply bind+listen to localhost, and for the ssh connection to use -L to setup a port forward. libressl (or OpenSSL, or BoringSSL) has nothing to do with ssh. In fact, even libssh2 (not related to everybody's favourite OpenSSH) wouldn't be much help since it's client-side only.
(eg: server# my_daemon, client$ ssh -L 1234:localhost:1234 server, and then localhost:1234 on the client routes over SSH to the server)
ty brycec and mercutio