https://bugzilla.redhat.com/show_bug.cgi?id=1443076 --- Comment #18 from jiri vanek <jvanek@xxxxxxxxxx> --- (In reply to Severin Gehwolf from comment #17) > (In reply to jiri vanek from comment #12) > > (In reply to Severin Gehwolf from comment #11) > > > (In reply to jiri vanek from comment #3) > > > > * unlike java-1.8.0-openjdk bundled NSS is used > > > > > > Can we actually do this? I don't think so. Otherwise why would we remove > > > that code from source in the generate-source-tarball script for JDK 8? > > > Actually comparing ./jdk/src/jdk.crypto.ec/share/native/libsunec/impl from > > > JDK 9 and ./jdk/src/share/native/sun/security/ec/impl from JDK 8 yields no > > > difference for me. > > > > Tahts surprising. I did not do work on that. That means that all patches > > form 8 are upstreamed, and it is default choice in OJDK.... (see the make > > call) > > I don't understand what you are saying. Can you clarify what "That" in "That > means ..." is? Should be "system nss": USage of system nss is surprising. I did not do work on that. System nss used by ddefault means that all patches form 8 are upstreamed, and it is default choice in OJDK.... (see the call to make ) Better? Sorry. > > Originally you've said that bundled NSS is being used. That's for EC > support, right? However, I believe we cannot use a source tarball with the > internal NSS fork of openjdk included, can we? Wouldn't we need to go down a > similar path as with openjdk 8. Remove internal NSS fork from sources, use > system NSS. Or, alternatively, don't support EC. Sure, removal of the sources iss deffinitley thing to do. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx
