This is *not* a safe practice. If you can leave the XSS filter on, then please do.
I didn't mention XSS filter was on, as I thought exceptions had a meaning only if XSS filter was on.
What I meant was, don't write an exception if you can help it. Keep filtering these requests, because they're dangerous.
If the site breaks when the XSS filter is triggered, then I recommend using a separate profile for your banking, so that your bank can't be attacked by other sites in the same window..
======
Thrawn
------------
Religion is not the opium of the masses. Daily life is the opium of the masses.
True religion, which dares to acknowledge death and challenge the way we live, is an attempt to wake up.
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:40.0) Gecko/20100101 Firefox/40.0
Thrawn wrote:
If the site breaks when the XSS filter is triggered, then I recommend using a separate profile for your banking, so that your bank can't be attacked by other sites in the same window..
I wish I knew what you mean by "breaks". What my experience is that when XSS filter is on, with no exception, there is a 15sec delay, where firefox window "freezes" (no response at all). After that the prompt save/open window comes out. The story is repeated for every new or same refreshed page in eurobank.gr
Mozilla/5.0 (Windows NT 6.3; WOW64; rv:40.0) Gecko/20100101 Firefox/40.0
maxer wrote:I wish I knew what you mean by "breaks".
It means "not working in a way that makes it unusable" - including, for example, what you experience on eurobank with the XSS filter left alone.
My recommendation would be to use Thrawn's advice to use a separate profile for eurobank - where you ONLY access eurobank in that profile - but make sure you install NoScript in that profile and add that XSS exception. Because it's not a safe exception to have in general.
*Always* check the changelogs BEFORE updating that important software!