DarthSikle
GFHH Moderator
http://www.exisle.net/mb/index.php?showtopic=37066
the blood letting continues.
Orpheus says "fuck you TK"
the blood letting continues.
Orpheus says "fuck you TK"
DarthSikle said:http://www.exisle.net/mb/index.php?showtopic=37066
the blood letting continues.
Orpheus says "fuck you TK"
jack said:I have to be able to speak for myself over there.
Shatna said:Want me to do it?
"Nice going, you fucks. You fucked with the wrong psycho this time. I beat fucking Veitch, fucked him right in the neck you fucks. (laughing)"
The staff has reviewed/discussed all facts available to us, especially:
1. darthsikle was permanently banned on Jan 11, 2006. Since then, he has made warnable (offensive) posts through two accounts (logging in from his own work IP with the proper L/P and no sign of account hacking). Whatever the original intent in opening those accounts, they were now clearly deliberate duals, with the cooperation of the account starter, to circumvent darthsikle's permaban. Public notice given in AQG on February 24 [link] that further illicit activities from this might lead to it being blocked, which would prevent *any* account from being accessed from that one IP, in accord with existing EI precedents.
2. After discussing "jack's" posts from DS' IP, the admins, as warned, imposed a block on that IP, where DS and BDM (but no other EIers) work. It was regrettable that DS did not have more regard for his pal BDM's convenience, but BDM's *account* was not affected. He was more than welcome at that point to post from any other legal and legitimate IP, such as his home, library, free internet cafe, public hotspot or other public access, as many EIers do.
3. On March 19, after the IP block, BDM posted again, from an IP near his stated/logged geographic location. The staff was pleased to see his return after the IP block.
4. On March 20, in an unrelated matter, Gagh was suspended for proxy use (China and US on consecutive days, when all prior access had been from the location in his public profile [UK]). A review of his IP use showed that one of his proxy IPs had attempted unsuccessfully, in recent weeks, to compromise a staff account. This was the same IP used by BDM the prior day! Since we did not have any specific evidence linking this attack to either Gagh or BDM specifically, we acted only against the IP itself, and not against any member account. At no time did BDM seek authorization to use this proxy.
5. Later that day, after the attacking IP was blocked, BDM posted from a second proxy: a residential cable account in greater Boston, hundreds of miles from his stated location and prior IPs. Orpheus, a customer of that same greater Boston ISP, knew that its ToS strictly forbids public proxies. Since BDM had asked us to authorize use of this proxy, Orpheus had to check its legitimacy. His ISP told him that the proxy was an infected residential computer. A web search later showed that the same ToS against proxies applied to BDM's previous IP as well. Most cable ISPs explicitly prohibit public proxies, which are a security threat *inside the ISP's network*, especially to customers on the same ISP LAN leg.
We feel that this pattern of *multiple* proxy use is serious. There was no request for authorization of the first proxy, and a request was made for authorization of the second only after the first had been blocked. There are also serious questions of how/why BDM knew of and used these illicit proxies instead of one of the many legitimate, non-anonymizing public proxy services. Using the computers and IPs of innocent, unwitting victims is not benign, even if one did not originally infect the system oneself. Your computer is not legitimately "up for grabs" to anyone who can manage to get in through (e.g.) a published hacker list.
In light of these facts, and Staff discussion, we feel that this pattern of activity justifies the indefinite suspension of Big D. McGee, and it will therefore stand.
Part of this is my fault. BDM asked me where to get a proxy. I told him to use Samair's list of proxy's.