Java uses code signing as a requirement for granting elevated privileges to code. Many security policies permit signed code to operate with privileges that exceed the default. For example, Java applets can escape the default sandbox restrictions when signed. Applications can use custom security policies based on code signing. ThusConsequently, users can grant explicit permissions either to a particular codebase or to all code signed by a particular signer. This approach places control of security in the hands of the user, who can choose whether to run an application with full or restricted permissions.
...
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="9f41c5205093998b-bcdf5af6-42e74d3e-95feb179-5f440fc4697101b0991da2e7"><ac:plain-text-body><![CDATA[ | [[Dormann 2008 | AA. Bibliography#Dormann 08]] |
| ]]></ac:plain-text-body></ac:structured-macro> |
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="61b33a4f304dd62d-3807a915-4b7b4937-a4499179-56549358cf4b02901f133244"><ac:plain-text-body><![CDATA[ | [[McGraw 1999 | AA. Bibliography#McGraw 99]] | Appendix C: Sign Only Privileged Code | ]]></ac:plain-text-body></ac:structured-macro> |
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="d9b00583f18235f1-c760d717-4fb744e7-946b8c17-51d9b94bc9d64b6566aa60d7"><ac:plain-text-body><![CDATA[ | [[Schneier 2000 | AA. Bibliography#Schneier 00]] |
| ]]></ac:plain-text-body></ac:structured-macro> |
...