lua-users home
lua-l archive

Search lua-l

This index contains 143,615 documents and 1,774,615 keywords. Last update on 2023-03-09 .

Query: [How to search]

Display: Description: Sort by:

Results:

References: [ sandboxing: 527 ]

Total 527 documents matching your query.

301. Improved functions sandboxing in Lua and LuaJIT2 (score: 33)
Author: Tymur Gubayev <tymur.gubayev@...>
Date: Mon, 21 Feb 2011 05:49:53 +0100
I apologize for my english, i know it isn't well. I'm writing some server application in pure Lua (pure mostly because of very limited experience in C/C++), and want to sandbox dangerous Lua code (sc
302. Re: newproxy, bug (score: 2)
Author: HyperHacker <hyperhacker@...>
Date: Mon, 10 Jan 2011 16:51:28 -0700
Doesn't 5.2 add __insert as well, and some other useful metamethods? (On a semi-related note, does string.format call tostring (and by extension __tostring) in 5.2? Having to do that manually always
303. Re: newproxy, bug (score: 2)
Author: Mike Pall <mikelu-1101@...>
Date: Tue, 11 Jan 2011 00:32:19 +0100
Userdata proxies are faster (*) and they can't be messed up by accident with rawset() or table.insert(). And of course they are the best choice for real sandboxing. Also newproxy() is currently the o
304. Re: Lua Cookbook (score: 2)
Author: beo wulf <beowulf@...>
Date: Tue, 4 Jan 2011 03:55:47 -0800
This cookbook is aimed at lua 5.2 right?
305. Re: Lua Cookbook (score: 2)
Author: Axel Kittenberger <axkibe@...>
Date: Tue, 4 Jan 2011 12:47:26 +0100
I support this idea. As far I get it, a cookbook is some sort of of book an advanced Lua programmer will page through very quickly and put it back - "boring, know it all." But for some people like t
306. Re: Standard libraries (was Re: Virgin tables) (score: 2)
Author: Alexander Gladysh <agladysh@...>
Date: Mon, 3 Jan 2011 03:53:52 +0300
Well, no problem. Lets put together a list of topics and a topic format, and I'll write them. I believe that I, maybe, have something to say on the themes I listed above. (Also other Lua-related topi
307. Re: Standard libraries (was Re: Virgin tables) (score: 2)
Author: Henk Boom <henk@...>
Date: Sun, 2 Jan 2011 18:01:06 -0500
+1. Simple examples of complex topics are often extremely useful as the first step to learning new concepts. henk
308. Re: Standard libraries (was Re: Virgin tables) (score: 2)
Author: kevin beckford <chiggsy@...>
Date: Sun, 2 Jan 2011 14:27:17 -0800
I disagree, this is exactly what you'd want in a cookbook, since to address any of those topics you would inform the reader about thinking patterns for Lua code. The fact that you even mentioned it
309. Re: Lua Cookbook (score: 2)
Author: Marc Balmer <marc@...>
Date: Sun, 02 Jan 2011 13:18:54 +0100
Am 02.01.11 13:13, schrieb Pierre Chapuis: Why not advanced techniques? There is enough material for beginners around, and we pros need something to read, too ;) I could contribute a section on inter
310. Lua Cookbook (was: Standard libraries (was Re: Virgin tables)) (score: 2)
Author: Pierre Chapuis <catwell@...>
Date: Sun, 02 Jan 2011 13:13:21 +0100
I, maybe, can help with some recipes, especially on Sandboxing, DSL and codegeneration. Although these topics are, maybe, a bit too big for a cookbook format. I agree, a cookbook should not contain
311. Re: Standard libraries (was Re: Virgin tables) (score: 2)
Author: Steve Litt <slitt@...>
Date: Sun, 2 Jan 2011 04:02:22 -0500
wrote: wrote: I will. I can code up a text-based filepicker and picklist tools for Lua. Given my schedule it will take 6 to 10 weeks, and probably you'll all have better ideas on how to code it so mi
312. Re: Standard libraries (was Re: Virgin tables) (score: 2)
Author: Alexander Gladysh <agladysh@...>
Date: Sun, 2 Jan 2011 09:42:49 +0300
Although these topics are, maybe, a bit too big for a cookbook format. Anyway, one can start with a list of topics (maybe along with a way for authors to commit for one or more and for potential read
313. Re: Standard libraries (was Re: Virgin tables) (score: 2)
Author: Alexander Gladysh <agladysh@...>
Date: Sun, 2 Jan 2011 09:17:06 +0300
I, maybe, can help with some recipes, especially on Sandboxing, DSL and codegeneration. As for the organization, I like the way ProGit book is done: https://github.com/progit/progit Alexander.
314. Re: any plan about luajit2 support 5.2! (score: 2)
Author: Mike Pall <mikelu-1011@...>
Date: Fri, 19 Nov 2010 17:09:09 +0100
You're right of course. So I've reconsidered and now the upwards-compatible 5.2 features in LuaJIT are *DISABLED* by default. Even though they are unlikely to break anything for most people. See src/
315. Re: any plan about luajit2 support 5.2! (score: 4)
Author: GrayFace <sergroj@...>
Date: Fri, 19 Nov 2010 01:09:15 +0600
I haven't done sandboxing yet, but here are my 2 cents: (*) I guess most users won't care or won't need to know about _ENV. But those that do are unlikely to upgrade, as they'll have to ditch their s
316. Re: any plan about luajit2 support 5.2! (score: 3)
Author: Alexander Gladysh <agladysh@...>
Date: Wed, 17 Nov 2010 22:58:44 +0300
I care for _ENV. And yes, I'll have to redesign my "sandboxing frameworks". So, for me the checklist to be able to switch to 5.2 is as follows: 1. LJ2 supports 5.2. I will not even move before that.
317. Re: any plan about luajit2 support 5.2! (score: 2)
Author: Enrico Colombini <erix@...>
Date: Wed, 17 Nov 2010 17:36:59 +0100
I always use a local copy of Lua executable + needed_libs in each project, so changes can't break anything. One of my projects would need to be redesigned for _ENV (it probably will, in a distant fut
318. Re: any plan about luajit2 support 5.2! (score: 2)
Author: Mike Pall <mikelu-1011@...>
Date: Wed, 17 Nov 2010 17:12:19 +0100
Well, Lua source code is almost unaffected by the 5.2 changes (*). Having two different targets is mainly required to handle the Lua/C ABI breakage between 5.1 and 5.2. But until there are tons of C
319. Re: Sanitizing first class values (score: 2)
Author: George Georgalis <george@...>
Date: Thu, 4 Nov 2010 21:54:38 -0700
Thanks, Lua is quite a sophisticated language! -George
320. Re: Sanitizing first class values (score: 2)
Author: steve donovan <steve.j.donovan@...>
Date: Thu, 4 Nov 2010 08:31:26 +0200
Ah, but then sandboxing becomes important. You can control the environment in which any user values/expressions are evaluated, so that no potentially harmful functions can be accessed. http://lua-use

Search by Namazu v2.0.21