[REBOL] Re: secure
From: antonr:iinet:au at: 18-May-2003 15:35
Ah, it makes sense now.
I did a trace at the end of my user.r and saw
that this code is executed after the user.r
is done:
do compose/deep [secure [
file [ask read ask write ask execute]
(system/options/home/user.r) [allow read]
(system/options/home/prefs.r) [allow read]
(system/options/home/public) [allow read]
(either all [system/options/script not find system/components
'link]
[first split-path system/options/script]
[system/options/home])
allow
]]
So even if you set the secure level before in the user.r,
those settings will be ignored since rebol sets the secure level
itself as above.
But if 'secure is none, then the above code won't change
the security level anymore.
I assume rebol starts with no security at all so it can
do what it needs to do.
I hope you understand what I am trying to say here;
The 'secure word has been pointed away from its original
function, therefore it does nothing when rebol tries to
increase the security.
I put these two lines at the end of my user.r to
get the trace:
trace on
echo %startup-trace.txt
I now remember that this topic was already talked about
a long time ago. :)
Anton Rolls.