| Wiki Markup |
|---|
Native methods are defined in Java and written in traditional languages such as C and C++ \[[JNI 2006|AA. Bibliography#JNI 06]\]. The added extensibility comes at the cost of flexibility and portability as the code no longer conforms to the policies enforced by Java. In the past, native methods were used for performing platform specific operations, interfacing with legacy library code and improving program performance \[[Bloch 2008|AA. Bibliography#Bloch 08]\]. Although this is no longer completely true --- because of poor portability, safety and (quite ironically) performance issues --- native code is still used to interface with legacy code. |
...
| Wiki Markup |
|---|
\[[Fairbanks 2007|AA. Bibliography#Fairbanks 07]\] \[[JNI 2006|AA. Bibliography#JNI 06]\] \[[Liang 1997|AA. Bibliography#Liang 97]\] \[[Macgregor 1998|AA. Bibliography#Macgregor 98]\] Section 2.2.3, Interfaces and Architectures |
| Wiki Markup |
|---|
\[[MITRE 2009|AA. Bibliography#MITRE 09]\] [CWE ID 111|http://cwe.mitre.org/data/definitions/111.html] "Direct Use of Unsafe JNI"
\[[SCG 2007|AA. Bibliography#SCG 07]\] Guideline 3-3 Define wrappers around native methods |
...
void SEC17SEC13-J. Create and sign a SignedObject before creating a SealedObjectDo not allow unauthorized construction of classes in inaccessible packages 14. Platform Security (SEC) SEC19-J. Do not rely on the default automatic signature verification provided by URLClassLoader and java.util.jar