db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <derby-...@db.apache.org>
Subject [jira] Created: (DERBY-467) Restrict direct access to priviliged blocks from application code
Date Wed, 20 Jul 2005 20:21:46 GMT
Restrict direct access to priviliged blocks from application code
-----------------------------------------------------------------

         Key: DERBY-467
         URL: http://issues.apache.org/jira/browse/DERBY-467
     Project: Derby
        Type: Bug
  Components: Security  
    Versions: 10.1.1.0, 10.2.0.0    
    Reporter: Daniel John Debrunner
 Assigned to: Daniel John Debrunner 


In looking at the privilged blocks in Derby  several are accessible from application code,
either as in public/protected methods and public classes. The fix for this includes:

- making packages in the jar files sealed wherever possible
- making classes and methods with privilged blocks  as private as possible (private or package
for methods, package for classes)

As Derby moves towards a more client server approach (e.g. see grant/revoke) I started to
perform a security analysis of the priviliged blocks, but realised it would be easier if I
fixed the obvious problems first.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message