Hi Tim,
it would help if you mentioned what system you are running on.
you wrote:
>;If I run rebol from the command line as thus:
>; rebol -s FileIO.r to disable the security check
>; is disabled
>
>; I would like to be able to disable the security check from
>; the code itself:
>; After review example files, it appears that the following as
>; the first line should do it:
>#!rebol -s
REBOL does not interpret this line. It is a shell command and will be
interpreted by bash or whatever shell you are using.. It will work if the
the file is set executable (under Linux or some other Unix system) and you
start the script up under the shell:
./some-script.r
provided that REBOL is accessable from your current directory.
It will not work, if you expect REBOL to interpret that:
rebol some-script.r
If you're using MS Windows it won't work, since MS Windows off the shelf
does not have a shell that supports the bang notation for scripts, as Unix
does. Here you will have to
- set the REBOL file properties command line to rebol.exe -s
or
- if you registered REBOL script files in the Windows registry to launch
REBOL.exe when they are double-clicked, you will need to include -s in the
command line of the windows registry tool, where you do the file assoications.
you wrote:
> Actually, what I was really wanting to do
>is disable the security check from the code itself.
>I am reposting and rewording, so that others in the
>list may review. Don't work too hard!!
>>:)
I thought you meant to do it programmatically, i.e. so that REBOL
interprets your request and does it.
In that case
help secure
would help you with that. IMHO it's the only way to disable security check
programmatically.
Since a rogue script running on your Web site cgi may want to reduce
security settings for itself, if you reduce security level programmatically
you have to ok the change.
For instance, going from tight security to
secure allow
will request permission once, while it remains in secure allow mode, it
will not reuqest permission if you set secure allow again later.
If you go from secure allow for instance to secure throw, now permission is
required, since you are raising security level. Going back to secure allow
will again require your explicit permission.
That's the only way there is to
>disable the security check from the code itself.
as far as I know.
Hope this helps,
;- Elan >> [: - )]
