Re: 答复: RFR 8036779: sun.security.krb5.KdcComm interprets kdc_timeout asmsec instead of sec

On 05/15/2014 04:09 AM, Xuelei Fan wrote: The actual problem is, what if I want to use 121 seconds? It is a possible timeout value in practice. I assume you could specify it as 121000 milliseconds. :-) -- Florian Weimer / Red Hat Product Security Team

RFR 8027575: b113 causing a lot of memory allocation and regression for wls_webapp_atomics

Can someone help reviewing this SunJCE provider fix? Essentially, CipherCore class is updated to minimize memory allocation and data copying. The fix has been verified against the wls_webapp_atomics benchmark. Webrev: http://cr.openjdk.java.net/~valeriep/8027575/webrev.00/ Thanks, Valerie

RFR 8037745: Consider re-enabling PKCS11 mechanisms previously disabled due to Solaris bug 7050617

Tony, Can you please help reviewing this PKCS11 provider configuration file change? This is for removing the digest related mechs from the disabledMechanism section now that relevant native bugs have been fixed. Webrev: http://cr.openjdk.java.net/~valeriep/8037745/webrev.00/ Thanks, Valerie

Re: RFR 8037745: Consider re-enabling PKCS11 mechanisms previously disabled due to Solaris bug 7050617

Whoo Hoo. :) Looks good. Brad On 5/15/2014 4:11 PM, Valerie (Yu-Ching) Peng wrote: Tony, Can you please help reviewing this PKCS11 provider configuration file change? This is for removing the digest related mechs from the disabledMechanism section now that relevant native bugs have been fix

Re: RFR 8037745: Consider re-enabling PKCS11 mechanisms previously disabled due to Solaris bug 7050617

Looks good Tony > On May 15, 2014, at 4:11 PM, "Valerie (Yu-Ching) Peng" > wrote: > > Tony, > > Can you please help reviewing this PKCS11 provider configuration file change? > This is for removing the digest related mechs from the disabledMechanism > section now that relevant native bugs hav