Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: v_borchert@despammed.com (Volker Borchert) Newsgroups: comp.lang.java.programmer Subject: Re: JDK 1.8.0_131 Date: 24 Apr 2017 18:00:07 GMT Organization: Private site at Eddersheim, Germany Lines: 25 Distribution: world Message-ID: References: X-Trace: individual.net kMCWPX/H7KblNhs1rDaVSgkyywBZ9BO7Km9mZWWxs4LSDjBmwj Cancel-Lock: sha1:O7T6StXMf/+1TQO231FMOjeI4zU= Xref: csiph.com comp.lang.java.programmer:36525 Eric Sosman wrote: > On 4/24/2017 8:43 AM, omegajunior wrote: > > Roedy Green Wrote in message: > >> JDK 1.8.0_131 is out > >> > > > > Oh, bloody hell, what is it this time? I just got through testing > > all my applications with 1.8.0_121. There must be a faster > > way. > > To answer "What is it this time?" begin by studying the release > notes. Sometimes the study's answers are less than comprehensive > (release notes can be downright coy when discussing security issues), > but that's where you should start. And it seems to be more often than not that the security fixes only apply to Java-in-the-browser causing sandbox escapes and do not affect standalone applications at all, so that you might even be able to completely ignore them unless you have customers who are paranoid and stubborn at the same time. -- "I'm a doctor, not a mechanic." Dr Leonard McCoy "I'm a mechanic, not a doctor." Volker Borchert