hg: jdk7/tl/jdk: 6975866: api/org_ietf/jgss/GSSContext/index.html#wrapUnwrapIOTest started to fail since jdk7 b102

2010-12-16 Thread weijun . wang
Changeset: 1f0f0737f04e Author:weijun Date: 2010-12-17 11:03 +0800 URL: http://hg.openjdk.java.net/jdk7/tl/jdk/rev/1f0f0737f04e 6975866: api/org_ietf/jgss/GSSContext/index.html#wrapUnwrapIOTest started to fail since jdk7 b102 Reviewed-by: valeriep ! src/share/classes/sun/security/

Re: Please Review: required security algorithms for Java SE 7 implementations

2010-12-16 Thread Xuelei Fan
On 12/17/2010 12:07 PM, Brad Wetmore wrote: >> Brad, can you comment on the RFC 5746 support? Do you think we should >> make the TLS_EMPTY_RENEGOTIATION_INFO_SCSV CipherSuite a requirement of >> all Java 7 TLS 1.0 implementations? > > That's an excellent question. The RFC has been out less than a

Re: Please Review: required security algorithms for Java SE 7 implementations

2010-12-16 Thread Brad Wetmore
I think the TLSv1 cipher suite list is effectively much longer. Correct? Yes, but only TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA is mandatory. See section 9 of RFC 2246: http://www.ietf.org/rfc/rfc2246.txt I think it's prudent to require TLS_RSA_WITH_AES_128_CBC_SHA as well (which is mandatory per R

Re: Please Review: required security algorithms for Java SE 7 implementations

2010-12-16 Thread Brad Wetmore
Hi Florian, SecureRandom is still underspecified. Most applications want an algorithm which cannot block and will not wait for true, physical randomness to arrive. If such applications accidentally use a blocking generator (such as /dev/random on Linux without special hardware support), then t

Re: Please Review: required security algorithms for Java SE 7 implementations

2010-12-16 Thread Dr Andrew John Hughes
On 16 December 2010 19:05, Sean Mullan wrote: > Right, but there are ECC patents that each vendor needs to consider on their > own. Since these are requirements that all Java SE 7 implementations would > have to support, it did not seem appropriate to make any ECC algorithms > required or in gener

hg: jdk7/tl/jaxws: 7006853: Integrate JAX-WS 2.2.2 RI into JDK 7

2010-12-16 Thread kelly . ohair
Changeset: aca101db2361 Author:ohair Date: 2010-12-16 13:14 -0800 URL: http://hg.openjdk.java.net/jdk7/tl/jaxws/rev/aca101db2361 7006853: Integrate JAX-WS 2.2.2 RI into JDK 7 Reviewed-by: ramap ! jaxws.properties

hg: jdk7/tl/jaxp: 7007257: jaxp 1.4.5 jdk7 1st integration

2010-12-16 Thread kelly . ohair
Changeset: 63190d0ca619 Author:ohair Date: 2010-12-16 13:10 -0800 URL: http://hg.openjdk.java.net/jdk7/tl/jaxp/rev/63190d0ca619 7007257: jaxp 1.4.5 jdk7 1st integration Reviewed-by: joehw ! jaxp.properties

Re: Please Review: required security algorithms for Java SE 7 implementations

2010-12-16 Thread Sean Mullan
Right, but there are ECC patents that each vendor needs to consider on their own. Since these are requirements that all Java SE 7 implementations would have to support, it did not seem appropriate to make any ECC algorithms required or in general any algorithm that may be protected by patents.

Re: Please Review: required security algorithms for Java SE 7 implementations

2010-12-16 Thread Tomas Gustavsson
I don't see any ECC algorithms. These are in wide use today to say the least. And will be so even more tomorrow (i.e. when Java SE 7 is out you can not live without it). Regards, Tomas On 12/15/2010 04:11 PM, Sean Mullan wrote: Hello, Currently, the Java security APIs do not specify algori

Re: Please Review: required security algorithms for Java SE 7 implementations

2010-12-16 Thread Sean Mullan
On 12/16/2010 11:30 AM, Florian Weimer wrote: * Sean Mullan: On 12/15/10 10:38 AM, Florian Weimer wrote: * Sean Mullan: Please review the following list: http://cr.openjdk.java.net/~mullan/5001004/review.00/StandardNames.html#impl "SHA-1" or "SHA1"? (Our code uses "SHA1" for some reason,

Re: Please Review: required security algorithms for Java SE 7 implementations

2010-12-16 Thread Florian Weimer
* Sean Mullan: > On 12/15/10 10:38 AM, Florian Weimer wrote: >> * Sean Mullan: >> >>> Please review the following list: >>> http://cr.openjdk.java.net/~mullan/5001004/review.00/StandardNames.html#impl >> >> "SHA-1" or "SHA1"? (Our code uses "SHA1" for some reason, perhaps for >> consistency with

hg: jdk7/tl/jdk: 6980447: Rhino JavaScript engine code in jdk-7 has to updated with the latest code from Rhino 1.7R3.

2010-12-16 Thread sundararajan . a
Changeset: e67a399dd4ad Author:sundar Date: 2010-12-16 20:52 +0530 URL: http://hg.openjdk.java.net/jdk7/tl/jdk/rev/e67a399dd4ad 6980447: Rhino JavaScript engine code in jdk-7 has to updated with the latest code from Rhino 1.7R3. Summary: Updating Rhino javascript engine with versio