> From: Marc Balmer [mailto:[email protected]] > > > It's not *much* less safe than compiling and executing a string in the > > kernel. The only additional attack surfaces are that you can write things > > that the compiler wouldn't write. This can (1) cause a crash at load time, > > or it can (2) cause surprising behavior later. > > The problem is that malicious bytecode in 5.1 is possible. That is why > there is a guad against loading bytecode.
Malicious in what sense? Is this a type-1 problem or a type-2 problem? Or something else that I've not considered? --Terry
