Re:PayPal's Beautiful Demonstration of Extended Validation FUD
by nikanj on Thursday May 23, 2019 @05:59PM
(#19996441)
I'm really happy that Paypal ops is not upgrading anything just for the sake of upgrading it. At that scale, changes should be approached with extreme caution.
[ Parent
| on HN ]
Re:PayPal's Beautiful Demonstration of Extended Validation FUD
by jmgrosen on Thursday May 23, 2019 @06:29PM
(#19996658)
Well, perhaps they should upgrade it for the sake of the ~170 CVEs that have been published against Java 1.8.0_60? https://www.cvedetails.com/vulnerability-list.php?vendor_id=...
Sure, a lot of those probably don't apply to how they're using Java, but I'd bet at least a couple do.
Re:PayPal's Beautiful Demonstration of Extended Validation FUD
by sroussey on Thursday May 23, 2019 @08:11PM
(#19997292)
Vendors often backport CVEs without changing version numbers.
Re:PayPal's Beautiful Demonstration of Extended Validation FUD
by viraptor on Thursday May 23, 2019 @09:38PM
(#19997745)
Or review the details and decide that the specific issue doesn't apply to them. This actually makes sense in larger environments.
Re:PayPal's Beautiful Demonstration of Extended Validation FUD
by Rebelgecko on Thursday May 23, 2019 @06:32PM
(#19996676)
They're missing out on probably dozens of security fixes from the past 4 years. Unless they depend on buggy behavior, it is incredibly unlikely that they'll have any backwards compatibility issues, and hopefully they would have tests they could run against a newer JVM to help surface those issues.
Re:PayPal's Beautiful Demonstration of Extended Validation FUD
by yjftsjthsd-h on Thursday May 23, 2019 @07:48PM
(#19997151)
> changes should be approached with extreme caution.
It's good to make updates carefully, with full testing and a rollback plan. It is also important to actually push updates.