On Mar 3, 2007, at 8:11 , Andreas Raab wrote:
Bert Freudenberg wrote:
The debug log you attached before shows that your image was in restricted mode. In this sandbox mode, you are only allowed to write inside the SecurityManager's "untrusted directory". I don't think you're even supposed to save the image when in sandbox mode, so if you try anyway, there might be any number of bugs lurking. IIRC the image save logic assumes that FileDirectory default and the image directory are identical. But in sandbox mode, this is not true anymore.
That is correct. With the sandbox on, you can't safe the image - otherwise this would be a trivial way for a malicious bit of code to make itself forever at home in that image.
Well, you should be able to save the image in the untrusted directory, right? Squeakland users usually never save the image, and Squeak.org users never enable the sandbox, so there might well be bugs hidden there.
- Bert -