[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: Lua registry, environment, and threads.
- From: Alexander Gladysh <agladysh@...>
- Date: Fri, 8 Jan 2010 13:56:27 +0300
On Thu, Jan 7, 2010 at 20:56, Leo Razoumov <slonik.az@gmail.com> wrote:
> On 2010-01-07, Roberto Ierusalimschy <roberto@inf.puc-rio.br> wrote:
>> Actually, getfenv and setfenv will be deprecated too. (But is is easy
>> to have them back for compatibility.)
>> Lua 5.2 will have "lexical environments", a kind of lexical setfenv.
>> The construction "in t do command end" will execute <command> with
>> all global variables being resolved in <t>.
> What would be Lua-5.2 idioms for creating sandboxes and jails?
I'm concerned by the sandboxing issue as well.
However, in 5.1 proper sandbox already requires using debug library
(debug.sethook). Since Roberto said that "official" setfenv and
getfenv would move to debug library and stay there, I guess we're
fine.
It is a pity though that trusted config file loading would have to use
debug library now... I understand that load{file/string} would not be
affected by "in" construction. Am I right?
Alexander.
- References:
- Lua registry, environment, and threads., Christian Tellefsen
- Re: Lua registry, environment, and threads., Patrick Donnelly
- Re: Lua registry, environment, and threads., Roberto Ierusalimschy
- Re: Lua registry, environment, and threads., Christian Tellefsen
- Re: Lua registry, environment, and threads., Roberto Ierusalimschy
- Re: Lua registry, environment, and threads., Mark Hamburg
- Re: Lua registry, environment, and threads., Patrick Donnelly
- Re: Lua registry, environment, and threads., Roberto Ierusalimschy
- Re: Lua registry, environment, and threads., Leo Razoumov