Users browsing this thread: 2 Guest(s)
| 
 | |||
| 
 | |||
| 
					what is the nick max character limit?
                                         | |||
| 
 | |||
| 
					If I remember correctly it's 8 Edit- spelling | |||
| 
 | |||
| 
					damn it, off by 1
                                         | |||
| 
 | |||
| 
					it's 9. also i think i fixed apk's problem with drinking and irc. | |||
| 
 | |||
| 
					yeah, so looks like i will just stick with rchaos on the forums
                                         | |||
| 
 | |||
| 
					Looks like the unix.chat ssl cert has expired:  verify error:num=10:certificate has expired notAfter=Jun 14 11:25:00 2017 GMT | |||
| 
 | |||
| 
					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. | |||
| 
 | |||
|  | |||
| 
 | |||
| 
					unix.chat is now failing as well.
                                         | |||
| 
 | |||
| 
					bonjour Je ne peux me connecter a nixers, j'ai connection refused | |||
| 
 | |||
| 
					C'est un forum anglophone, pour info :) Ensure that you're connecting via SSL on port 6697. The service is not accessible without SSL. | |||
| 
 | |||
| 
					who can invite me to irc, nick is jjan
                                         | |||
| 
 | |||
| 
 | |||
| 
					@z3bra yes #unix, it says you need an invite or am i missing something out
                                         | |||
| 
 | |||
| 
					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.. | |||
| 
 | |||
| 
					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 | |||
| 
 | |||
| 
					>> *nix users needing invites to networks ;)
                                         | |||
| 
 | |||
| 
					Any idea why I'm banned? nick = fraun
                                         | |||
| 
 | |||
| 
					Hi again, any luck unbanning me?
                                         | |||
| 
 | |||
| 
					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# vi /etc/inetd.conf Code: irc-freenode  stream  tcp  nowait  nobody  /usr/bin/openssl   openssl s_client -quiet -connect irc.freenode.net:6697And 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 | |||
| 
 | |||
| 
					nice one Josuah! Taking the best from unix IPC ;)
                                         | |||
| 
 | |||
| 
					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# ii -s unix.chat -u /tmp/unix.chat And then you have ~/irc/unix.chat and not ~/irc/127.0.0.1. :) | |||
| 
 | |||
| 
					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"For anyone that runs into this, you can turn off verification with: Code: /set irc.server.<identifier>.ssl_verify off | |||
| 
 | |||
| 
					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. | |||
| 
 | |||
| 
					Is it because of the TLS issues?
                                         -- <mort> choosing a terrible license just to be spiteful towards others is possibly the most tux0r thing I've ever seen | |||
| 
 | |||
| 
 | |||
| 
					Why freenode instead of efnet? #nixers is not taken there. I think the change is a solid idea btw. | |||
| 
 | |||
| (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. | |||
| 
 | |||
| (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. | |||

 
                                			


 
                                			

 
                                			
 
                                			



