"Inteligent" Shrink?
Paul D. Fernhout
pdfernhout at kurtz-fernhout.com
Mon Feb 26 20:21:07 UTC 2007
A good question, but if you are serious about security, a much more secure
system is going to come from building a system up (especially up from a
textual description), and understanding what each component you include
does, and testing all their interactions, rather than just accepting what
results from some random shrink command that may or may not remove code
with various security problems. Security is not an add-on -- if you want a
secure application, the idea of security needs to be woven throughout
everything you do -- initial image or source, code development processes,
deployment approach, update streams, and so on.
--Paul Fernhout
Blake wrote:
> On Mon, 26 Feb 2007 11:26:07 -0800, Paul D. Fernhout
> <pdfernhout at kurtz-fernhout.com> wrote:
>
>> Why take a perfectly working application and start potentially
>> introducing all sorts of random errors into it at the last minute
>> just to save a bit of storage space and network bandwidth (especially
>> these days)?
>
>
> Security?
>
>
>
More information about the Squeak-dev
mailing list
|