atom feed94 messages in org.blender.bf-committersRe: [Bf-committers] "Security" gets i...
FromSent OnAttachments
Daniel Salazar - 3Developer.comApr 27, 2010 6:00 pm 
Matt EbbApr 27, 2010 6:17 pm 
Benjamin TolputtApr 27, 2010 7:09 pm 
Benjamin TolputtApr 27, 2010 7:25 pm 
Matt EbbApr 27, 2010 7:33 pm 
Benjamin TolputtApr 27, 2010 7:57 pm 
Campbell BartonApr 28, 2010 1:04 am 
Daniel Salazar - 3Developer.comApr 28, 2010 1:14 am 
Remo PiniApr 28, 2010 1:34 am 
Benjamin TolputtApr 28, 2010 2:36 am 
horace grantApr 28, 2010 4:28 am 
Benjamin TolputtApr 28, 2010 7:06 am 
horace grantApr 28, 2010 7:57 am 
Remo PiniApr 28, 2010 8:32 am 
Nery ChucuyApr 28, 2010 8:42 am 
Raul Fernandez HernandezApr 28, 2010 8:59 am 
male...@licuadorastudio.comApr 28, 2010 9:31 am 
Bassam KurdaliApr 28, 2010 9:55 am 
Raul Fernandez HernandezApr 28, 2010 10:59 am 
Makslane RodriguesApr 28, 2010 1:52 pm 
horace grantApr 28, 2010 2:28 pm 
Matt EbbApr 28, 2010 2:34 pm 
Charles WardlawApr 28, 2010 2:59 pm 
Makslane RodriguesApr 28, 2010 3:15 pm 
Tom MApr 28, 2010 3:16 pm 
Ruslan MerkulovApr 28, 2010 4:33 pm 
Charles WardlawApr 28, 2010 5:09 pm 
joeApr 28, 2010 5:21 pm 
Benjamin TolputtApr 28, 2010 5:31 pm 
Ruslan MerkulovApr 28, 2010 5:40 pm 
64 later messages
Subject:Re: [Bf-committers] "Security" gets in the way
From:Matt Ebb (ma@mke3.net)
Date:Apr 27, 2010 7:33:14 pm
List:org.blender.bf-committers

On Wed, Apr 28, 2010 at 12:09 PM, Benjamin Tolputt <btol@internode.on.net> wrote:

Matt Ebb wrote:

This stuff is unnecessary in a studio environment,

Agreed. The primary target user-base for the security issue are new & inexperienced users who *will* download material online and install it without thinking about the consequences because they are simply unaware of them. I fully accept that there should be an option to turn this thing off completely and have that stick. I have similar "ignore this warning from now on" options in most the applications I put together.

This is the problem though really - it's not always enough to say 'change the defaults and save the preferences' because inevitably problems still occur. For example some situations in which this caused issues included:

* An animator taking some work home to do over the weekend to meet a deadline * Sending files to another studio who was helping us out with rendering * Bringing in and adding in borrowed machines to the render farm (like artists laptops) to help with last-minute rendering power

In these situations, it was a matter of quickly installing blender and getting it going, often not by blender experts. It's not as if it was a strictly controlled 'software roll-out' environment - indeed most studios that use Blender (small ones) probably don't have that kind of organised IT infrastructure like you might have in a large corporation.

Sure, one can say "oh it's your fault for not enabling the options" but that brings me back to the original point - regardless of whether you want to blame the user or not, the existence of this 'security' does cause real practical problems. Especially in cases like I described above where you're tired and stressed meeting a deadline and the last thing on your mind is going to disable some stupid security preference and saving default preferences.

Matt