4 ms·
IRC in 307 rules of C code without dependencies, pretty cool. Of course for that to work they had to sacrifice secure TLS support. Based on the "do one thing we
by tmsbrg 6y ago
IRC in 307 rules of C code without dependencies, pretty cool. Of course for that to work they had to sacrifice secure TLS support. Based on the "do one thing well" I was thinking you could set up a TLS tunnel from localhost:6667 to <irc-server>:6697
Not really perfect but my WIP attempt using `socat`:
`socat -v tcp-listen:6667,reuseaddr,fork,bind=127.0.0.1 ssl:<irc-server>:6697`
then connect to it:
`./kirc -s 127.0.0.1 -c 'channel' -n 'name' -r 'realname'`
not sure what TLS version socat uses by default, might be something horrible :)
- mcpcpc 6y agooohh interesting. will throw this in as an “example”. thanks!
- anthk 6y agoThanks, this will work for SIC too.
- vaccinator 6y agoAny chance you know how to do encrypted dcc sends too?
- visualphoenix 6y agoFWIW I’ve had great success using ghostunnel[0] instead of stunnel in prod. Big fan. [0] https://github.com/ghostunnel/ghostunnel https://github.com/ghostunnel/ghostunnel
- 1vuio0pswjnm7 6y agoWhat was the need for an stunnel "replacement"? Looks like it has additional access controls and was written for use at Square, Inc. stunnel supports TLS1.3; from the client side IME it works really well ghostunnel appears to have a large number of dependencies on Go libraries written by a variety of third party authors stunnel is a long-running project dating from 1998, managed by the same single author over the entire period