[Bf-committers] "Security" gets in the way
horace3d at gmail.com
Fri Apr 30 02:27:22 CEST 2010
* Objective: sandbox tinypy and then (as in lunatic python) build
a python module that uses tinypy for safe execution of “unknown” code
it's just an idea at the moment and not implemented but this sounds
interesting. :) tinypy could be used for drivers in the long term.
in the short to mid term there doesn't seem to be an easy and secure
solution but in the long term all the "this is impossible with python"
seems to be wrong to me. to me it looks like in 2-3 years the whole
situation will look different (pypy, tinypy,...) and there will be
On Fri, Apr 30, 2010 at 2:09 AM, Martin Poirier <theeth at yahoo.com> wrote:
> There's still very little doubt that this will be the solution that is going to be adopted (in the short to mid term at least).
> --- On Thu, 4/29/10, Benjamin Tolputt <btolputt at internode.on.net> wrote:
>> From: Benjamin Tolputt <btolputt at internode.on.net>
>> Subject: Re: [Bf-committers] "Security" gets in the way
>> To: "bf-blender developers" <bf-committers at blender.org>
>> Received: Thursday, April 29, 2010, 7:46 PM
>> Martin Poirier wrote:
>> > 0. Keep current features, switch from default on to
>> default off.
>> In which case you may as well not have the feature at all.
>> The people
>> most vulnerable to a malware attack from ANY vector are
>> those that would
>> not know to turn security on.
>> Not to mention the fact that security of an "on/off"
>> variety pretty much
>> hoses any chance of decent rigs whilst having security
>> enabled. As I've
>> mentioned, it's like disabling macros in Office and it not
>> allowing you
>> to use bold fonts and paragraph spacing. Sure you can get
>> around it, but
>> it is not what one would consider a "good solution"
>> Bf-committers mailing list
>> Bf-committers at blender.org
> Bf-committers mailing list
> Bf-committers at blender.org
More information about the Bf-committers