Nice to see the illiterate still have a place to hang out.
The INFECTED, too.....

On Sun, 18 Apr 2004 22:03:26 GMT, Screener1 >
vaguely proposed a theory
.......and in reply I say!:
remove ns from my header address to reply via email

Bee in bonnet.

Don't be too derisive about the infected.

I "trialled" one of these attachments. I ran a latest update (that
day's) virus checker over it (CA's AV)...clean. Then I checked it with
updated malware checkers...clean. I had a firewall running. I started
the trojan. It broke straight through the firewall, even wehn
completely blocked, and although the firewall could "see" the trojan
programme, it simply generated no traffic. I had all sorts of reasons
and excuses from the makers of the firewall.............ecepe that
another firewall _did_ catch the trojan every time.

In the end I used an online virus ID service, and it showed up the
malware in the exe file.

And this was after these things had been floating around for a week.

It appears there are two hand jobs here. The one by the perpetrators
of this shit, and the other by the purveyors of semi-capable
"protection".
>Nice to see the illiterate still have a place to hang out.
>The INFECTED, too.....

************************************************** **
I went on a guided tour not long ago.The guide got
us lost. He was a non-compass mentor.........sorry
.........no I'm not.

"Old Nick" > wrote in message
...
> On Sun, 18 Apr 2004 22:03:26 GMT, Screener1 >
> vaguely proposed a theory
> ......and in reply I say!:
> remove ns from my header address to reply via email
>
> Bee in bonnet.
>
> Don't be too derisive about the infected.
>
> I "trialled" one of these attachments. I ran a latest update (that
> day's) virus checker over it (CA's AV)...clean. Then I checked it with
> updated malware checkers...clean. I had a firewall running. I started
> the trojan. It broke straight through the firewall, even wehn
> completely blocked, and although the firewall could "see" the trojan
> programme, it simply generated no traffic. I had all sorts of reasons
> and excuses from the makers of the firewall.............ecepe that
> another firewall _did_ catch the trojan every time.

Amazing. Thanks for the warning, I don't have that kind of expertise to
remedy a situation like that.

>
> In the end I used an online virus ID service, and it showed up the
> malware in the exe file.
>
> And this was after these things had been floating around for a week.
>
> It appears there are two hand jobs here. The one by the perpetrators
> of this shit, and the other by the purveyors of semi-capable
> "protection".
> >Nice to see the illiterate still have a place to hang out.
> >The INFECTED, too.....
>
> ************************************************** **
> I went on a guided tour not long ago.The guide got
> us lost. He was a non-compass mentor.........sorry
> ........no I'm not.

On Mon, 19 Apr 2004 05:17:53 GMT, "righter" > wrote:

>
>"Old Nick" > wrote in message
.. .
>> On Sun, 18 Apr 2004 22:03:26 GMT, Screener1 >
>> vaguely proposed a theory
>> ......and in reply I say!:
>> remove ns from my header address to reply via email
>>
>> Bee in bonnet.
>>
>> Don't be too derisive about the infected.
>>
>> I "trialled" one of these attachments. I ran a latest update (that
>> day's) virus checker over it (CA's AV)...clean. Then I checked it with
>> updated malware checkers...clean. I had a firewall running. I started
>> the trojan. It broke straight through the firewall, even wehn
>> completely blocked, and although the firewall could "see" the trojan
>> programme, it simply generated no traffic. I had all sorts of reasons
>> and excuses from the makers of the firewall.............ecepe that
>> another firewall _did_ catch the trojan every time.
>
>Amazing. Thanks for the warning, I don't have that kind of expertise to
>remedy a situation like that.

Just don't click on anything that looks so stupid from the header
anyway

"DVD Doc" > wrote in message
...
> On Mon, 19 Apr 2004 05:17:53 GMT, "righter" > wrote:
>
> >
> >"Old Nick" > wrote in message
> .. .
> >> On Sun, 18 Apr 2004 22:03:26 GMT, Screener1 >
> >> vaguely proposed a theory
> >> ......and in reply I say!:
> >> remove ns from my header address to reply via email
> >>
> >> Bee in bonnet.
> >>
> >> Don't be too derisive about the infected.
> >>
> >> I "trialled" one of these attachments. I ran a latest update (that
> >> day's) virus checker over it (CA's AV)...clean. Then I checked it with
> >> updated malware checkers...clean. I had a firewall running. I started
> >> the trojan. It broke straight through the firewall, even wehn
> >> completely blocked, and although the firewall could "see" the trojan
> >> programme, it simply generated no traffic. I had all sorts of reasons
> >> and excuses from the makers of the firewall.............ecepe that
> >> another firewall _did_ catch the trojan every time.
> >
> >Amazing. Thanks for the warning, I don't have that kind of expertise to
> >remedy a situation like that.
>
> Just don't click on anything that looks so stupid from the header
> anyway

