|Compiler Bugs, please! email@example.com (F. Liekweg) (2001-12-20)|
|Re: Compiler Bugs, please! firstname.lastname@example.org (Martin von Loewis) (2001-12-22)|
|Re: Compiler Bugs, please! email@example.com.OZ.AU (2001-12-24)|
|Re: Compiler Bugs, please! firstname.lastname@example.org (Toon Moene) (2001-12-24)|
|From:||email@example.com.OZ.AU (Fergus Henderson)|
|Date:||24 Dec 2001 00:06:39 -0500|
|Organization:||Computer Science, University of Melbourne|
|Posted-Date:||24 Dec 2001 00:06:39 EST|
An interesting category of compiler bug that is often forgotten is "security
flaws". In some cases, where the compiler is part of a security enforcement
process (e.g. Java bytecode JIT compilers), this is obviously a consideration,
but security flaws can arise in any compiler -- for example, failure to use
appropriate permissions for installed programs or libraries, or for temporary
files. It's important to remember that security issues must be considered for
Fergus Henderson <firstname.lastname@example.org> | "I have always known that the pursuit
The University of Melbourne | of excellence is a lethal habit"
WWW: <http://www.cs.mu.oz.au/~fjh> | -- the last words of T. S. Garp.
Return to the
Search the comp.compilers archives again.