[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Emacs RPC security
From: |
Stefan Monnier |
Subject: |
Re: Emacs RPC security |
Date: |
Tue, 03 May 2011 10:47:08 -0300 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) |
> The natural way (and only way, I believe) to provide a restricted
> execution environment in Common Lisp is to leave the user in a package
> that contains only "safe" symbols. As elisp does not have packages in
> the CL sense, the only way I can think of would be to not use the
> elisp reader at all, and provide you own – or else go through the read
> form and excise forbidden symbols. This seems like a nontrivial (and
> somewhat pointless?) endeavour.
Indeed. The way to do it in Elisp is to not use `eval' but instead
implement some other protocol/language. Which is why it's outside the
scope of server.el.
Stefan
- Re: Emacs RPC security, (continued)
- Re: Emacs RPC security, Ted Zlatanov, 2011/05/02
- Re: Emacs RPC security, Lars Magne Ingebrigtsen, 2011/05/02
- Re: Emacs RPC security, Ted Zlatanov, 2011/05/02
- Re: Emacs RPC security, Lars Magne Ingebrigtsen, 2011/05/02
- Re: Emacs RPC security, Ted Zlatanov, 2011/05/02
- Re: Emacs RPC security, Lars Magne Ingebrigtsen, 2011/05/02
- Re: Emacs RPC security, Ted Zlatanov, 2011/05/02
- Re: Emacs RPC security, Lars Magne Ingebrigtsen, 2011/05/02
- Re: Emacs RPC security, Stefan Monnier, 2011/05/02
- Re: Emacs RPC security, Harald Hanche-Olsen, 2011/05/03
- Re: Emacs RPC security,
Stefan Monnier <=
- Re: Emacs RPC security, Stefan Monnier, 2011/05/02