JDK-6611379 : LiveConnect security model update
- Type: Bug
- Component: deploy
- Sub-Component: plugin
- Affected Version: 6u5
- Priority: P2
- Status: Closed
- Resolution: Duplicate
- OS: generic
- CPU: generic
- Submitted: 2007-09-30
- Updated: 2010-04-04
- Resolved: 2007-10-31
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 6 |
|---|
6u10Resolved  |
Related Reports
|
Duplicate :
|
Description
Revisit the new LiveConnect security implementation and add support for correctly granting permissions. During JavaScript-to-Java calls, the JavaScript code should effectively be treated as an unsigned applet originating from the document base, and receive permission to connect back to the host from which the HTML document came. Unsigned Java applets should receive permission to connect to the code base as usual. If the applet is unsigned, and the document base is not the same as the code base, the intersection of these permissions should imply that JavaScript-to-Java calls should not be able to connect to any host on the network. Currently the code grants permissions to connect to the code base and ignores the document base for calls originating from JavaScript, which is not correct.
Comments
|