[jira] Created: (RIVER-169) allow result caching in Security.verifyCodebaseIntegrity

["Bob Scheifler (JIRA)" <ji...@apache.org>]

allow result caching in Security.verifyCodebaseIntegrity
--------------------------------------------------------

                 Key: RIVER-169
                 URL: https://issues.apache.org/jira/browse/RIVER-169
             Project: River
          Issue Type: Improvement
          Components: net_jini_security
    Affects Versions: jtsk_2.0
            Reporter: Bob Scheifler
            Priority: Minor


Bugtraq ID [6293073|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6293073]

The spec for Security.verifyCodebaseIntegrity permits caching of verifier instances, but does not permit caching of verification results. In contrast, the spec for ClassLoading does permit caching. To the extent that most calls to Security.verifyCodebaseIntegrity originate from ClassLoading, perhaps it doesn't matter where the caching happens, but it would seem more consistent to allow it in both. A minor note: the ClassLoading spec seems to be written to only allow caching at the granularity of a codebase, rather than at the granularity of a URL. There doesn't seem to be a reason to disallow the latter in the Security spec.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.