Jump to content
pbust

Protection for new browsers

Recommended Posts

We are currently implementing the capability of adding new custom shields. Should be ready in a couple of versions after the 0.10.0 release.

Share this post


Link to post
Share on other sites

Here's a peak preview of the upcoming custom shields. Has yet to be reflected in the GUI buttons (add/delete custom shields) but it seems to be working nicely so far :)

 

 

post-141843-0-97808000-1396065111_thumb.

Share this post


Link to post
Share on other sites

Nice Pedro.

Share this post


Link to post
Share on other sites

Google is dropping support for Google Chrome running on 32-bit hardware.  I will therefore be using Comodo Dragon and so enter an additional plea for Dragon to be included within the scope of protection by Anti-Exploit.

 

Comodo Dragon = dragon.exe

Share this post


Link to post
Share on other sites

I copied file 'dragon.exe' to 'chrome.exe' in the Comodo Dragon program folder.  Surprise surprise, Anti-Exploit saw it and dragon.exe, oops, chrome.exe runs fine.  MBAE calls it 'Google Chrome' inn its log but what the heck.

Share this post


Link to post
Share on other sites

Here's a peak preview of the upcoming custom shields. Has yet to be reflected in the GUI buttons (add/delete custom shields) but it seems to be working nicely so far :)

 

when the custom shields will finally be available, if I may ask?  thank you!

Share this post


Link to post
Share on other sites

The next version that comes out will have it.

 

Here's a sneak preview ;)

post-141843-0-96949900-1400200024_thumb.

Share this post


Link to post
Share on other sites

Thirded!  :P   Pale Moon is, and has been for a long time,  my default browser.

 

h0e7.jpg

Digging up and old thread.

 

So will mbae work with Palemoon without doing anthing?

Share this post


Link to post
Share on other sites

MBAE Free doesn't protect Palemoon by default. You "could" make it work by renaming Palemoon to firefox.exe but then you'd have to do some manual verification with every update of Palemoon (if I recall correctly you'd have to rename back to palemoon.exe, update and then rename back to firefox.exe).

 

With MBAE Premium it's much easier. You simply create a custom shield for Palemoon and it automatically protects Palemoon and all future updates to Palemoon without any user interaction.

 

Share this post


Link to post
Share on other sites

MBAE Free doesn't protect Palemoon by default. You "could" make it work by renaming Palemoon to firefox.exe but then you'd have to do some manual verification with every update of Palemoon (if I recall correctly you'd have to rename back to palemoon.exe, update and then rename back to firefox.exe).

 

With MBAE Premium it's much easier. You simply create a custom shield for Palemoon and it automatically protects Palemoon and all future updates to Palemoon without any user interaction.

 

Ah yes one could do that, if they had money they could just grab it out of thin air. I think it would make sense to have pale moon support consider they use much of the same code.

Share this post


Link to post
Share on other sites

What are the different filenames of the executables of the browsers we should be protecting (i.e. Palemoon, Maxthon, etc.)?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.