Jump to content

Recommended Posts

Win 10 Pro, Firefox 63.01 (64 bit) and EIS 12.0.27.0.

EIS has recently failed to start banking protection secure browser when I open my internet banking login page. There have been recent updates to Win 10, Firefox and EIS, so the cause is not clear. The only way I can open the secure browser is from within EIS, but that is not very convenient. Previously, I would open internet banking from a bookmark in Firefox and the secure browser would automatically open. How can I get this functionality back?

Share this post


Link to post
Share on other sites

Does the error persist after a system restart? To make sure that the system has been fully restarted, run "shutdown -r -t 0" from the tart menu.

Share this post


Link to post
Share on other sites

Yes it does persist after system restart. Strangely, when I opened the login page to my stockbroker's secure site, the banking protection secure browser opened and offered itself for that site. I want it to do the same for my internet banking site!

Share this post


Link to post
Share on other sites

Any chance that your bank is either St George or Westpac? I know that BPP doesn't currently work with either of them and Firefox, though it should work with IE11.

Share this post


Link to post
Share on other sites

Aha!! My bank is Bank SA, which is owned by Westpac, so you have probably identified the problem. The problem has only recently appeared. BPP worked fine before I went overseas mid-October. I just tried MS Edge browser (is that IE11?) but there was no sign of BPP.

Share this post


Link to post
Share on other sites

I just tested https://ibanking.banksa.com.au/ibank/loginPage.action and can confirm that it doesn't work with Firefox but does work with IE 11 (Internet Explorer 11)

BTW. Bank SA seems to be using the same software as St George

Share this post


Link to post
Share on other sites

I have the problem with the edge browser

Share this post


Link to post
Share on other sites

ibanking.banksa.com.au uses HTTP/2. Since Banking and payment protection doesn't support HTTP/2 yet, it won't open in a secure browser automatically.

Share this post


Link to post
Share on other sites
1 hour ago, AndrewJones said:

I have the same problem but my bank is LLoyds

www.lloydsbank.com should work fine as it doesn't support HTTP/2.0

Which browser are you using?

Edited by stackz

Share this post


Link to post
Share on other sites

Doesn't work for citi or chase either.  Has never, in nearly 2 years.  Always using Firefox.

Share this post


Link to post
Share on other sites

Thanks for all responses. It seems that the problem might affect a lot of users and that ESET should look at doing something about it.

Share this post


Link to post
Share on other sites
On 11/7/2018 at 7:24 AM, DGT said:

Aha!! My bank is Bank SA, which is owned by Westpac, so you have probably identified the problem.

The website https://ibanking.banksa.com.au uses HTTP/2, hence it's not open in a secure browser automatically.

Share this post


Link to post
Share on other sites

I have recently noticed the same problem.  Using Google Favorites-  two bank websites that were saved with eset protection have lost the eset protection.  Bank of America and Associated Credit Union.  As I have been trying to get info., I also noticed that when using Google Chrome, it says "Not Secure" on the ese tbanking and payment protection url

Share this post


Link to post
Share on other sites
7 hours ago, Jesse S. said:

I have recently noticed the same problem.  Using Google Favorites-  two bank websites that were saved with eset protection have lost the eset protection.  Bank of America and Associated Credit Union.  As I have been trying to get info., I also noticed that when using Google Chrome, it says "Not Secure" on the ese tbanking and payment protection url

That's weird. On my machine both were opened in a secure browser. Please post a list of installed ESET modules.

Is the eicar test file detected when you download it from https://secure.eicar.org/eicar_com.zip?

Share this post


Link to post
Share on other sites
13 hours ago, Jesse S. said:

I also noticed that when using Google Chrome, it says "Not Secure" on the ese tbanking and payment protection url

This is due to Chrome's recent changes to override the "lock" symbol processing for HTTPS web sites since "big brother" Google feels nothing on the web can be trusted unless Google "has in hands into it."

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.

×