MY safe zone browser hijacked! goes to fake google

[Nesivos]

Press release on new new Mailshell DNS Service

Mailshell’s New Encrypted DNS Service Secures Online Banking and Password Security
Mailshell today introduced Mailshell DNS, the first DNS service with military-grade encryption.

San Francisco, CA (PRWEB) February 13, 2011

Mailshell, the leading provider of Internet security engines for OEMs, today introduced Mailshell DNS, the first DNS service with military-grade encryption. This new DNS service closes DNS’ primary security hole and strengthens the security of all web sites. It relies on secure AES 256-bit encryption that would, according to Verisign, require trillions of years to crac

http://www.prweb.com/releases/2011/02/prweb5064014.htm

[dagrev]

Press release on new new Mailshell DNS Service

Mailshell’s New Encrypted DNS Service Secures Online Banking and Password Security
Mailshell today introduced Mailshell DNS, the first DNS service with military-grade encryption.

It relies on secure AES 256-bit encryption that would, according to Verisign, require trillions of years to crac

http://www.prweb.com/releases/2011/02/prweb5064014.htm

Or a couple weeks whichever comes first!

If this was the problem, might as well have some fun to add to the pain.

[Hermite15]

just wrote that to a friend:

"DNS poisoning is pretty rare,and bad - well I never saw it happen, neither with my ISP, nor with a third party DNS, and seeing it happening precisely with a supposed to be so secure tool - ie the safezone - not even sure if that's funny... but that's ridiculous"

 May be an option for the future >>> leave to the user the choice of the DNS server used in the SZ

[Zyndstoff (aka Steven Gail)]

Logos, mon ami,
you are neglecting your french forum badly... 

[Hermite15]

Logos, mon ami,
you are neglecting your french forum badly...  

I never really took care of it, it's not "my" forum

edit: glad to see you're doing a good job there

[dagrev]

SZ is working for me now.  I don't now why.  I did just install the massive MS patch update, but don't know that this had anything to do with it.  Still won't be doing any banking with it anytime soon even if it keeps working.

[Hermite15]

SZ is working for me now.  I don't now why.  I did just install the massive MS patch update, but don't know that this had anything to do with it.  Still won't be doing any banking with it anytime soon even if it keeps working.

yeah that is just what I meant, even if it works fine again...that's Avast SafeZone security versus your bank account safety... who wants to take the risk... and I'm going to take it a step further, Avast should remove the safe zone from AIS... at least for a while... a matter of respect for the users, and a matter of saving the company's reputation. What happened is not good.

[disPlay]

SZ is working for me now.  I don't now why.  I did just install the massive MS patch update, but don't know that this had anything to do with it.  Still won't be doing any banking with it anytime soon even if it keeps working.

yeah that is just what I meant, even if it works fine again...that's Avast SafeZone security versus your bank account safety... who wants to take the risk... and I'm going to take it a step further, Avast should remove the safe zone from AIS... at least for a while... a matter of respect for the users, and a matter of saving the company's reputation. What happened is not good.

Agree with you Logos.

[pk]

Mailshell DNS guys confirmed that they have already fixed the problem:

We've tracked the problem down to a corrupt DNS cache on one DNS HTTP servers.
This is why it was seen by some users but not others.  We have disabled the bad server and the DNS HTTP service should now be returning correct data.

I again apologize for the trouble this has caused your users and we will take steps to ensure this does not happen again

[Zyndstoff (aka Steven Gail)]

Mailshell DNS guys confirmed that they have already fixed the problem:

We've tracked the problem down to a corrupt DNS cache on one DNS HTTP servers.
This is why it was seen by some users but not others.  We have disabled the bad server and the DNS HTTP service should now be returning correct data.

I again apologize for the trouble this has caused your users and we will take steps to ensure this does not happen again

Good news!
No hijacking or DNS poisoning.
This has to be communicated widely in order to re-establish trust.

[Hermite15]

Mailshell DNS guys confirmed that they have already fixed the problem:

We've tracked the problem down to a corrupt DNS cache on one DNS HTTP servers.
This is why it was seen by some users but not others.  We have disabled the bad server and the DNS HTTP service should now be returning correct data.

I again apologize for the trouble this has caused your users and we will take steps to ensure this does not happen again

Good news!
No hijacking or DNS poisoning.
This has to be communicated widely in order to re-establish trust.

oh just a corrupt cache?   http://en.wikipedia.org/wiki/DNS_cache_poisoning

what was the nature of the corruption?

[bob3160]

"To perform a cache poisoning attack, the attacker exploits a flaw in the DNS software. If the server does not correctly validate DNS responses to ensure that they are from an authoritative source (for example by using DNSSEC) the server will end up caching the incorrect entries locally and serve them to other users that make the same request.
This technique can be used to direct users of a website to another site of the attacker's choosing. For example, an attacker spoofs the IP address DNS entries for a target website on a given DNS server, replacing them with the IP address of a server he controls. He then creates files on the server he controls with names matching those on the target server. These files could contain malicious content, such as a computer worm or a computer virus. A user whose computer has referenced the poisoned DNS server would be tricked into accepting content coming from a non-authentic server and unknowingly download malicious content."

Considering the nature of the service offered, shouldn't measures have been in place to make sure that couldn't happen
This reminds me of building a Nuclear Power plant on a fault zone. Not a wise move.  :'(

I will still use SafeZone because I think that Avast will now be making doubly sure this sort of thing never happens again as I hope Comodo learned from their mistake.

[Jack 1000]

I don't have a Pro version of Avast, but have a security question about this issue,

Would a HiJackThis log file be able to assist in this situation or not?

Jack

[YoKenny]

I don't have a Pro version of Avast, but have a security question about this issue,

Would a HiJackThis log file be able to assist in this situation or not?

Not on Vista nor Windows 7 systems as HijackThis is obsolete!

[DraKuL]

Considering the nature of the service offered, shouldn't measures have been in place to make sure that couldn't happen
This reminds me of building a Nuclear Power plant on a fault zone. Not a wise move.  :'(

I will still use SafeZone because I think that Avast will now be making doubly sure this sort of thing never happens again as I hope Comodo learned from their mistake.

exactly!