2014/1/23 12:58 -0800, [email protected]: > 2014/1/22 16:54 -0800, Andrew Haley <[email protected]>: >> On 01/23/2014 12:21 AM, [email protected] wrote: >>> 2014/1/21 21:04 -0800, Andrew Haley <[email protected]>: >>>> There are some JCK failures in the draft RI. >>>> >>>> ... >>>> >>>> Failures: >>>> api/org_ietf/jgss/GSSContext/* (14 total): >>>> all caused by missing support for AES256, so I'd say it's expected >>> >>> Hrm, maybe you expect them but they're not known failures. Could you >>> please send me (privately) the relevant .jtr file and also a description >>> of the system on which you're running the JCK (OS, kernel version, >>> hardware, etc.)? I'll forward that information on to the JCK team for >>> analysis. >> >> OK. > > The JCK team is still looking into the AES256 issue. We don't think > these tests should be failing.
These tests will pass if you enable AES256 encryption [1], as you probably know. - Mark [1] http://docs.oracle.com/javase/7/docs/technotes/guides/security/jgss/jgss-features.html
