lua-l archive

Search lua-l

This index contains 143,604 documents and 1,774,497 keywords. Last update on 2023-03-08 .

1. RE: coroutine.resume() crash (score: 2)

Author: John Dunn <John.Dunn@...>

Date: Fri, 9 Sep 2022 02:24:09 +0000

Both - the app I'm referring to is just the sample code. The actual program is many times more complicated so I'm testing everything with the very simple sample app and am able to reproduce the issu

2. Re: Why is break not syntactically required to be the last statement in a block (anymore)? (score: 2)

Author: Philippe Verdy <verdyp@...>

Date: Sun, 21 Aug 2022 22:16:54 +0200

That's also my favorite syntax: using labelled loops is clearer than inserting a label after the loop, just before any unrelated instruction. And this fixes the allowed semantics for break<label> and

3. Re: The Future of Lua's C ABI Compatibility (score: 2)

Author: DENIS <denis@...>

Date: Sun, 24 Apr 2022 17:54:26 -0300

Hi all. Evolution has a cost. incompatible compiled modules (know issue): $cat main.lua -- -- main.lua -- print( _VERSION ) $luac-5.1 -o main51.out main.lua $luac-5.2 -o main52.out main.lua $lua52 ma

4. Re: The Future of Lua's C ABI Compatibility (score: 2)

Author: Matthew Wild <mwild1@...>

Date: Sun, 24 Apr 2022 20:49:15 +0100

Hi Ryan, To pick on one of the concrete examples you provided... The old behaviour of luaL_register() was very problematic, because it always inserted the module table into the default global environ

5. Re: I have a feature request... sandboxing. (score: 34)

Author: Sean Conner <sean@...>

Date: Wed, 16 Mar 2022 15:51:26 -0400

It was thus said that the Great Lars Müller once stated: Memory can be controlled using a custom allocator (see lua_Alloc and lua_newstate()). CPU time is more OS or platform specific though. -spc

6. Re: I have a feature request... sandboxing. (score: 35)

Author: Lars Müller <appgurulars@...>

Date: Wed, 16 Mar 2022 20:07:01 +0100

Yes. All of this is already possible in just Lua (limiting calls can be done using debug hooks). The proposed "feature" is oddly specific, tailored to a certain usecase. What I would really like to s

7. Re: I have a feature request... sandboxing. (score: 34)

Author: Spar <developspartv@...>

Date: Wed, 16 Mar 2022 22:03:54 +0300

Lot's of typos, sorry. Sandboxing can be done using _ENV variable or a parameter in the "load" function for the environment. _ENV is _G by default, which contains all functions you mentioned. Make a

8. I have a feature request... sandboxing. (score: 34)

Author: XavierH622 <JacobK622@...>

Date: Wed, 16 Mar 2022 18:59:08 +0000

I have a feature request... sandboxing implementation: two new c functions "lua_sandbox(lua_state *L, bool sandboxed)" and "lua_allow_fileio(lua_state *L, bool allow_fileio)" when lua_sandbox(*L, tru

9. Re: I have a feature request... sandboxing. (score: 34)

Author: Spar <developspartv@...>

Date: Wed, 16 Mar 2022 22:01:09 +0300

This is done in Lua using _ENV variable and a parameter in load function for the environment. Pass a table to that function that doesn't have function don't want users to use On 16 Mar 2022, 21:59 +0

10. Re: "Pre-empting" lua code (score: 2)

Author: Milind Gupta <milind.gupta@...>

Date: Wed, 9 Mar 2022 16:14:35 -0800

I made a module[1] to manage tasks just like that and help wrap them in environments. Using that the base Lua program can time slice between the tasks based on priority or any criteria they choose. [

11. Re: "Pre-empting" lua code (score: 2)

Author: Adam Higerd <chighland@...>

Date: Wed, 9 Mar 2022 15:37:36 -0600

On Wed, Mar 9, 2022 at 3:22 PM John W <jwdevel@gmail.com> wrote: Ah, I just discovered PIL 25.2 (Hooks) and 25.4 (Sandboxing), so perhaps debug.sethook() will be a good way to do this. Though still i

12. Re: "Pre-empting" lua code (score: 2)

Author: John W <jwdevel@...>

Date: Wed, 9 Mar 2022 13:22:20 -0800

Ah, I just discovered PIL 25.2 (Hooks) and 25.4 (Sandboxing), so perhaps debug.sethook() will be a good way to do this. Though still interested in other solutions, if people have them. -John

13. Re: Protect global table from any changes (score: 2)

Author: Flyer31 Test <flyer31@...>

Date: Fri, 21 Jan 2022 09:53:12 +0100

But then Lua will "sort of crash" in sandbox (of course with error message, but anyway crash) ... and if this crash is not restricted to sandbox but crashes also any further scripts which invoked thi

14. Re: Protect global table from any changes (score: 2)

Author: Petri Häkkinen <petrih3@...>

Date: Fri, 21 Jan 2022 10:11:37 +0200

This is not only about _G. In a sandboxed app you need to protect all the module tables too and potentially any tables you pass between sandbox and privileged environments. Proxying everything has a

15. Re: Protect global table from any changes (score: 2)

Author: Flyer31 Test <flyer31@...>

Date: Fri, 21 Jan 2022 07:08:37 +0100

sorry, another PPS: What would you then ask Lua to do, if somebody would try to modify _G inside sandbox or in later code? Should Lua then terminate with an error message, or just ignore this modific

16. Re: Protect global table from any changes (score: 3)

Author: Flyer31 Test <flyer31@...>

Date: Fri, 21 Jan 2022 07:05:45 +0100

PS: in my last post it should say "somehow at least prepared/planned for future" (not "not for future"). And my last paragraph proposal is somehow rubbish ... so if you would replace "unfreeze" by an

17. Re: Protect global table from any changes (score: 2)

Author: Flyer31 Test <flyer31@...>

Date: Fri, 21 Jan 2022 07:00:35 +0100

If you want to implement read-only data, you have to distinguish mainly also between "pre-defined read-only" or "run-time read-only". Pre-defined read-only I think is somehow at least prepared / plan

18. Re: Protect global table from any changes (score: 2)

Author: v <v19930312@...>

Date: Wed, 19 Jan 2022 20:34:10 +0300

I feel like a lot of other replies are focusing on the exact question of preventing modification of global table rather than intent of isolating scripts from one another. Say you've somehow managed t

19. Re: Protect global table from any changes (score: 2)

Author: Patrick Kurth <p.kurth@...>

Date: Wed, 19 Jan 2022 17:26:24 +0000

On Jan 19, 2022 18:14, Gé Weijers <ge@weijers.org> wrote: On Wed, Jan 19, 2022 at 7:23 AM Patrick Kurth <p.kurth@posteo.de> wrote: [...] local source = "rawset(_ENV, 'foo', function() print('bar') en

20. Re: Protect global table from any changes (score: 2)

Author: Spar <developspartv@...>

Date: Wed, 19 Jan 2022 17:02:08 +0300

There is a page about sandboxing global table on lua-users. But in a nutshell you just make a new table and put all "allowed" for other scripts functions On 19 Jan 2022, 16:56 +0300, Meir Shpilraien