Home > Computing > Oracle takes down CSO’s chastising blog post…

Oracle takes down CSO’s chastising blog post on home-security testing

If the last few years have taught us anything about the nature of digital security, it’s that nothing is airtight. Whether you look to Edward Snowden absconding with the NSA’s secretive files, Sony having its servers’ contents dumped all over the floor or indeed, Hacking Team itself being hacked, it’s clear everyone and everything is vulnerable.

Perhaps that’s why a lot of Oracle software users have been trying to find flaws in its software, something that the chief security officer at the company, Mary Davidson, isn’t happy with. So much so, in fact, that she penned a sarcastic, chastising blog post over the weekend that pointed out not only were people breaking their license agreement by reverse engineering Oracle programs, but that they were wasting their time too.

“I’ve been writing a lot of letters to customers that start with ‘hi, howzit, aloha,’ but end with ‘please comply with your license agreement and stop reverse engineering our code, already,'” she said in the now deleted post (via Ars Technica).

Related: Supreme Court declines to hear Oracle’s copyright case against Google

She went on to poke fun at those using automated tools to scan Oracle software for flaws, suggesting that not only that those tools’ reports do not — as she is concerned — quantify an actual potential exploit, but that they are roping someone else into breaking their license agreement too.

“Oh, and we require customers/consultants to destroy the results of such reverse engineering and confirm they have done so,” she said.

Her reasoning for this attack on customers, who she seems to believe are either misguided or want to catch Oracle out, is that she doesn’t want to send out more sternly worded letters telling people to stop. She also reiterated that third-party tools and analyzers don’t do a good job of looking at Oracle code anyway.

“I do not need you to analyze the code since we already do that.”

Do you think those sending in reports of Oracle bugs are doing it because they want the praise for finding a flaw, as Davison seems to think, or does this suggest a growing climate of more security concious software users?