lisp and security

From: John Thingstad (john.thingstad_at_chello.no)
Date: 02/25/04 

Date: Wed, 25 Feb 2004 16:31:13 +0100

For the record. The reason for the thread was not to start a lisp vs XML
discussion
but to find out if anyone knew a simple way to ruggedise eval.
I know the difference between read and eval. It was the "#.(evilcode)" I
wanted to avoid.
Setting *READ-EVAL* to nil was the answer I was looking for.
As for ruggedising the reader further I am not sure it is worth it.
(If the system crashes I just reset it. It is mallicious worms breaking in
I want to avoid.)
Anyhow thanks for all the responses.

John 

-- 
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/

Relevant Pages

  • Re: lisp and security
    ... The reason for the thread was not to start a lisp vs XML ... > wanted to avoid. ...
    (comp.lang.lisp)
  • Re: lisp and security
    ... The reason for the thread was not to start a lisp vs XML ... > wanted to avoid. ...
    (comp.lang.lisp)
  • Re: X-expressions: XML for Lisp for Lisp programmers who hate XML
    ... but it seems that there is no XML package defined... ... is there some reason to write CamelCase or UPPERCASE ... You keep writing Lisp code ...
    (comp.lang.lisp)
  • Re: DS Alert (1-5)
    ... predictions wre more reliable and reasonably accurate instead of the WAG ... I'd certainly avoid driving on that road today. ... Stocking up on extra perishable supplies would also make ... probably the reason he was still alive. ...
    (rec.arts.comics.strips)
  • Re: That Poor Kid In Portugal
    ... for some reason see as the epitome of US capitalism with little ... people who avoid them on principle, like they're making some sort of stand against US ... big mac has fewer calories that the quarter pounder - either way I'd ...
    (uk.media.tv.misc)