Scott Barnes wrote:
Server sandbox -- basically all CFMX operations occur through Java, the sandbox controls all java access. The issue of low level access to the box is common across all application servers -- it's not unique to CF. That's why its dangerous to consider any type of commerically sensitive deployment on shared infrastructure.Has anyone else but me contemplated the potential whole in CFMX having the ability to access .java files? i.e. in CFMX although it has CFFILE/DIRECTORY flags on/off with Sandboxing, what's to stop you from manipulating files/directories from other peoples components made in .java?or can that be controlled? If so how?
The new server sandbox for CFMX is infinitely better than prior versions of CF:
- um.. it actually works as you would anticipate
- it is simple to set up -- so more likely to be actually used
-- geoff
http://www.daemon.com.au/
---
You are currently subscribed to cfaussie as: [email protected]
To unsubscribe send a blank email to [EMAIL PROTECTED]
MX Downunder AsiaPac DevCon - http://mxdu.com/
