As there is a preMaster, may not need the debug-only
debugProtocolVersion class field. It can be extracted from preMaster in
the print() implementation.
Xuelei
On 11/5/2016 6:17 AM, Bradford Wetmore wrote:
https://bugs.openjdk.java.net/browse/JDK-8169229
http://cr.openjdk.java.net/~wetmore/
I didn't see anything majorly different in what I looked at earlier, I
didn't check java.security or the test case.
CryptoLevel.java
49: Your usage mentions only unlimited|limited. Do you want to include
a check for that?
JceSecurity.java
300: Indention pr
Do you know if the problem of obtaining TGT session key on Windows from LSA
credential cache is resolved (see snippet below)? Microsoft has not been able
to provide any guidance on steps to make it work. These steps below haven’t
helped:
* Turn off UAC
* Remove Service Account for appli
Hi all,
I discovered that for Java 9, the following page is not updated for the new
hashing algorithms:
http://download.java.net/java/jdk9/docs/technotes/guides/security/StandardNames.html
I don't know whether it is on your to do list, if it is already an item
then just ignore this email.
If I ca
https://bugs.openjdk.java.net/browse/JDK-8169229
http://cr.openjdk.java.net/~wetmore/8169229/webrev.00/
Please review this minor bug fix. Our RSAClientKeyExchange isn't
properly outputing the RSA PreMasterSecret field.
Thanks,
Brad
Hi,
changes to SignatureFileVerifier in 9+142 has some startup implications,
and a small
cleanup to avoid some trivial regexes etc reduces number of classes
initialized in affected
startup tests by 61, undoing most of the observed regression.
Webrev: http://cr.openjdk.java.net/~redestad/81689
* SecureRandom
131 * If this attribute is not set or is "false", this class will instead
132 * synchronize access to each of the methods of the {@code
SecureRandomSpi}
133 * implementation.
Not all of the methods are synchronized - engineGetParameters is not,
for example. I think to avo
Build changes look ok to me.
/Erik
On 2016-11-04 14:42, Seán Coffey wrote:
Looking to push this enhancement to jdk8u. The change introduces the
new Security property which was brought into JDK 9 via JDK-8061842.
The code differs in that jar files continue to be used and backwards
compatibil
Looking to push this enhancement to jdk8u. The change introduces the new
Security property which was brought into JDK 9 via JDK-8061842.
The code differs in that jar files continue to be used and backwards
compatibility is maintained. If the new security property is not defined
and the policy
