On Wed, 21 Oct 2026 09:31:01 GMT, Hai-May Chao <[email protected]> wrote:
>> src/java.base/share/classes/sun/security/ssl/Hybrid.java line 462: >> >>> 460: this.k2 = k2; >>> 461: byte[] encoded1 = k1.getEncoded(); >>> 462: byte[] encoded2 = k2.getEncoded(); >> >> What if `k1` or `k2` is not extractable? Why is the old multiple round >> `addIKM` feature dropped? > > Now the new code fails if either component is not extractable, combines the > required TLS hybrid secret bytes, cleans the temporary encodings, and > destroys the component keys without retaining them. The multiple-addIKM() > logic was removed because JSSE now treats the built-in hybrid result as one > RAW concatenated secret. But there are cases where one or both of the secret keys cannot be extracted and you cannot get the RAW concatenated secret. This is the ultimate reason we design the multi-step `addIKM` methods in `HKDFParameterSpec`. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/33433#discussion_r4418101984
