For some of the serializable classes, during obfuscation the private field names will have changed. Looking at the current jar file:

com.sun.net.ssl.internal.ssl.JS_KeyPairGenerator
    private String algorithm;
    private int keyPairState;

    /* Ignoring the static INITIALIZED/NOT_INITIALIZED fields */

Dumping the contents of an obfuscated jar.

-------------------------------
Fields (count = 6)

*IGNORING the protected and serialVersionUID*

3) Field: Name (45): a Type (39): Ljava/lang/String; Access Flags: pr
ivate
Attributes: Attributes (count = 0)

4) Field: Name (46): b Type (35): I Access Flags: private
Attributes: Attributes (count = 0)

*IGNORING the final static ints.*
-------------------------

And in a *non-obfuscated*

-------------------------
3) Field: Name (48): algorithm Type (49): Ljava/lang/String; Access F
lags: private
Attributes: Attributes (count = 0)

4) Field: Name (50): keyPairState Type (51): I Access Flags: private
Attributes: Attributes (count = 0)
-------------------------

Currently, Dasho is renaming the first variable as "a", second as "b" but that can't be guaranteed. If anyone reorders/adds any new fields, this will break quite nicely! :)

For compatibity reasons in tiger, we should look at what the fields were renamed to, rename the variables to this, and then include the classes unconditionally.

As of 3/14/03, the classes that have private members include:

com.sun.net.ssl.internal.ssl.JS_KeyFactory
    private String transformation;

com.sun.net.ssl.internal.ssl.JS_KeyPairGenerator
    private String algorithm;
    private int keyPairState;

com.sun.net.ssl.internal.ssl.JS_Signature
    private String keyAlgorithm;
    private boolean signing;

###@###.### 2003-03-14