@@ -92,10 +92,10 @@ There is no native TLS/SSL support. Instead, users can achieve this functionalit
92
92
93
93
* [ socat] ( https://linux.die.net/man/1/socat ) example (remember to replace items enclosed with ` <> ` ):
94
94
95
- ``` shell
96
- socat tcp-listen:6667,reuseaddr,fork,bind=127.0.0.1 ssl:< irc-server> :6697
97
- kirc -s 127.0.0.1 -c ' channel' -n ' name' -r ' realname'
98
- ```
95
+ ``` shell
96
+ socat tcp-listen:6667,reuseaddr,fork,bind=127.0.0.1 ssl:< irc-server> :6697
97
+ kirc -s 127.0.0.1 -c ' channel' -n ' name' -r ' realname'
98
+ ```
99
99
100
100
# # SASL PLAIN Authentication
101
101
@@ -119,11 +119,11 @@ Similar to `SASL PLAIN`, the `SASL EXTERNAL` mechanism allows us to authenticate
119
119
120
120
* [socat](https://linux.die.net/man/1/socat) example (remember to replace items enclosed with ` <> ` ):
121
121
122
- ``` shell
123
- socat TCP4-LISTEN:1110,fork,bind=0,reuseaddr SOCKS4A:127.0.0.1:< onion_address.onion> :< onion_port> ,socksport=9050
124
- socat TCP4-LISTEN:1111,fork,bind=0,reuseaddr ' OPENSSL:127.0.0.1:1110,verify=0,cert=<path_to_pem>'
125
- kirc -e -s 127.0.0.1 -p 1111 -n < nick> -x ' wait 5000'
126
- ```
122
+ ` ` ` shell
123
+ socat TCP4-LISTEN:1110,fork,bind=0,reuseaddr SOCKS4A:127.0.0.1:< onion_address.onion> :< onion_port> ,socksport=9050
124
+ socat TCP4-LISTEN:1111,fork,bind=0,reuseaddr ' OPENSSL:127.0.0.1:1110,verify=0,cert=<path_to_pem>'
125
+ kirc -e -s 127.0.0.1 -p 1111 -n < nick> -x ' wait 5000'
126
+ ` ` `
127
127
128
128
# # Contact
129
129
0 commit comments