Timestamps are in GMT/BST.
[1:07] * helix84 (~ctenar@195.178.95.132) Quit (Ping timeout: 268 seconds)
[1:29] * aawoods_ (~awoods@c-67-165-245-76.hsd1.co.comcast.net) has joined #duraspace
[1:32] * kshepherd (kim@ec2-184-73-177-234.compute-1.amazonaws.com) Quit (Ping timeout: 276 seconds)
[1:32] * awoods (~awoods@c-67-165-245-76.hsd1.co.comcast.net) Quit (Ping timeout: 276 seconds)
[1:37] * kshepherd (kim@ec2-184-73-177-234.compute-1.amazonaws.com) has joined #duraspace
[4:58] * helix84 (~ctenar@195.178.95.132) has joined #duraspace
[6:31] -holmes.freenode.net- *** Looking up your hostname...
[6:31] -holmes.freenode.net- *** Checking Ident
[6:31] -holmes.freenode.net- *** Found your hostname
[6:31] -holmes.freenode.net- *** No Ident response
[6:31] * DuraLogBot (~PircBot@ec2-107-22-210-74.compute-1.amazonaws.com) has joined #duraspace
[6:31] * Topic is '[Welcome to DuraSpace - This channel is logged - http://irclogs.duraspace.org/]'
[6:31] * Set by cwilper!ad579d86@gateway/web/freenode/ip.173.87.157.134 on Fri Oct 22 01:19:41 UTC 2010
[8:26] * aawoods_ (~awoods@c-67-165-245-76.hsd1.co.comcast.net) Quit (Ping timeout: 252 seconds)
[8:28] * aawoods_ (~awoods@c-67-165-245-76.hsd1.co.comcast.net) has joined #duraspace
[10:11] * helix84 (~ctenar@195.178.95.132) Quit (Ping timeout: 245 seconds)
[10:18] * helix84 (~ctenar@195.178.95.132) has joined #duraspace
[14:26] -holmes.freenode.net- Server Terminating. Received SIGTERM
[14:26] * Disconnected.
[14:27] -kornbluth.freenode.net- *** Looking up your hostname...
[14:27] -kornbluth.freenode.net- *** Checking Ident
[14:27] -kornbluth.freenode.net- *** Found your hostname
[14:27] -kornbluth.freenode.net- *** No Ident response
[14:33] -tomaw- [Global Notice] Earlier today the freenode infra team noticed an anomaly on a single IRC server. We have identified that this was indicative of the server being compromised by an unknown third party. We immediately started an investigation to map the extent of the problem and located similar issues with several other machines and have taken those offline. For now, we recommend that every change their NickServ password as a precaution.
[14:33] -tomaw- [Global Notice] We'll issue more updates as WALLOPS and via social media!
[18:31] -tomaw- [Global Notice] Some have pointed out that it might have been useful if I had told you HOW to update your passwords. Use /msg NickServ SET PASSWORD <NEW PASS> (without the <>). Thanks!
These logs were automatically created by DuraLogBot on irc.freenode.net using the Java IRC LogBot.