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 
Benjamin TolputtApr 28, 2010 6:45 pm 
63 later messages
Subject:Re: [Bf-committers] "Security" gets in the way
From:Benjamin Tolputt (btol@internode.on.net)
Date:Apr 27, 2010 7:57:53 pm
List:org.blender.bf-committers

Matt Ebb wrote:

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.

Well, first thing to note is that I think that the current implementation is not really a solution and needs to be turfed. There is no way of knowing if someone has tampered with a file on a website, so a malicious user need only hack the web-site of someone putting up, say, a useful base rig that was verified in the past as "secure". It is trivial to then link Python code into every file then saved by Blender. Given the fact Python is the problem - I don't see a solution with it as the scripting foundation of Blender as things stand currently.

That said, I find the idea that one doesn't want to flick one extra switch on initial setup a relatively weak reason not to include security. There is always going to be a trade-off with security - it is /built-in/ to the whole model of limiting what can be done so as not to compromise/hurt yourself. And not allowing it to be set as the default basically makes it useless (because those most vulnerable will not even know to look for it to turn on).

I know & understand your position on this (I've lost count of how many time a missing password or command line flag has meant an overnight data processing run has come out bad); but that doesn't mean I agree with your position that some small hassle ONCE on install outweighs security concerns.

Our disagreement is all superfluous though because I think the current security option is worse than none. It both provides an illusion of security AND causes all the hassles (& more?) a real solution would entail.