How many copies of the latest fucking virus are in my fucking mail? TOO FUCKING MANY. With a new one on average every one hundred and fifty seconds for the past three days! I think the Bayesian filter is this close to deciding the word 'Microsoft' indicates spam.
Your excuses are tired. The bogus analogies, the belligerent whininess. You talk like junkies in danger of being cut off. YOUR COMPUTERS ARE AGENTS OF CONTAGION. THEY DESERVE TO BE BANISHED FROM THE NET FORTHWITH. I wish to declare my full and ardent support for this move. People who complain this is unfaaair and toooo haaard are like people who run over kids and whose only defence is that they can't be expected to know how to drive and therefore couldn't possibly be held responsible.
I fully expect the comments on this entry to be filled with lame justifications, ridiculous analogies and badly-misremembered Microsoft FUD. Don't whine to me for daring to complain about your intrinsically unsecurable systems - just CLEAN UP AFTER YOURSELVES AND YOUR COMPATRIOTS, YOU SKANKY SHITBAGS.
(Thunderbird seems to detect the web page variant of the virus, but not the mailbounce one - it doesn't like running slabs of MIME-encoded binary through the filter. Filter on the string TVqQAAMAAAAEAAAA// - that's the beginning of the virus code, and will nail it nicely.)
Note: I expect things to be even worse when popular Linux is afflicted with self-propagating rootkits. For the same reason.
(no subject)
Date: 2003-09-21 02:29 pm (UTC)Some large Balkanised organisations already do this; "The marketing department is being billed pro-rata for the bandwidth they consume; this month, that means you will be paying about 63% of our bandwidth bill. Here's a copy of the site-licensed virus scanner. Use it and avoid the same bill next month. Have a Nice Day."
You can, trivially, detect M$ executables with Spamassassin (look for the magic number which identifies an EXE to the kernel) and score them up.
(no subject)
Date: 2003-09-21 02:32 pm (UTC)(no subject)
Date: 2003-09-21 02:33 pm (UTC)Cricket clap!
I'm an ardent MAC user.
Pish and tosh to McDonalds. I mean Microsoft.
(And all who have to sail in her).
Do you think this E mail bugging will die down any time soon?
We don't have any spam filtering system in place here at Swarf HQ.
I am the spam filtering system and I no longer enjoy my job...
(no subject)
Date: 2003-09-21 02:34 pm (UTC)What are you using for an email program? The current Mozilla isn't quite OSX-conformant, but eats spam like nothing else.
(no subject)
From:(no subject)
From:(no subject)
Date: 2003-09-22 10:06 pm (UTC)(no subject)
Date: 2003-09-21 03:28 pm (UTC)Though on a similair note, god i love Thunderbirds filters.
(no subject)
Date: 2003-09-21 03:48 pm (UTC)(no subject)
Date: 2003-09-21 03:57 pm (UTC)(no subject)
Date: 2003-09-21 04:03 pm (UTC)(no subject)
Date: 2003-09-21 04:33 pm (UTC)But seriously:
CLEAN UP AFTER YOURSELVES AND YOUR COMPATRIOTS
I've been doing that up here in Liverpool for quite a while now. I have made sure that quite a few goths up here have decent firewalls and anti-virus software.
Really it's a matter of luser era-ducation. If they don't learn, take their net access away...
Or hit them. Or something like that...
I feel so left out
Date: 2003-09-21 04:34 pm (UTC)(no subject)
Date: 2003-09-21 05:08 pm (UTC)Incidentally, anyone who thinks Diva is going overboard or being unneccessarily harsh: think about this for a moment. Diva is one of the most patient, most polite men I know. He's certainly a damned sight more patient and tactful than I am, for example. It takes quite a bit to provoke this kind of outburst.
I've received enough of this virus spam to cause Mozilla to crash two or three times a night under the onslaught, causing a forced reboot of my system. And I've received maybe a tenth of the crap Diva has.
Quite frankly I'm not surprised he's a tad pissed off.
(no subject)
Date: 2003-09-21 06:55 pm (UTC)Woah. Either he's mellowed considerably, or you're *really* bad.
Diva got himself an interesting reputation when we were working together. There were more than a few complaints along the lines of "who does he think he is, the BOFH?".
But yeah, string the fuckers up. And the idiots with the virus scanners that send warning messages to the forged sender can go up with 'em -- I get as many of those at work as I do the actual virus.
(no subject)
From:(no subject)
Date: 2003-09-21 05:17 pm (UTC)Damn it's good to read you in rant mode ;-)
(no subject)
Date: 2003-09-21 05:38 pm (UTC)So blame the lusers, some of us know how to protect the crap we're forced to use ;P
(no subject)
Date: 2003-09-22 02:34 am (UTC)(no subject)
Date: 2003-09-21 05:54 pm (UTC)(no subject)
Date: 2003-09-21 06:00 pm (UTC)[1]it's part laziness and part financial. I can get buttloads of free software with an MS based system and I have buttloads of software that I've paid for. If I switched I'd have to reinvest WAY too much money to make it worth the effort.
(no subject)
Date: 2003-09-22 04:23 am (UTC)(no subject)
From:(no subject)
Date: 2003-09-21 06:07 pm (UTC)The pattern is predictable. CERT advisory goes out. 12-36 hours later, the Windows Update thingy shows up in system trays around the world. A week later, I see the $VBC internal IT announcements coming out saying "Patch NOW, dammit!" and giving directions for internal access to the patch. Then two days later, the emails with the virus payloads start flooding in. There's a LOT of Windows boxes out there, and many of them are at least competantly-managed ENOUGH to avoid contributing to the problem. All it really takes is the FIVE FUCKING MINUTES every couple of week to put the patch on that MS makes available. It's all coming from unpatched machines. Machines where the owners didn't know or care what the little update picture was, or thought "I'll do it next week" or "I'm safe! I have anti-virus software!"
Binky, anti-virus software doesn't protect your machine. It tells you when you're already fucked. If you put on the patch, even if you get an infected email, even if you click on the attachment, it won't be able to do anything except crash *your* machine. Most importantly, it won't be able to do it's main job of passing itself on. By the time your AV software yells and you do something about it, it's spooged itself on a hundred other machines, hoping to find a couple of fertile ones. Ones where the owners ALSO thought "I'll take care of that next week."
There's been discussion before about how Evil it would be for Microsoft to remove the choice option about downloading updates and patches to remote machines, so it happens *WITHOUT* the owner's aquiescence. I used to think that that was a horrible idea, and was giving MS way too much power. I think I'm changing my mind.
(no subject)
Date: 2003-09-21 08:11 pm (UTC)At work, I am forced to use Win2K, Outlook, and Explorer (yes, some of what I do is unfortunately browser-specific). I leave my computer running over the weekend so that it can thoroughly Nortonize itself every Saturday, and use Windows Update as regularly and religiously as if it were beads on a rosary. I also have serious filtering set up in Outlook, so if anything lands in my actual inbox and doesn't get filtered, I'm immediately suspicious of it. I don't even open joke emails from my coworkers--trash 'em all.
What gets me is that when I asked the second-in-command of our IT department whether they recommended that people patch their machines regularly, he said, "Well, you know, some patches can make your machine run slower... all you need to do is run antivirus software. What, are you afraid of hackers or something? If something goes wrong, we'll fix it." Leaving aside the fact that I do have credit card and bank account information on my machine and that it's going back and forth over our email servers all day, as far as I know completely unencrypted, no, I'm afraid of our site going down because our network is totally clogged with bogus packets! How the hell can you admin a Windows network for a company where Outlook is practically mandated--when I first started working there, I was told by a coworker that I "needed" to be using it because other people were doing things that required a recipient to have it, which sounded dubious from the beginning and of course turned out to be completely untrue--and not teach people how to take proper care of their machines?
Not to mention that plenty of my coworkers are stupid enough to open any attachment called "cute.tla" and be shocked when it infects their system. We email clients and other coworkers nonstop during the day; we are tremendously susceptible to virii. But when I got my work machine, pre-configured, Norton was installed but totally dormant, not even set to automatically download new virus definitions. Stupid stupid stupid.
*sigh*
(no subject)
Date: 2003-09-22 01:06 am (UTC)(no subject)
Date: 2003-09-22 01:08 am (UTC)head$ spamstatus
Scanned: 867
Passed: 355
(no subject)
Date: 2003-09-22 02:24 am (UTC)My fun[at]thingy.apana.org.au address has been all across the net for the past six years, so I get a comprehensive view of this sort of thing.
(no subject)
From:(no subject)
From:(no subject)
From:(no subject)
Date: 2003-09-22 09:41 am (UTC)T ~s ^SUBJECT:
That's for the faked-bounce kind.
And, obviously, I now have a procmail rule to do the same (you know, because that's more useful than writing SA rule for it, when I've already got another procmail rule consulting SA ;^>).
Other options
Date: 2003-09-22 11:42 am (UTC)Take a squint at http://www.peteweb.com/winrg.php
It is indeed real good !
(no subject)
Date: 2003-09-22 02:03 pm (UTC)(no subject)
From:(no subject)
From:Re: Not meaning to rain on your parade
From:Re: Not meaning to rain on your parade
From:Re: Not meaning to rain on your parade
From:Re: Not meaning to rain on your parade
From:Re: Not meaning to rain on your parade
From:Re: Not meaning to rain on your parade
From:Re: Not meaning to rain on your parade
From:Re: Not meaning to rain on your parade
From:Re: Not meaning to rain on your parade
From:Re: Not meaning to rain on your parade
From:Re: Not meaning to rain on your parade
From:Re: Not meaning to rain on your parade
From:Re: Not meaning to rain on your parade
From:Re: Not meaning to rain on your parade
From:Re: Not meaning to rain on your parade
From:Re: Not meaning to rain on your parade
From:Re: Not meaning to rain on your parade
From:Re: Not meaning to rain on your parade
From:Re: Not meaning to rain on your parade
From:(no subject)
Date: 2003-10-01 03:41 am (UTC)Unix/Linux users do seem to be more aware of such stuff and inform one another and fix quicker, that probably contributes to the stats/results. As does the market share of OS use.
But another contribution is faith in the OSs security itself. I worked for an ISP, they installed new 2 Red Hat machines in Cardiff and sent them up to London, we got them and found they'd both already been root kitted. Too much faith is a dangerous thing.
A badly set up Linux box is just as insecure as a reasonably set up windows one, though there's less people able to exploit it, so there's more chance of geting away with it.