...
Users often assume that Java class files obtained from a trustworthy source will be conforming and, consequently, safe for execution. This belief can erroneously lead them to see bytecode verification as a superfluous activity for such classes. Consequently, they could disable bytecode verification, undermining Java's safety and security guarantees. But the bytecode verifier must not be suppressed.
Noncompliant Code Example
...
| Code Block | ||
|---|---|---|
| ||
java -Xverify:all ApplicationName |
Exceptions
ENV09-EX1EX0: On Java 2 systems, the primordial class loader is permitted to omit bytecode verification of classes loaded from the boot class path. These system classes are protected through platform and file system protections, rather than by the bytecode verification process.
...
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="6193a8d2cbedaa40-6261cb1e-45c6453a-b884bf69-45fc1bbf2e6e99e02b561293"><ac:plain-text-body><![CDATA[ | [[Oaks 2001 | AA. Bibliography#Oaks 01]] | The Bytecode Verifier | ]]></ac:plain-text-body></ac:structured-macro> |
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="d80fd91e55519d19-4a6f65f9-4c2347a2-a961844e-eb0a6065a5d5cffe8ced0e14"><ac:plain-text-body><![CDATA[ | [[Pistoia 2004 | AA. Bibliography#Pistoia 04]] | Section 7.3, The Class File Verifier | ]]></ac:plain-text-body></ac:structured-macro> |
...