Security

Does anyone have any specific pointers on how to write more secure
code in Common Lisp? For instance, with C/C++ programs you have to
be careful not to allow buffer overrun's to occur. But I can't see
how this could be a problem in Lisp.

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

Are there a set of hard-won rules-of-thumb to help avoid specific
security issues?

Thanks for any info!

Steve
.

Relevant Pages

  • Re: [PATCH] Undo some of the pseudo-security madness
    ... You just have to be more careful where you map. ... the lisp system executable itself -- because the lisp code ... serve the application deployment cause -- abolish the need for ...
    (Linux-Kernel)
  • 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)
  • Re: Security
    ... is there an equivalent type of problem with Lisp? ... So> thing I can think of is to be careful of code-injection type problems ...
    (comp.lang.lisp)
  • Re: scheme seems neater
    ... > bite you. ... You have to be careful about some things, ... >> that it is a reasonable choice. ... later implementations changed many things from Lisp 1.5. ...
    (comp.lang.lisp)
  • Re: Lispnik logo (was Re: Lisp Logo Madness!)
    ... > OTOH, we should be careful what we ask for;) ... In case you haven't seen the Save Lisp and Die logo: ... I post that because there's this terribly cute logo in the middle right ...
    (comp.lang.lisp)