In sun.security.x509.AVA, there are 3 places where
} else if (debug != null && Debug.isOn("ava")) {
is checked. If it's true, string representations of an AVA object uses
\HEX dump for non-printable characters. This is nice for debugging
purposes, but the output of a method depending on a de
On 09/16/2011 01:45 PM, Xuelei Fan wrote:
My first impression about the fix:
1. Do you want to update getKeys() comments about isInitiator value?
OK. I'll simply remove the "(in JAAS words, isInitiator=true and
storeKey=true)" line.
2. It seems that when isInitiator is true, getKeys() sh
My first impression about the fix:
1. Do you want to update getKeys() comments about isInitiator value?
2. It seems that when isInitiator is true, getKeys() should throw exception if
the state is not OK, right? If so, it looks like that the update of getKeys()
will not throw ISE if the state is
Hi All
Code changes at
http://cr.openjdk.java.net/~weijun/7089889/webrev.00/
KrbAsReqBuilder maintains a state enforcement: at the beginning it's
INIT, after doing an AS-REQ it's OK, and we used to only allow getKeys()
to be called when the state is OK. Now if an acceptor has
isInitiator=
On Aug 25, 2011, at 8:00 PM, Sebastian Sickelmann wrote:
> Am 26.08.2011 00:24, schrieb Sebastian Sickelmann:
>> Am 26.08.2011 00:03, schrieb Sebastian Sickelmann:
>>> I have found more places in jdk source where an Exception has a private
>>> cause field.
>>>
>>> share/classes/javax/management/r
Hi Max:
In Java plugin, we display the detail information of certificate in both
Java Control panel and certificate dialog box from security warning, we
also extract entension from certificate to make sure they are valid to use.
Currently we are parsing the X509Certificate object to extract a
Changeset: 9281d65f911a
Author:michaelm
Date: 2011-09-15 13:50 +0100
URL: http://hg.openjdk.java.net/jdk8/tl/jdk/rev/9281d65f911a
7073491: -Dsun.net.maxDatagramSockets=1 does not work correctly with system.gc()
Reviewed-by: ngmr
! src/share/classes/java/net/AbstractPlainDatagramSoc
On 09/14/11 09:30 PM, Valerie (Yu-Ching) Peng wrote:
>
> As long as Solaris supports both key formats after fixing 6830224, then it'd
> be
> fine, I guess.
>
> Oh, are you gonna change the synopsis to describe the cause of the problem?
> I'd
> also prefer it that way.
I've fixed that:
http:
