From: | thomas at tada(dot)se (Thomas Hallgren) |
---|---|
To: | |
Subject: | [Pljava-dev] threads left running after function end |
Date: | 2009-05-27 06:07:00 |
Message-ID: | 4A1CD884.3030208@tada.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pljava-dev |
Kris Jurka wrote:
> Without a fix to this I don't see any alternative to dropping the
> trusted version of pljava.
>
I think the easiest fix would be to prevent a trusted function from ever calling an untrusted
function. I don't think that would be too limiting and it should be easy enough to check. The
semantic would do something like this:
At the point when the SecurityManager is replaced, check if the invocation is nested. If it is,
check if the current SecurityManager is the one used by a trusted function. If so, throw an exception.
Regards,
Thomas Hallgren
From | Date | Subject | |
---|---|---|---|
Next Message | Oleg Vasylenko | 2009-06-13 08:53:19 | [Pljava-dev] How to read LargeObject with pljava? |
Previous Message | Kris Jurka | 2009-05-27 00:18:45 | [Pljava-dev] threads left running after function end |