24 Apr 15 On Java and potholes
MEMBER 80 also writes on this topic:
“It is well known that ATO potholes don’t work with the Chrome browser.
ATO euphemistically calls this fact ‘important news’.
It appears this defect is NOT going to be fixed anytime soon, so we need to get over the inconvenience and endless frustration it causes.
Despite the outstanding popularity of Chrome, ATO appears stuck using outdated technology and remains committed to Java.
The Java plug-in for web browsers relies on the cross platform plugin architecture known as NPAPI.
In September 2013, Google announced that NPAPI support in Chrome would be phased out during 2014 because ‘NPAPI’s 90s-era architecture has become a leading cause of hangs, crashes, security incidents, and code complexity.’
There’s been a well documented stream of discovered security flaws in Java.
This week’s (April 15) Java update from Oracle contains patches for at least 15 remotely exploitable flaws.
We wonder how many Java flaws will be patched next month, and the month after.
Years ago the US Dept of Homeland Security warned users to disable or uninstall Java software.
‘Java was responsible for 50 percent of all cyber attacks last year in which hackers broke into computers by exploiting software bugs, according to Kaspersky Lab.’
Can TTI ask ATO for any information regarding plans to move on from Java?
Alternatively, does ATO seriously expect its potholes to be successful when they don’t work with the world’s most widely used internet browser?
Seems strange that all our internet banking websites are apparently secure without any Java, and those banking websites deal with money transactions in real-time.
Imagine the prospects of success for any organisation trying to do business using the internet, and forcing its customers to use Java.
Failure would be assured.”
TAX COUNSEL THILINI WICKRAMASURIYA COMMENTS: We will raise this issue through the ATO Tax Practitioner Advisory Group and keep members updated through TaxVine.