time to do (the chroot jail a bit easier,
> >> actually...), but quite do-able.
> >>
> >> It depends on (1) how paranoid you are, (2) how much trouble you
> >> want to
> >> have for yourself to achieve those restrictions...
> >>
> >> hadl
ote:
>
> What are you trying to defend against? A serious attacker could still
> use rm/assign/get/eval/... to circumvent your replaced functions. I
> think it would be very difficult (if not impossible) to prevent this
> from happening), especially if the user can load packages.
>
Hi,
I am trying to tighten file I/O security on a process that passes a
user-supplied script to R CMD Batch. Broadly speaking, I'd like to restrict
I/O to a designated path on the file system. Right now, I'm trying to
address this in the R environment by forcing the script to use modified
version
I don't know of one.
Ideally, instead of a specifc function anyNA() function, any() could be
perhaps be extended to any(x, FUN) where FUN returns a logical for an
element of x, and implemented to find the 1st instance as you suggest.
Mike
On 8/13/07, Henrik Bengtsson <[EMAIL PROTECTED]> wrote:
