SSL and JWS Sandbox
843802Jan 23 2002 — edited Feb 2 2002I saw references herein and at the vamphq faq that you could not run SSL from within the JWS Sandbox. I'm guessing that this is a JDK1.3 issue because, while in the sandbox, you cannot install the security provider. Therefore, this issue should go away with JDK1.4 since the default security provider is pre-installed, and SSL from inside the JWS Sandbox should work. Comments?
However, you cannot use a proxy server because the proxy server is not the download host. So for proxy server cases (which is quite often), you would still need "all permissions". Any way around this?
And, of course, just to chime in, JWS does need granular permissions so you can request just, for example, java.net.SocketPermission, and not all permissions. As others have noted, a security box that declares an application is requesting unrestricted access makes an end-user very wary. Of course, end-users install applications all the time that have unrestricted access, but since they usually aren't warned, they don't think about it. Telling the user is, in theory, a good feature. But if we tell them, we need to be able to ask for much less.