> > That's interesting to check, but I don't like to make users responsible > for checking each .blend they want to load. My preference is a way that's > relatively safe and works out of the box for everyone (except system > administrators :). > > what if we can make it a feature of blender itself and on by default. it will check the blend file and will display a start up msg if there are known security holes and asks the user if he wants to open it . may be the option to ignore the risks can be local to a blend file so next time its opened it doesnt annoy the user. also having a cli option to disable the feature would be handy :) ... (not talking about the auto-run scripts option) one way to implement this is generate a key when the user runs blender for the first time. blender will check the blend file and determine if its legit according to the key (local files will already have the installed key from local blender). if not it will annoy the user with the risks involved . if user finds it safe he can ignore it for the rest of the blend files life .
All this can happen in the background without users intervention. This way we dont have to hack and slash CPython and make it unusable . let python be We just have to invest time on creating a modular base system to find bad code in .blend files . it can be based on rules that can be improved with time . IIRC in my previous workplace we had a similar kind of system to check for malicious lines and bad practices in perl scripts -- regards - shrinidhi Even god fails to understand a human until his death! http://www.linkedin.com/in/shrinidhi666 https://github.com/shrinidhi666 <http://www.imdb.com/name/nm3025616> _______________________________________________ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers