From: "Geo." 

"Adam Flinton"  wrote in
message news:f0925c.513128{at}harborwebs.com...

> OK then they could start with SE Linux. Failing that it is simply a matter
of
> "don't choose any apps during the install" such that the
only code which
is
> loaded is the code which has to be there.

this is getting kinda silly Adam, now it's like me saying we only count
exploits that affect embedded NT?

Here is where the problems come in. We have this latest exploit based on
ASN.1 which no doubt I consider a windows security issue and so it ups the
count of patches I have to apply and so it counts in my book.

However it's really not a "windows" issue. Here's a list of other
things it may or may not affect (they all are probably being checked out as
I type this":

http://asn1.elibel.tm.fr/en/uses/rfc.htm

So now the question is, is this issue which is clearly being billed as a
"windows" issue really a windows issue? In my book yes because I
had to patch my windows install (a pure windows, no extra apps, install).
Whether or not it's really an OS issue or a protocol issue or a notebook
remote exploit doesn't really matter to me. What matters is I now have a CD
which if I install from it I have to go and get patched, the CD is out of
date so it is a product defect.

Geo.

--- BBBS/NT v4.01 Flag-5