[
https://issues.apache.org/jira/browse/DERBY-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12542899
]
Knut Anders Hatlen commented on DERBY-2564:
-------------------------------------------
That doesn't mean we don't need to wrap the call in a privileged block, though.
A SecurityManager implementation is free to override the checkAccess(Thread)
method and perform stricter checks.
> ContextService.notifyAllActiveThreads() needs a privileged block around the
> call to Thread.interrupt()
> ------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2564
> URL: https://issues.apache.org/jira/browse/DERBY-2564
> Project: Derby
> Issue Type: Bug
> Components: Security
> Affects Versions: 10.0.2.0, 10.0.2.1, 10.1.1.0, 10.1.2.1, 10.1.3.1,
> 10.2.1.6, 10.2.2.0
> Reporter: Rick Hillegas
>
> It looks to me as though the call to interrupt() can raise a
> SecurityException. I think this may give rise to another permission that we
> need to add to our template policy file and to our security documentation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
