Re: [Jessie-discuss] Client Auth Enabled, Getting "RSA Signature not available" Error

[chinmaya]

On 4/6/07, Casey Marshall <address@hidden> wrote:

On Apr 6, 2007, at 4:26 PM, chinmaya wrote:

> Hi
> I tried using client auth and I used following as the only cipher
> suite for the negotiation
> TLS_RSA_WITH_AES_128_CBC_SHA. This is causing an error on the TLS
> server side,
> giving me 'RSA signature not available error'.
>
> Isn't RSA signature impelementation part of Standarad SUN JDK?
> Is there anything I am doing wrong? Any suggestion to fix this?
>

The code is actually looking for the signature algorithm called
"TLSv1.1-RSA", which handles things a little different. This *should*
be a part of Jessie: in gnu.javax.net.ssl.provider.Jessie there is:

   put("Signature.TLSv1.1-RSA", SSLRSASignatureImpl.class.getName());
   put("Alg.Alias.Signature.TLSv1-RSA", "TLSv1.1-RSA");
   put("Alg.Alias.Signature.SSLv3-RSA ", "TLSv1.1-RSA");

And the class SSLRSASignatureImpl implements this. If you're
installing the Jessie provider properly, this should work.

Yup the is exactly like this, but it still does not work. 
Well, point to be noted is that, I have one-more provider being used in the same JVM.
But I have added Jesse at position one

-- code --
java.security.Security.insertProvider(new Jessie(), 1);
java.security.Security.insertPovider(new BouncyCastle(), 2).
-- code --

Also while creating SSLContext I explicitly specify Jessie as the provider.

-- code --
Provider provider = new Jessie();
ctx = SSLContext.getInstance("TLS", provider)
-- code --



I have put some debugs at (ServerHandshake.java:1249), the code
engine.session().suite.signatureAlgorithm().toString() is returning RSA as the string, so basically the call which is failing is 
java.security.Signature.getInstance("RSA").


Any clues to proceed further to fix this issue?



thank you 
chinmaya