... Saturday night and the only 2 dead men I can find are on CBM and that is full. Meathook and baldric are empty and I am despondant!
Oi! You lot, stop having lives and come play wif me (sniff)
I missed you by about ten seconds :-(
You could have had a moderately entertaining hour or so finding new places to shoot me :)
Saturday night and no one on. I'm damn well going to ask for my money....................oops
...the real reason for everyone's absence from MH was the outage that the net had (probab;y in London) that affected our connection earlier in the evening between the hours of about 6pm and 10pm.
If you had tried to connect to either these forums or MH or Baldric you would not have been able to get through. The problem was only resolved later in the evening - hence all the dMw peeps and other regulars were elsewhere last night. Sorry to have missed you! Stryker spent a while trying to get to the bottom of the problem - it appeared that it was nothiing to do with the Manchester server farm, but sourced down in London and related to an effective DDOS caused by the new port 1434 virus that was running around in bulk last night.
On the other hand that explanation could have been complete bollocks, in which case I expect a clarifying post from Stryker to follow momentarily :D
TL. 8)
Following up on that last post, the Internet Storm Center provide some idea of what may have happened yesterday. Paraphrasing from their website:
The new virus (currently with no destructive payload - but hey, give it time :? ) attacks a keep-alive mechanism for Microsoft SQL Server 2000 allowing remote attackers to cause a denial of service (bandwidth consumption) via a "ping" style packet to the Resolution Service (UDP port 1434) with a spoofed IP address of another SQL Server system, which causes the two servers to exchange packets in an infinite loop.
It also causes multiple buffer overflows in SQL Server 2000 Resolution Service allowing remote attackers to cause a denial of service or execute arbitrary code via UDP packets to port 1434 in which (1) a 0x04 byte causes the SQL Monitor thread to generate a long registry key name, or (2) a 0x08 byte with a long string causes heap corruption.
The following table, whilst difficult to read, shows some log data from the extremely small minority of net users that actually bother to submit their logs to ISC. Increase the numbers to allow for the rest of net users and you have some sense of the massive upswing in activity yesterday :(
Date; Number of Sources; Number of Targets; Records
2003-01-25 80384 161182 7159564
2003-01-24 1233 346 2168
2003-01-23 19 31 46
2003-01-22 17 726 742
2003-01-21 11 68 364
2003-01-20 11 32 54
2003-01-19 25 416 450
2003-01-18 11 59 72
TL. 8)
That excuse was too technical to be true. It is my opinion that you were all out "having a life" and consequently I am disgusted with you :-)
See you tonite?
QuoteThat excuse was too technical to be true. It is my opinion that you were all out "having a life" and consequently I am disgusted with you :-)
See you tonite?
If you don't have a life BB I hope and actually rely on that you will be on this afternoon. Come to think of it actually I DEMAND that you idle all day on MH. ;)
Fancy a noon game?
I do but it depends on what "she who must be obeyed" wants to do. If I'm free I'll be on at about 1230 GMT
How can anyone be 'free' when there's footy on TV. :o
Quote but sourced down in London and related to an effective DDOS caused by the new port 1434 virus that was running around in bulk last night.
It will be fun watching Microsoft twist and turn like a twisty turny thing, explaining why the included such a daft ping feature in SQL Server 2000
Trustworthy Computing my TANGO :?
QuoteTrustworthy Computing my TANGO :?
Just why does your TANGO need computing and who is Trustworthy? :D
TL. 8)
No I meant Microsofts pathetic attempt to address security issues with their trustworthy computing ....oh forget it :wink: