The basic idea is as follows: Any Web site that runs JavaScript code that makes use of JNEXT, will have to sign that code with its private key, and make it's corresponding X509 certificate available for download by the JNEXT client. The JNEXT plugin will verify that the JavaScript code matches the signature, using the Web site certificate and the locally stored root certificate of the CA that issued the Web site certificate.
If the root certificate of the Certificate Authority, the Web site certificate, the JavaScript code and the JavaScript code signature are inconsistent, then JNEXT will not allow the JavaScript code from that page access to native code via JNEXT extensions.
[ add comment ] ( 3 views ) | permalink |




( 3 / 61 )
Calendar



