I wonder if this could be a security issue for us.  Theoretically:

1) attacker manages to land a bad file on disk, via upload or some other approach.  Maybe it's a .jpg file that has executable content in it?  Not sure
2) attacker gets admin access to G3 via some means - maybe XSS?
3) attacker sets the binary path to the directory containing the malicious file
4) attacker uses a setting to target the specific file as a binary (like ffmpeg, or something similar - I forget offhand but I think at least one of our binaries can be set that way)
5) this code runs and makes the malicious file executable
6) attacker manages to execute it some other way

I need to think about that.  Right now I think that's probably not a major issue because once you have admin access you can do a lot of other bad stuff already.. thoughts?