[03:11] *** up_the_irons has quit IRC (Ping timeout: 272 seconds) [03:13] *** up_the_irons has joined #arpnetworks [03:13] *** ChanServ sets mode: +o up_the_irons [04:05] *** Guest9057 has quit IRC (Read error: Connection reset by peer) [04:06] *** Guest9057 has joined #arpnetworks [04:06] *** gizmoguy has quit IRC (Ping timeout: 240 seconds) [04:06] *** gizmoguy has joined #arpnetworks [08:23] *** acf_ has quit IRC (Ping timeout: 240 seconds) [09:23] *** CaZe has quit IRC (Ping timeout: 245 seconds) [09:24] *** mnathani has quit IRC (Ping timeout: 245 seconds) [09:25] *** CaZe has joined #arpnetworks [09:26] *** mnathani has joined #arpnetworks [13:27] 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) [13:35] *** acf_ has joined #arpnetworks [13:36] *** acf_ has quit IRC (Client Quit) [13:36] *** acf_ has joined #arpnetworks [13:37] *** acf_ has quit IRC (Client Quit) [13:37] *** acf_ has joined #arpnetworks [13:38] *** acf_ has quit IRC (Client Quit) [13:38] *** acf_ has joined #arpnetworks [14:43] music.. why not just use stdin/stdout? [14:43] you can multiplex with existing connectinos, or create connections with keys [14:43] or if you receive connections, execute program and the program sees it nroaml [14:45] you can also do magic with pipes [14:46] which i tried once [14:46] so that you output to a pipe on one machine, that goes into pipe on the other [14:47] i was using it to start remote terminals etc, as proof of concept rather than really necessary [14:49] *** novae has quit IRC (Ping timeout: 264 seconds) [15:40] well i finally got word that truecrypt is dead [16:10] like official word? [17:54] 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. [17:55] (eg: server# my_daemon, client$ ssh -L 1234:localhost:1234 server, and then localhost:1234 on the client routes over SSH to the server) [18:59] *** hazardous has quit IRC (Ping timeout: 240 seconds) [19:04] *** hazardous has joined #arpnetworks [19:43] *** novae has joined #arpnetworks [21:55] ty brycec and mercutio