The goal of this project is to create a wrapper around standard Lisp reader to make it able to read input from untrusted sources, such as internet sockets.
Example usage - creating a client-server communication protocol that is based on S-expressions. Using bare READ on both server and client allows the malicious client/server to execute any code on any other networked clients/servers.
As of now, this repository includes variant of READ secure against internbombing, excessive input and macro characters.
- Internbombing - the behaviour of READ function, which automatically interns every unknown symbol it doesn't know. This can lead to namespace pollution and blowing the heap with input like
(symbol1 symbol2 ... symbol9999999999).
- Excessive input - causing an out of memory error simply by feeding the READ function an invalid S-expression that does not terminate.
- Macro characters - functioning of character macros within Lisp syntax, both standard and implementation-defined. They create simple dangers such as
#.(let (memleak) (loop (setf memleak (cons memleak memleak))))along with more subtle ones that are not listed here.
&optional (stream *standard-input*) ?
s-expression error-status *
S-EXPRESSION - the read S-expression or NIL if reading was impossible. *
ERROR-STATUS - one of
:INCOMPLETE-INPUT :MALFORMED-INPUT :INPUT-SIZE-EXCEEDED or NIL in case of success.
- Input will not be read beyond this size; SAFE-READ will return
:INPUT-SIZE-EXCEEDEDas its second value.
- Defaults to 128 kB.
- Only lists are accepted as input. Atoms produce
- All macro characters other than
- Package-qualified names (including keywords) produce
- All symbols read are non-interned.
- Read always stops on EOF and newlines.
- Reading from each stream is buffered, meaning that subsequent calls to SAFE-READ can produce a valid S-expression if it spans over multiple lines. An example is a list containing a string containing a newline.
- No new S-expression must begin on the line where the previous one ended as they will be ignored.
make it possible to signal conditions instead of relying on the second return value.
make it possible to read multiple expressions without newlines
- Micha? "phoe" Herda <email@example.com>
- BSD 2-clause