+- nixers (https://nixers.net)
+-- Forum: General (https://nixers.net/Forum-General)
+--- Forum: Community & Forums Related Discussions (https://nixers.net/Forum-Community-Forums-Related-Discussions)
+--- Thread: IRC (/Thread-IRC--1876)
RE: IRC - josuah - 12-04-2017
(12-01-2017, 10:25 AM)z3bra Wrote: You can also use stunnel if you don't feel like patching.
It works great!
Code:
$ cat << EOF > config
[unix.chat]
accept = 127.0.0.1:6667
connect = unix.chat:6697
EOF
$ stunnel config
$ sic -h 127.0.0.1 -p 6667Et voià!
RE: IRC - robotchaos - 12-04-2017
what is the nick max character limit?
RE: IRC - pyratebeard - 12-04-2017
If I remember correctly it's 8
Edit- spelling
RE: IRC - robotchaos - 12-04-2017
damn it, off by 1
RE: IRC - fro - 17-04-2017
it's 9.
also i think i fixed apk's problem with drinking and irc.
RE: IRC - robotchaos - 18-04-2017
yeah, so looks like i will just stick with rchaos on the forums
RE: IRC - xcko - 14-06-2017
Looks like the unix.chat ssl cert has expired:
verify error:num=10:certificate has expired
notAfter=Jun 14 11:25:00 2017 GMT
RE: IRC - hubcaps - 06-09-2017
SSL cert appears to have expired again.
edit: actually seems to work on unix.chat by itself, the others list the cert fails to verify.
RE: IRC - xero - 07-09-2017
looks ok to me, for another week
https://www.sslshopper.com/ssl-checker.html#hostname=unix.chat
RE: IRC - hubcaps - 15-09-2017
unix.chat is now failing as well.
RE: IRC - perrierjouet - 15-10-2017
bonjour
Je ne peux me connecter a nixers, j'ai connection refused
RE: IRC - z3bra - 15-10-2017
C'est un forum anglophone, pour info :)
Ensure that you're connecting via SSL on port 6697. The service is not accessible without SSL.
RE: IRC - Nihility - 22-11-2017
who can invite me to irc, nick is jjan
RE: IRC - z3bra - 22-11-2017
(22-11-2017, 06:41 AM)Nihility Wrote: who can invite me to irc, nick is jjan
Hello jjan, do you want to join IRC channel #unix @unix.chat ?
RE: IRC - Nihility - 22-11-2017
@z3bra yes #unix, it says you need an invite or am i missing something out
RE: IRC - z3bra - 22-11-2017
Ah, I guess I'm just too old then. Back in my days this chan was begging people to join
Anyhow, tried to invite you but you're not connected, so..
RE: IRC - Nihility - 22-11-2017
i'm online now
i've been here since 2012 (unixhub days) but i'm just a lurker because my english is not that good
RE: IRC - budRich - 22-11-2017
>> *nix users needing invites to networks ;)
RE: IRC - fraun - 17-01-2018
Any idea why I'm banned? nick = fraun
RE: IRC - fraun - 06-02-2018
Hi again, any luck unbanning me?
RE: IRC - josuah - 09-02-2018
I had trouble for connecting with a client that does not handle TLS (like ii, sic, ...), and I found a solution! :)
I use an inetd stream entry which for piping the command-line TLS client* and a local TCP socket for your client to connect to. You can even have a Proxy machine which does the translation!
* openssl s_client, nc -ssl, brssl client... now you have the choice of your backend! :D Pipes are universal.
# vi /etc/services
Code:
irc-freenode 6970/tcp
irc-unix 6971/tcp
irc-other 6972/tcp
...# vi /etc/inetd.conf
Code:
irc-freenode stream tcp nowait nobody /usr/bin/openssl openssl s_client -quiet -connect irc.freenode.net:6697
irc-unix stream tcp nowait nobody /usr/bin/openssl openssl s_client -quiet -connect unix.chat:6697
irc-other stream tcp nowait nobody /usr/bin/openssl openssl s_client -quiet -connect irc.other.networks:6697
...And then start the inetd service, the inetd daemon... however you distro or you wants it... If it already runs, you can probably reload its configuration with:
# pkill -HUP inetd
You can pretty much use xinetd for this, the command itox translates the inetd format to xinetd format:
# itox < inetd.conf
Code:
service irc-unix
{
socket_type = stream
protocol = tcp
wait = no
user = nobody
server = /usr/bin/openssl
server_args = s_client -connect unix.chat:6697
}RE: IRC - z3bra - 10-02-2018
nice one Josuah! Taking the best from unix IPC ;)
RE: IRC - josuah - 11-02-2018
Thank you z3bra!
For the ii client, it is possible to use UNIX sockets instead of TCP sockets:
# vi /etc/inetd.conf
Code:
/tmp/irc.freenode.net stream unix nowait nobody /usr/bin/openssl openssl s_client -quiet -connect irc.freenode.net:6697
/tmp/unix.chat stream unix nowait nobody /usr/bin/openssl openssl s_client -quiet -connect unix.chat:6697
/tmp/other... stream unix nowait nobody /usr/bin/openssl openssl s_client -quiet -connect irc.other.networks:6697
...# ii -s unix.chat -u /tmp/unix.chat
And then you have ~/irc/unix.chat and not ~/irc/127.0.0.1. :)
RE: IRC - Dog - 01-03-2018
I have to turn off verification for this server to connect. I'm getting this in weechat:
Code:
│13:49:42 | unix.chat =!= | gnutls: the hostname in the certificate does NOT match "irc.unix.chat"
│13:49:42 | unix.chat -- | gnutls: peer's certificate is trusted
│13:49:42 | unix.chat =!= | irc: TLS handshake failed
│13:49:42 | unix.chat =!= | irc: error: Error in the certificate.For anyone that runs into this, you can turn off verification with:
Code:
/set irc.server.<identifier>.ssl_verify offRE: IRC - venam - 27-05-2020
There has been some changes in the IRC space. We now have an official IRC channel on freenode, #nixers_net (Yes, #nixers was taken).
Be sure to update your IRC clients to point to this new home of ours.
The nixers philosophy, rules, and mentality apply there. All in good faith, I hope you prefer this change.
RE: IRC - jkl - 27-05-2020
Is it because of the TLS issues?
RE: IRC - venam - 27-05-2020
(27-05-2020, 02:17 AM)jkl Wrote: Is it because of the TLS issues?
The previous IRC, not hosted by nixers, was supposed to be temporary until we could host its own, that lead to some unfortunate behavior that doesn't reflect the community. You're welcomed to join anytime.
RE: IRC - fro - 27-05-2020
Why freenode instead of efnet? #nixers is not taken there.
I think the change is a solid idea btw.
RE: IRC - venam - 27-05-2020
(27-05-2020, 02:37 AM)fro Wrote: Why freenode instead of efnet? #nixers is not taken there.
No particular reason other than that I forgot about efnet. In all honesty, I'm not sure it really matters where we host it or whether we're using #nixers_net instead of #nixers, as long as people can find us there should be no issue.
RE: IRC - fro - 27-05-2020
(27-05-2020, 02:52 AM)venam Wrote:Yeah no worries. I was just curious because I think you're already connected to efnet.(27-05-2020, 02:37 AM)fro Wrote: Why freenode instead of efnet? #nixers is not taken there.
No particular reason other than that I forgot about efnet. In all honesty, I'm not sure it really matters where we host it or whether we're using #nixers_net instead of #nixers, as long as people can find us there should be no issue.