Of course. I get, from time to time, about 30 virus attempt notifications
on this email address that my isp intercepts. There're actually isps out
there that don't crack down on virus spreading and data mining spam among
their subscribers. I used to get 20 fake Microsoft patch virus emails a day
until my isp did something about it. But I was never dumb enough to
download any of them.

Old Nick > wrote in
:

> I "trialled" one of these attachments. I ran a latest update (that
> day's) virus checker over it (CA's AV)...clean. Then I checked it with
> updated malware checkers...clean. I had a firewall running. I started
> the trojan. It broke straight through the firewall, even wehn
> completely blocked, and although the firewall could "see" the trojan
> programme, it simply generated no traffic. I had all sorts of reasons
> and excuses from the makers of the firewall.............ecepe that
> another firewall _did_ catch the trojan every time.
>
> In the end I used an online virus ID service, and it showed up the
> malware in the exe file.
>
> And this was after these things had been floating around for a week.
>
> It appears there are two hand jobs here. The one by the perpetrators
> of this shit, and the other by the purveyors of semi-capable
> "protection".

Which "firewall" were you running?

YG

In article >,
"righter" > wrote:

> "DVD Doc" > wrote in message
> ...
> > On Mon, 19 Apr 2004 05:17:53 GMT, "righter" > wrote:
> >
> > >
> > >"Old Nick" > wrote in message
> > .. .
> > >> On Sun, 18 Apr 2004 22:03:26 GMT, Screener1 >
> > >> vaguely proposed a theory
> > >> ......and in reply I say!:
> > >> remove ns from my header address to reply via email
> > >>
> > >> Bee in bonnet.
> > >>
> > >> Don't be too derisive about the infected.
> > >>
> > >> I "trialled" one of these attachments. I ran a latest update (that
> > >> day's) virus checker over it (CA's AV)...clean. Then I checked it with
> > >> updated malware checkers...clean. I had a firewall running. I started
> > >> the trojan. It broke straight through the firewall, even wehn
> > >> completely blocked, and although the firewall could "see" the trojan
> > >> programme, it simply generated no traffic. I had all sorts of reasons
> > >> and excuses from the makers of the firewall.............ecepe that
> > >> another firewall _did_ catch the trojan every time.
> > >
> > >Amazing. Thanks for the warning, I don't have that kind of expertise to
> > >remedy a situation like that.
> >
> > Just don't click on anything that looks so stupid from the header
> > anyway
>
or before downloading, fire up google and type in the name of whatever
it is, often if it is a virus it will bring up the security releases
about it.

On Mon, 19 Apr 2004 01:21:46 -0400, DVD Doc
> vaguely proposed a theory
.......and in reply I say!:
remove ns from my header address to reply via email


OK. Rant still on.

As I said it's not always that easy. These things must work, because
they are still being sent. There are many infected PCs out there. I
can't believe that all of them are the reuslt of the deliberate
actions of the infected person. Too often, the default setup for many
programmes is to open the attachement, willy nilly. Bam!

And the people most likely to get caught are those with the least
other protection.

I agree don't click. But maybe it's time we all started sending
details to our ISPs and the pruveyors of "protection". Either it would
be enough of a nuisance to get more action, or at least make sure all
sig recog files were up to date.

>Just don't click on anything that looks so stupid from the header
>anyway

************************************************** **
I went on a guided tour not long ago.The guide got
us lost. He was a non-compass mentor.........sorry
.........no I'm not.

On Mon, 19 Apr 2004 05:17:53 GMT, "righter" >
vaguely proposed a theory
.......and in reply I say!:
remove ns from my header address to reply via email

No worries. BTW, I am no expert believe me. It was persistance, with I
suppose a bit of expertise, and help from online reps from companies.

>Amazing. Thanks for the warning, I don't have that kind of expertise to
>remedy a situation like that.


************************************************** **
I went on a guided tour not long ago.The guide got
us lost. He was a non-compass mentor.........sorry
.........no I'm not.

On Mon, 19 Apr 2004 05:36:47 GMT, "righter" >
vaguely proposed a theory
.......and in reply I say!:
remove ns from my header address to reply via email

Please read my post "Maybe we should all report the malware"
************************************************** **
I went on a guided tour not long ago.The guide got
us lost. He was a non-compass mentor.........sorry
.........no I'm not.

Screener1 > wrote:

> Nice to see the illiterate still have a place to hang out.
> The INFECTED, too.....

And you have cross-posted this message to all those newsgroups for which
purpose, exactly?

Rowland.
[FU set appropriately]

--
Remove the animal for email address:
PGP pub key 0x62DCCA78 Sorry - the spam got to me
http://www.mag-uk.org
UK biker? Join MAG and help keep bureaucracy at bay