This bug follows up with JDK-8032276. Although applet is blocked finally, the information on first dialog is not correct.
Steps to reproduce it:
1) import cert into signer CA from:
http://sqeweb.us.oracle.com/deployment2/sheldon/webCases/VerifyTerms/tmpcert/self.valid.cert
2) Launch the applet without Permissions Attribute from
http://sqeweb.us.oracle.com/deployment2/sheldon/webCases/VerifyTerms/html/CheckResource.html
3) If the signed security warning dialog with the yellow warning area shows up, bug is reproducible.
It should be a dialog stating that it's blocked from security settings. And the information on yellow warning area is not correct, since this application is blocked now rather than blocked in future.
Steps to reproduce it:
1) import cert into signer CA from:
http://sqeweb.us.oracle.com/deployment2/sheldon/webCases/VerifyTerms/tmpcert/self.valid.cert
2) Launch the applet without Permissions Attribute from
http://sqeweb.us.oracle.com/deployment2/sheldon/webCases/VerifyTerms/html/CheckResource.html
3) If the signed security warning dialog with the yellow warning area shows up, bug is reproducible.
It should be a dialog stating that it's blocked from security settings. And the information on yellow warning area is not correct, since this application is blocked now rather than blocked in future.
- duplicates
-
JDK-8037526 For signed jars without manifest "Permissions", there is still security warning dialog before Application Error (Or blocked) Dialog.
-
- Closed
-
- relates to
-
-
- Closed
-