Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.java.programmer > #35819
| From | Eric Sosman <esosman@comcast-dot-net.invalid> |
|---|---|
| Newsgroups | comp.lang.java.programmer |
| Subject | Re: new JDK 1.8.0_112 |
| Date | 2016-10-19 09:28 -0400 |
| Organization | A noiseless patient Spider |
| Message-ID | <nu7sds$g4a$1@dont-email.me> (permalink) |
| References | <d68d0c9ub7i9gc66m8p3sduv44nbvpmhn1@4ax.com> <801e31b0-8a86-4276-952c-45c44a0d5d81@googlegroups.com> <nu7oeb$229$1@dont-email.me> <ce1f7a97-eab7-4314-b635-917c5eedaefa@googlegroups.com> |
On 10/19/2016 8:33 AM, Eric Douglas wrote:
> On Wednesday, October 19, 2016 at 8:20:56 AM UTC-4, Eric Sosman wrote:
>> From Oracle's download page:
>>
>> "Java SE 8u111 includes important security fixes. Oracle
>> strongly recommends that all Java SE 8 users upgrade to this
>> release. Java SE 8u112 is a patch-set update, including all of
>> 8u111 plus additional features (described in the release
>> notes). "
>>
>> Also, a few links from that same page:
>>
>> http://www.oracle.com/technetwork/java/javase/8u111-relnotes-3124969.html
>>
>> http://www.oracle.com/technetwork/java/javase/8u112-relnotes-3124973.html
>>
>> Will there be anything else, Sir?
>
> It just seems odd...why they call them both public release, and they list the lower number first for downloads, and the higher numbered one crashed our system last time...
> Now I guess we want to test both versions, since higher should be better (if it doesn't crash the system?) and the first bug fix listed says they made it faster?
> Version 122 seems to work, maybe we should run the 'early release' versions in production!?
Which to adopt for production is, of course, your call and not mine.
If the choice were mine, though, I doubt I'd opt for 122 -- 112, maybe,
but 122 would seem just a wee bit rash. :)
112's list of bug fixes is considerably longer than 111's, but I'm
not in a position to say how important that might be in your situation.
If you're using SecureRandom.PKCS11 you'll have an easier time with 111
than with 112, but there may be other countervailing considerations.
If you don't need the bug fixes *and* you run only apps and applets
that are trusted, you might be able to stick with what you're using
now. But if anyone in your organization runs apps or applets downloaded
from untrusted sources, the fixes for seven CVE's may be of interest ...
--
esosman@comcast-dot-net.invalid
"Don't be afraid of work. Make work afraid of you." -- TLM
Back to comp.lang.java.programmer | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
new JDK 1.8.0_112 Roedy Green <inquiry@mindprod.com> - 2016-10-18 15:24 -0700
Re: new JDK 1.8.0_112 Eric Douglas <e.d.programmer@gmail.com> - 2016-10-19 05:03 -0700
Re: new JDK 1.8.0_112 Eric Sosman <esosman@comcast-dot-net.invalid> - 2016-10-19 08:20 -0400
Re: new JDK 1.8.0_112 Eric Douglas <e.d.programmer@gmail.com> - 2016-10-19 05:33 -0700
Re: new JDK 1.8.0_112 Eric Sosman <esosman@comcast-dot-net.invalid> - 2016-10-19 09:28 -0400
Re: new JDK 1.8.0_112 Eric Douglas <e.d.programmer@gmail.com> - 2016-10-19 07:14 -0700
Re: new JDK 1.8.0_112 Arne Vajhøj <arne@vajhoej.dk> - 2016-10-19 21:26 -0400
csiph-web