[8u] RFR 8080462: Update SunPKCS11 provider with PKCS11 v2.40 support

[Hohensee, Paul]

As long as it's in your backlog, I'm ok with it.

Thanks,
Paul

On 11/21/19, 8:26 AM, "Martin Balao" <mbalao at redhat.com> wrote:

    Hi Paul,
    
    On 11/20/19 1:07 PM, Hohensee, Paul wrote:
    > You define TRAILER_FIELD_BC in two places which may result in future version skew (i.e., one gets updated but the other doesn't). I'd put the 11u PSSParameterSpec definition in 8u instead. That'll be an obvious overlay if 8146293 is backported, imo likely given it seems to be needed for TLS 1.3.
    
    I've thought about this when doing the backport. My understanding was
    that adding a public TRAILER_FIELD_BC field in PSSParameterSpec would
    change the API/spec without a CSR. 8146293 is likely to be backported in
    a few months for TLS 1.3 as you said. Can we leave the TRAILER_FIELD_BC
    local for now until 8146293 is backported and we then synchronize the
    constants? If you agree with this compromise solution, I'll keep this in
    my backlog.
    
    Thanks,
    Martin.-