[Bf-committers] Blender 2.5 malicious scripting

[Campbell Barton]

committed an option not to trust blend files on load.

the default state for this button can be changed in the user
preferences 'System' section

On Sat, Feb 27, 2010 at 2:04 AM, Erwin Coumans <erwin.coumans at gmail.com> wrote:
> The issue is about automatic running startup scripts, on loading a .blend
> file.
> I would like to turn off executing startup scripts, and want this off by
> default.
>
>>> a warning poping up for every file would just be annoying
> You could have the warning in the console.
> (and make it so no scripts can overwrite this security option)
>
> If you don't want those warnings/security,
> you can turn off this option and run all startup scripts (and be exposed to
> risks).
>
>
>
>
> On 26 February 2010 16:13, Tyler Tricker <tntricker at gmail.com> wrote:
>
>> Well thinking about it from a user perspective.. a warning poping up for
>> every file would just be annoying, and if scripts could over write this
>> option it wouldn't be that useful.
>>
>> <<'from conversations with python devs, the request of sandboxing
>> <<gets the response "dont even think about it!"'
>>
>> I find that disappointing. It's not even the language that would need to
>> change, just the ability to lock down the entire interpreter with policy
>> kit
>> would be useful.
>>
>> On an unrelated topic, I think this information should be put in to the
>> wiki
>> to prevent it from being a recurring topic.
>> _______________________________________________
>> Bf-committers mailing list
>> Bf-committers at blender.org
>> http://lists.blender.org/mailman/listinfo/bf-committers
>>
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers
>



-- 
- Campbell