sites

commit 2fcbe64b5d3dcd121eacc209b79659e90b3263c4
parent 5543405891615c031bafd22be39f73c67d2dfeb9
Author: Josuah Demangeon <mail@josuah.net>
Date:   Mon, 12 Feb 2018 01:02:25 +0100

for inetd solution, use unix socket rather than a tcp socket

Diffstat:
M
tools.suckless.org/ii/usage.md
 | 
10
+++-------

1 file changed, 3 insertions(+), 7 deletions(-)
diff --git a/tools.suckless.org/ii/usage.md b/tools.suckless.org/ii/usage.md
@@ -72,14 +72,10 @@ In `/etc/stunnel/stunnel.conf`:
 [inetd](http://man.openbsd.org/inetd) listens on multiple TCP ports and can connect a program standard input and output to a TCP socket.
 This enables it to act as a simple proxy using any command line TLS client, such as [openssl s_client](http://man.openbsd.org/openssl#S_CLIENT), [brssl client](https://bearssl.org/gitweb/?p=BearSSL;a=blob;f=tools/brssl.c;h=91372b09f42149a503f9d13db0b78cf0a123611e;hb=HEAD#l43), nc -ssl, socat... or any other:
 
-In `/etc/services`:
-
-	irc-oftc	<your port>/tcp
-
 In `/etc/inetd.conf`:
 
-	irc-oftc	stream	tcp	nowait	nobody	/usr/bin/openssl	openssl s_client -quiet -connect irc.oftc.net:6697
+	/tmp/irc.oftc.net	stream	unix	nowait	nobody	/usr/bin/openssl	openssl s_client -quiet -connect irc.oftc.net:6697
 
-Then a proxy should be available at localhost:<your port> for ii to connect to:
+Then a proxy should be available as an unix socket for ii to connect to:
 
-	ii -s 127.0.0.1 -p <your port>
+	ii -s irc.oftc.net -u /tmp/irc.oftc.net