In terms of tone, I wouldn't hold this up as a good example - it distracts from any legitimate argument the writer may or may not have.
In terms of tone, I wouldn't hold this up as a good example - it distracts from any legitimate argument the writer may or may not have.
If I was an Oracle customer (which I will never, ever be) I would appreciate the honesty. This honesty enables me to make purchase decisions as well, better than megabytes of legalese would have. In this case it's not a really surprising attitude given the company, but I really wish more vendors would be as open about the nature of their intended relationship with their customers.
Fair point. And a hint to everyone still hanging on to oracle Databases.
One of the best lines is this here:
> Q. What does Oracle do if there is an actual security vulnerability?
> (...) if there is an actual security vulnerability, we will fix it.
Sure, the question is 'when', not so much 'if' customers have payed a hell of a lot money to get this straight.
If you are by nature arrogant, insulting, and condescending, then no, you can't.
Interesting that all the reasons she cites for why she thinks trying to reverse-engineer Oracle products is a bad idea are the same exact reasons why more and more administrators with any sense in security are switching to open-source software and have been for the last decade or so. Being able to inspect the code yourself (or hire someone to do it for you) is apparently important enough to a sufficiently-large population for Oracle to whine about it.