On Tue, 18 May 2021 10:37:21 GMT, Patrick Concannon
wrote:
> Hi,
>
> Could someone please review my code for updating the code in the `java.util`
> package to make use of the `instanceof` pattern variable?
>
> Kind regards,
> Patrick
Because we still make jdk11-compatible test-release java.u
On 10/08/2014 05:38 AM, Peter Levart wrote:
http://cr.openjdk.java.net/~plevart/jdk9-dev/AtomicFieldUpdater.AccessChecks/AnonClassPerCclass/AtomicIntegerFieldUpdater.java
Paul Sandoz has been working on VarHandles (like MethodHandles)
for similar purposes. Possibly even the same purposes.
Se
Thanks for the careful explanation. In short, the current checks
reject reasonable EE usages, which can lead users to widen
permissions, which can lead to less overall security.
The solution to inspect other caller frames seems OK to me.
But acceptance into OpenJDK requires approval from securit
Peter: Thanks very much for attacking the shocking impact/complexity
of getting a few seed bits.
On 06/25/2014 01:41 PM, Peter Levart wrote:
Peeking around in the sun.security.provider package, I found there already is a
minimal internal infrastructure for obtaining random seed. It's encapsula
On 10/02/2013 12:29 PM, Martin Buchholz wrote:
FutureTask.cancel(true) invokes thread.interrupt on the thread (if any)
currently running the task.
This should succeed even if modifyThread permission is denied by the security
manager.
We haven't interpreted "should" in this way in the past here
On 04/15/10 18:34, Martin Buchholz wrote:
People are using Atomic field updaters to update fields in classes in other
classloaders.
I think the policy on this awaits interpretation by Jeff
or other members of security team. FWIW, my take is that
if users know that they may cross class loaders
