Re: Security



So> So, is there an equivalent type of problem with Lisp? The only
So> thing I can think of is to be careful of code-injection type problems
So> where evaluating s-expressions from an untrusted source could be
So> harmful. But that's pretty obvious.

even w/o eval, people can make DoS attack interning too many symbols,
starving server's memory.
so doing READ is tricky


.



Relevant Pages

  • Re: Security
    ... be careful not to allow buffer overrun's to occur. ... how this could be a problem in Lisp. ... thing I can think of is to be careful of code-injection type problems ...
    (comp.lang.lisp)
  • Security
    ... with C/C++ programs you have to ... be careful not to allow buffer overrun's to occur. ... how this could be a problem in Lisp. ... thing I can think of is to be careful of code-injection type problems ...
    (comp.lang.lisp)