All of that changed this year, when I discovered that Oracle has finally released a series of supported instructions to do exactly that: update the Java JDK embedded in an Oracle Home directory as a part of the normal quarterly patch set update cycle.įirst Oracle layed out an overview of supported update paths in My Oracle Support (MOS) Doc ID 1449674.1 (no longer available), which stated essentially that it is ok to make minor release updates to the embedded JDK, say from Java 7 update 181 to Java 7 update 191, but not major release updates as from Java 7 to Java 8. We started to get dinged frequently on security scans for not having the latest Java versions installed. Over the last year or two however, the corporate security types decided that they didn’t care about all that, or the fact that Oracle didn’t offer separate patches. It is a fair question given how security conscious we are these days, and my automatic answer – up until now – was always, “It is embedded as-is by Oracle and I can’t alter it without voiding our support agreement,” or, “it doesn’t support any networked services or user facing functionality, only admin-level configuration tools, so it isn’t really a risk.” Updated on to update links and references at My Oracle Support.Įvery once in a while over the years I have been asked, “Why don’t you patch the Java JDK included in an Oracle Home directory?”
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |