Freenode IRC is down
Does anyone know what is going on?
9 comments
They are taking a massive DDoS, not only it is having recurrent netsplits, the services (chanserv, nickserv) are getting up and down, and lots of bogus users are logging in and off (right now I am seeing a 31NAEEEF5Q for example... and some minutes ago I saw 18 users in the same style in a channel that had 3 real users)
The "bogus users" are probably bots like those of scrollback.io's (which is a service used by a few channels that I frequent).
It started experiencing frequent netsplits as the Super Bowl stream began, and went down completely a few seconds before the Half-Time Show, then came back up for a few seconds right after it ended. Since then I've been reconnecting over and over without being able to load any channels.
It's just come back up as of five minutes ago, with normal chat working.
(US user)
It's just come back up as of five minutes ago, with normal chat working.
(US user)
Lots of mentions in here of the term "netsplit". I hadn't heard of it before, so here's some context: http://en.wikipedia.org/wiki/Netsplit
This probably doesn't help:
$ dig chat.freenode.net | grep 127
chat.freenode.net. 264 IN A 127.0.0.1
chat.freenode.net. 264 IN A 127.0.0.2Did a double take when I saw this in irssi:
23:22:03 Looking up irc.freenode.net
23:22:03 Connecting to irc.freenode.net [127.0.0.1] port 6697
23:22:03 warning SSL handshake failed: Connection refused
23:22:03 Connection lost to irc.freenode.netFYI using IRC over SSL is useless.
FYI, no, it's not and this stupid line of thinking is getting old.
Just because the NSA can also connect to the server, join the same channels you're in, and see your conversations does not mean SSL is "useless".
It's like saying that locking your car doors "is useless" because someone can just smash the window in.
Just because the NSA can also connect to the server, join the same channels you're in, and see your conversations does not mean SSL is "useless".
It's like saying that locking your car doors "is useless" because someone can just smash the window in.
It's not stupid nor is your analogy apt.
All it takes is one user not using SSL or not verifying certs for your chats to be vulnerable to eavesdropping.
All it takes is one user not using SSL or not verifying certs for your chats to be vulnerable to eavesdropping.
That is bullshit. SSL on IRC enables you to:
- evade local packet inspection
- ensure no local MITM is performed
- log in to services via a client cert instead of a passphrase
Please take your FUD elsewehere.
- evade local packet inspection
- ensure no local MITM is performed
- log in to services via a client cert instead of a passphrase
Please take your FUD elsewehere.
Let me ask you something.
What purpose, other than eavesdropping, is there for performing MITM on irc?
What purpose, other than eavesdropping, is there for performing MITM on irc?
Probably not much. But it's nice to minimize attack surfaces and annoy arpspoofing skids which might be on your LAN.
Some people may reuse NickServ passwords for other more important things. Those passwords are just sent over plaintext.
Credential theft
Even if it is, I have to identify with nickserv. I'd rather not do that in plaintext.
FYI, you can still connect by using a named server, ie roddenberry.freenode.net.
http://freenode.net/irc_servers.shtml
http://freenode.net/irc_servers.shtml
[deleted]
It sounds like it primarily affecting US servers. Avoid those and don't use the chat.freenode.net servers.
Mine's not working either. Connection refused on both +7000 and +7070