JDK-6569795 : Don't present security dialog for Sun-signed binaries
- Type: Enhancement
- Component: deploy
- Sub-Component: deployment_toolkit
- Affected Version: 6u10,7
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- OS: generic,windows
- CPU: generic,x86
- Submitted: 2007-06-14
- Updated: 2010-05-05
- Resolved: 2009-07-22
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 | JDK 7 |
|---|---|
6u10Fixed  |
7 b64Fixed |
Related Reports
|
Duplicate :
|
|
|
Duplicate :
|
|
|
Duplicate :
|
|
|
Relates :
|
|
|
Relates :
|
Description
###@###.### and others recently proposed that to improve the user experience we should consider not presenting the security warning dialog boxes for Sun-signed binaries and standard extensions. Many users are scared off by such warning boxes. While there might be a slight security or publicity risk in doing this, it probably isn't any worse than what would happen if we had a security hole in a signed product which the user explicitly accepted. If we do this then we should consider instituting a program by which third parties could have their binaries signed by Sun (also suggested by ###@###.###).
Comments
|