I keep running into sandbox trouble due to file- and directory-existence tests that are buried inside functions that inspect Racket's configuration. For example, the contract system runs into trouble because it uses `path->relative-string/library', which has to find collections, so it needs to look at the installation's configuration file, which it may have to find relative to the `racket' executable (and that's just the tip of the iceberg).
Although I can imagine ways to fix the problem that involve trusting the modules that search for paths, I wonder whether there's any harm in simply allowing all file- and directory-existence tests. Is there a situation where allowing an arbitrary file- or directory-existence test would be bad? _________________________ Racket Developers list: http://lists.racket-lang.org/dev
