On Sat, Aug 07, 2004 at 06:41:49PM -0700, Matt Setzer wrote:
Specifically, what are the top five or ten
security papers that you'd recommend to anyone wanting to learn more about
security? What are the papers that you keep printed copies of and reread
every few years just to get a new
/
http://www.google.com/search?q=international+SPIN+workshopstart=0start=0ie=utf-8oe=utf-8client=firefox-arls=org.mozilla:en-US:official
ciao,
-nash
Notes:
** This definition of exploit is chosen more or less arbitrarily. It
seems reasonable to me. It might not be. I would conjecture that any
and functional requirements is the
single best way to prevent intrusions, bar none.
nash e. foster
Stratum Security, LLC
--
the lyf so short, the craft so long to lerne.
- Geoffrey Chaucer
___
Secure Coding mailing list (SC-L)
SC-L
, but are still largely
theoretical.
http://en.wikipedia.org/wiki/Capability-based_security
That said, every decent Unix system I'm aware of has ulimit, which you
can use to restrict virtual memory allocations, total open files, etc:
nash @ quack% ulimit -a
...
virtual memory
universe.
-nash
On Tue, Aug 15, 2006 at 10:03:07AM +0200, John Wilander wrote:
Hi!
The security principle of minimizing your attack surface (Writing
Secure Code, 2nd Ed.) is all about minimizing open sockets, rpc
endpoints, named pipes etc. that facilitate network communication
between
