gcj-security and some issues

Bryce McKinlay mckinlay@redhat.com
Wed Apr 28 23:05:00 GMT 2004


Tom Tromey wrote:
>>>>>>"Michael" == Michael Koch <konqueror@gmx.de> writes:
>>>>>>>>>>>>>>>>>>I *think* this would be all that is needed to implement the
>>>AcessController. I think this could be done anytime, and as soon as
>>>gcj applies Codesoures to its classes one can start testing the
>>>implemention.
>>>>>>>>Michael> Your analysis seems quite correct BUT the biggest problem yet
>Michael> is that StackTrace's implementation is just crap. The
>Michael> solution you provided is nearly the same I did here some days
>Michael> ago until I found out that StrackTrace is so dumb (it calls
>Michael> external apps to analyze the stack ...). Bryce McKinley is
>Michael> working on a better solution. The base has to be built first
>Michael> before we can build the roof.
>>Does Bryce's patch address this? 
>
Yes, the only time an external program is called is to obtain the source 
line info for debugging stack traces. No external programs are needed 
for security checks. And no heap allocations either, if getContext() etc 
is implemented natively.
Regards
Bryce


More information about the Java mailing list

AltStyle によって変換されたページ (->オリジナル) /