[1627] in WWW Security List Archive
Re: Java "security holes'
daemon@ATHENA.MIT.EDU (Marianne Mueller)
Wed Mar 13 17:10:57 1996
Date: Wed, 13 Mar 1996 11:05:16 -0800
From: mrm@doppio.Eng.Sun.COM (Marianne Mueller)
To: chess@watson.ibm.com
Cc: www-security@ns2.rutgers.edu
In-Reply-To: <199603131715.MAA06090@ns2.rutgers.edu> (chess@watson.ibm.com)
Errors-To: owner-www-security@ns2.rutgers.edu
I should issue disclaimers on all email ... :-)
I agree, an "implementor's guide" relies on an articulated security
model.
It's hard to argue with this statement:
A security model should list all the things that are officially
part of the security model.
I was just trying to say that it's unlikely anyone knows 100% of all
security-related things in a system. Security is a lot like system
robustness, in that many bugs can be exploited to attack a security
model. Having said that, yes, of course, the intent in articulating a
security model is for it to be as complete as possible.
Marianne
