Problem (was: Re: need help with tool requirement)
Bill Freeman
f at ke1g.mv.com
Wed Apr 21 08:22:01 EDT 2004
bmcculley at rcn.com writes:
...
> What approach would provide sufficient assurance that the code
> does not contain any "Easter eggs" or trap doors to allow
> future egg-laying?
Heavily reviewed OSS (note not necessarily FOSS)?
But then how can you be sure that the binary delivered was
compiled by an un-hacked compiler and linked against un-hacked
libraries? Risk runs as far as you want to take it.
Bill
More information about the gnhlug-discuss
mailing list