Re: [SC-L] By default, the Verifier is disabled on .Net and Java

2006-05-12 Thread Dinis Cruz
Michael Silk wrote: You can't disable the security manager even with the verifier off. But you could extend some final or private class that the security manager gives access to. This is not correct. With the verifier disabled there are multiple ways you can jump out of the Security

Re: [SC-L] By default, the Verifier is disabled on .Net and Java

2006-05-12 Thread Dinis Cruz
Michael Silk wrote: "What is the point of the verifier?' , 'Why use it? and 'What are the real security advantages of enabling the verifier if the code is executed in an environment with the security manager disabled?' Huh? You can find what it does here:

Re: [SC-L] By default, the Verifier is disabled on .Net and Java

2006-05-12 Thread Dinis Cruz
Gary McGraw wrote: The switch from applets vs applications security to trusted code vs untrusted code happened with the introduction of jdk 1.1 (way back when). Ed and I followed the sun marketing lead in 96 when it came to applets vs applications, but we cleared this up later in Securing

[SC-L] Comment on Microsoft's leaked memos, and the unofficial end of Microsoft 'Trustworthy Computing'

2006-05-12 Thread Dinis Cruz
[Due to the relevance to the current discussion on Java Verifier, here is a blog entry that I wrote last November (also posted on Full Disclosure )] ___ Comment on Microsoft's leaked memos, and the unofficial end of Microsoft 'Trustworthy Computing'

Re: [SC-L] By default, the Verifier is disabled on .Net and Java

2006-05-12 Thread Michael Silk
On 5/12/06, Dinis Cruz [EMAIL PROTECTED] wrote: Michael Silk wrote: What is the point of the verifier?' , 'Why use it? and 'What are the real security advantages of enabling the verifier if the code is executed in an environment with the security manager disabled?' Huh? You can find what