Re: Re: Re: Re: Perl & Java -- Can they keep a secret?

It still requires the provider's presence... and it is my understanding that the sun provider is the only one included in the core Java dist.

My code doesn't have bugs, it just develops random features.

Flame

Comment on Re: Re: Re: Re: Perl & Java -- Can they keep a secret?

Replies are listed 'Best First'.
Re: Re: Re: Re: Re: Perl & Java -- Can they keep a secret? by hossman (Prior) on Nov 18, 2003 at 07:41 UTC
I don't think so. I haven't dealt with crypto providers much, but as i understand it the whole point of the two different "getInstance" methods is that in one case you are saying "get me an instance from whichever provider is configured in my JVM for "foo". In the other case you are saying "get me an instace from this provider, right here, this one, the one i'm passing you" -- all you have to do is make sure you have a constructed Provider object. Even if I'm wrong, you can still modify the security providers list at run time... that's what Security.addProvider and Security.insertProviderAt are for.	[reply]

Replies are listed 'Best First'.

Re: Re: Re: Re: Re: Perl & Java -- Can they keep a secret?
by hossman (Prior) on Nov 18, 2003 at 07:41 UTC

I don't think so.

I haven't dealt with crypto providers much, but as i understand it the whole point of the two different "getInstance" methods is that in one case you are saying "get me an instance from whichever provider is configured in my JVM for "foo". In the other case you are saying "get me an instace from this provider, right here, this one, the one i'm passing you" -- all you have to do is make sure you have a constructed Provider object.

Even if I'm wrong, you can still modify the security providers list at run time... that's what Security.addProvider and Security.insertProviderAt are for.

[reply]