C
cortez
Please read the following carefully. It has implications
for all MSAS users.
Yesterday i posted a notice concerning an issue
submitting a spyware report. The spyware report would not
submit due to what it said was "IE Proxy Settings". Two
MS Techno's acknowledged the issue as a MSAS software one
saying it would be fixed with the release of Beta2.
The implications are...a very real spyware threat exists
which MSAS can't act on. This also leaves all other other
MSAS users potentially vulnerable because definition and
signature files can't be updated. And how far off is Beta
2? They didn't say.
So heres the issue.....MSAS alerted me to a host file
issue concerning Oneclicksearches.com and that it was ok
because it was on loop back. I typed the URL into my web
browser and a Microsoft Internet Explorer window opened
with the following message.....Attention! Your PC is
infected with Spyware....Browser version:4.0 (Compatible;
MSIE 6.0; WindowsNT5.1)"StealthSWs114.h!dll"
ver.4.442as18a. Access Port #33299. You are at risk...
blah blah blah.
Note that it was MSIE which opened with the details and
not MSAS... More importantly...how did this manage to get
past MSAS protections shields which were active??? and
how did the resulting full scan not pick it up??? obvious
not on the signature files. Also... MSAS realtime active
protection does not obviously recognise the encoded
language which is common to most spyware. And how do you
like their response and solution??? is this the behaviour
you would expect from a company with professionally
trained software developers and technicians???
The important lesson here is that MSAS is a beta and beta
realise that as such it's not to be relied on as the sole
source of spyware protection. Don't get caught out. Have
a few other more well known and reputable programs
running at the same time. This also once again highlights
the ongoing IE security issues that seem to plague MS.
My advise to Microsoft. Best you understand the serious
nature of this issue and treat it with the urgency it
deserves. This is not just about your spyware. It's about
the spyware community you set up and your commitment to
them and it's also about the community you respresent
having confidence in your company to act appropriately.
In this case words are not enough. Get real and be
authentic. You started out with a great product concept
developed by creative intelligent human beings who were
passionate about being of service to others. The
community will judge you by what you do and not by what
you say so the time to act is now. If you can't get small
issues like this right now how are are going to behave
when a big one comes your way???
You need to be grateful and thankful that the community
takes the time and cares enough to inform you of these
issues. If you don't act accordingly you end up getting
peoples backs up and drawing to yourself alot of self
destructive negative criticism.
for all MSAS users.
Yesterday i posted a notice concerning an issue
submitting a spyware report. The spyware report would not
submit due to what it said was "IE Proxy Settings". Two
MS Techno's acknowledged the issue as a MSAS software one
saying it would be fixed with the release of Beta2.
The implications are...a very real spyware threat exists
which MSAS can't act on. This also leaves all other other
MSAS users potentially vulnerable because definition and
signature files can't be updated. And how far off is Beta
2? They didn't say.
So heres the issue.....MSAS alerted me to a host file
issue concerning Oneclicksearches.com and that it was ok
because it was on loop back. I typed the URL into my web
browser and a Microsoft Internet Explorer window opened
with the following message.....Attention! Your PC is
infected with Spyware....Browser version:4.0 (Compatible;
MSIE 6.0; WindowsNT5.1)"StealthSWs114.h!dll"
ver.4.442as18a. Access Port #33299. You are at risk...
blah blah blah.
Note that it was MSIE which opened with the details and
not MSAS... More importantly...how did this manage to get
past MSAS protections shields which were active??? and
how did the resulting full scan not pick it up??? obvious
not on the signature files. Also... MSAS realtime active
protection does not obviously recognise the encoded
language which is common to most spyware. And how do you
like their response and solution??? is this the behaviour
you would expect from a company with professionally
trained software developers and technicians???
The important lesson here is that MSAS is a beta and beta
realise that as such it's not to be relied on as the sole
source of spyware protection. Don't get caught out. Have
a few other more well known and reputable programs
running at the same time. This also once again highlights
the ongoing IE security issues that seem to plague MS.
My advise to Microsoft. Best you understand the serious
nature of this issue and treat it with the urgency it
deserves. This is not just about your spyware. It's about
the spyware community you set up and your commitment to
them and it's also about the community you respresent
having confidence in your company to act appropriately.
In this case words are not enough. Get real and be
authentic. You started out with a great product concept
developed by creative intelligent human beings who were
passionate about being of service to others. The
community will judge you by what you do and not by what
you say so the time to act is now. If you can't get small
issues like this right now how are are going to behave
when a big one comes your way???
You need to be grateful and thankful that the community
takes the time and cares enough to inform you of these
issues. If you don't act accordingly you end up getting
peoples backs up and drawing to yourself alot of self
destructive negative criticism.