# Re: Security.addProvider() not allowed in applets?

Jan Luehe (Jan.Luehe@Eng)
Tue, 31 Mar 1998 14:40:38 -0800 (PST)

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Charlie Lai: "Re: Again: Trusted applets in generic browsers !"
- Previous message: Charlie Lai: "Re: Signed applets"
- Maybe in reply to: Mike Hanafin: "Security.addProvider() not allowed in applets?"

    Date: Tue, 31 Mar 1998 14:40:38 -0800 (PST)

    From: Jan Luehe <Jan.Luehe@Eng>

    Subject: Re: Security.addProvider() not allowed in applets?

    To: java-security@web2.javasoft.com, mike@baltimore.ie

Mike:

> This question may be more Netscape related but still:
>
> While I know that Security.addProvider() isn't normally allowed from applets
> (needing access to java.home for one), surely it should be possible withing
> Communicator by using the Capabilities API to grant privileges to your applet.
> My understanding was that applets could be allowed to do everything that
> applications can - am I mistaken here? It doesn't make sense that if I trust
> an applet implicitly it is then prevented from doing something an application
> can...

In JDK 1.2, you need to configure your policy file if you want to give
applets permissions to add/insert providers.

Please check

http://webwork.eng/products/jdk/1.2/docs/guide/security/CryptoSpec.html#Security

on how to do that.

Thanks,

Jan

- Next message: Charlie Lai: "Re: Again: Trusted applets in generic browsers !"
- Previous message: Charlie Lai: "Re: Signed applets"
- Maybe in reply to: Mike Hanafin: "Security.addProvider() not allowed in applets?"