Online Armor: Allow = Block

Australia is on the other side of the world, perhaps that is why the good Online Armor folks have reversed the meaning of the words Allow and Block.

Always thought that a block entry in your Hosts file would block traffic to the corresponding IP address. Not so with Online Armor's Hosts file! It actually allows it.

The corresponding Online Armor Web Help page offers a most peculiar explanation for the phenomenon:

* Allow – Allows the selected entry in your HOSTS file.
* Block – Blocks the selected entry from being made to your HOSTS file. (sic)

http://www.tallemu.com/webhelp3/Hosts.html#list

Am I the only one who finds this strange?

 

This is actually not strange if you sink deeper. OA handles HOSTS file and so allows or denies the entries other programs can try to write there. It doesn't use HOSTS files to master network traffic because it handles network by its own means.

So, if some program tries to write to the HOSTS something like:

malicious.IP.address windowsupdate.com

OA warns you about it and you can block this entry now and forever.

 

You're not alone!

There could be an indication of status within the HOSTS file, # against the dodgy site registering a instead of the current Only on reading Tall Emu's description does it make sense.

I am going with your theory about Australians being on the other side of the world, aka upside down, which is causing all the confusion. I wonder if any Australian users of Comodo can confirm the status of the thumbs up or down for banned websites. This could just be affecting those of us that are currently upside down to those confusing Australians.

 

You have got to be kidding me, if you dont understand it in english then get it translated, OA is designed to stop things that might be bad being added to youre host file, hence if OA considers it bad or even if something is being added to youre host file OA will either prevent it or let you know so you can make that decision, hence BLOCK if it is considered good then it will be allowed.

Nessy

 

well just as avira security suite and zone alarm have options to "lock host files" so no changes could be made by malware etc similarly OA has a block option its just how they call it.OA in learning mode checks host files and then offers user the option of blocking changes to them.

 

Thank God

But really, as apps are becoming more complex we need to have some sort of standardisation as to what things actually mean. It's a crazy situation that each company still has different ideas of what an interface should look like, leaving end users even more confused after reading their manuals. Less is more!

 

Hosts file weren't meant as a "blacklist". So the OA approach is more correct , and in keeping with how the host file is meant to be used.

 

Perhaps a 'Keep it Simple' approach would help.
In this case it's accept what you can't change.
On my side of the world Allow = permission granted.
If that doesn't translate well in all areas of the globe then I just need to try to keep track of the differences or use a different product.
Enjoy the day.
Hugger

 

After taking a quick look at the options tab...



... can anyone tell me which part is the most difficult one to understand.

Cheers

 

ROFLMAO

 

This post is the winner.

When we did the HOSTS checking, I never contemplated the use of HOSTS as a blacklist. We'll be changing how our hosts works soon enough. I really dont like the current implementation as it causes too much confusion.

Technically right or not - if people do not understand it, it's wrong and needs to be fixed.

 

Problem is, very few people seem to know that This is how its function is explained on the most popular site on the subject, arguably a major source of information for many, if not most people. Note that it contains the word 'block' three times in the first 120 words:

http://mvps.org/winhelp2002/hosts.htm

 

MikeNash

" Technically right or not - if people do not understand it, it's wrong and needs to be fixed. "

Yes indeed ! Good for you.