View Attach Info

Add new attachment

Only authorized users are allowed to upload new attachments.

This page (revision-13) was last changed on 29-May-2007 23:13 by JanneJalkanen  

This page was created on 25-Feb-2006 01:04 by 89.55.177.112

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Difference between version and

At line 45 changed one line
Note that the constructor takes an array of certificates, which can be used to verify the signatures on the permission class. Remember that {{UnresolvedPermission}}s enable the deferred loading of permission classes so that a given permission class need not be defined until necessary. __The very nature of such permission classes suggests that a more rigorous mechanism is required to ensure their authenticity. By signing a given permission class and specifying the signing requirement in the security policy, we have a foundation that can be used to assure us that the permission class respects the intentions of the root class {{java.security.Permission}} and that the implementation is not malicious.__ Of course, this assurance depends on the trust conveyed by the signature keys used to sign the class. However, without this mechanism, it would be up to the application to make this trust decision, which would be difficult, if not impossible, for the application to do.''
''Note that the constructor takes an array of certificates, which can be used to verify the signatures on the permission class. Remember that {{UnresolvedPermission}}s enable the deferred loading of permission classes so that a given permission class need not be defined until necessary. __The very nature of such permission classes suggests that a more rigorous mechanism is required to ensure their authenticity. By signing a given permission class and specifying the signing requirement in the security policy, we have a foundation that can be used to assure us that the permission class respects the intentions of the root class {{java.security.Permission}} and that the implementation is not malicious.__ Of course, this assurance depends on the trust conveyed by the signature keys used to sign the class. However, without this mechanism, it would be up to the application to make this trust decision, which would be difficult, if not impossible, for the application to do.''
Version Date Modified Size Author Changes ... Change note
13 29-May-2007 23:13 5.571 kB JanneJalkanen to previous
12 17-Jul-2006 21:51 5.449 kB Janne Jalkanen to previous | to last
11 17-Jul-2006 11:30 18.999 kB 211.53.198.25 to previous | to last
10 29-Mar-2006 10:18 5.449 kB 24.218.63.149 to previous | to last
9 29-Mar-2006 10:13 5.382 kB 24.218.63.149 to previous | to last
8 29-Mar-2006 10:13 5.352 kB 24.218.63.149 to previous | to last
7 29-Mar-2006 10:13 5.335 kB 24.218.63.149 to previous | to last
6 29-Mar-2006 10:11 5.121 kB 24.218.63.149 to previous | to last
5 29-Mar-2006 10:10 5.119 kB 24.218.63.149 to previous | to last
4 29-Mar-2006 10:09 5.118 kB 24.218.63.149 to previous | to last
3 29-Mar-2006 10:09 5.116 kB 24.218.63.149 to previous | to last
2 27-Feb-2006 07:28 0.667 kB 24.218.63.149 to previous | to last
1 25-Feb-2006 01:04 0.666 kB 89.55.177.112 to last
« This page (revision-13) was last changed on 29-May-2007 23:13 by JanneJalkanen