Mailing-List: contact commits-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Message-ID: <29996233.1166012121645.JavaMail.jira@brutus>
Date: Wed, 13 Dec 2006 04:15:21 -0800 (PST)
From: "Alexey Varlamov (JIRA)" <jira@apache.org>
To: commits@harmony.apache.org
Subject: [jira] Closed: (HARMONY-2301) [luni] flawed
 SecurityManager.checkPackageAccess() impl
In-Reply-To: <5896814.1164364141918.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/HARMONY-2301?page=all ]

Alexey Varlamov closed HARMONY-2301.
------------------------------------

    Resolution: Fixed

I believe this is finally fixed.

> [luni] flawed SecurityManager.checkPackageAccess() impl
> -------------------------------------------------------
>
>                 Key: HARMONY-2301
>                 URL: http://issues.apache.org/jira/browse/HARMONY-2301
>             Project: Harmony
>          Issue Type: Bug
>          Components: Classlib
>            Reporter: Alexey Varlamov
>         Assigned To: Alexey Varlamov
>         Attachments: fix2301.diff, test2301.diff
>
>
> There are several problems in the current implementation of j.l.SecurityManager.checkPackageAccess() method:
> 1) Dead-end caching of "package.access" property on the first use;
> 2) Thread-unsafe parsing to array of names: concurrent threads may fail with NPE accessing partially-filled array.
> 3) Incomplete name matching procedure, only works for subpackges.

-- 
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