[CM] S7 integrated in TIC-80, and bug reports

David St-Hilaire sthilaire.david at gmail.com
Fri Feb 3 05:43:11 PST 2023

I think it's mostly writing to files that is dangerous but disabling
reading would be important too, if not only for forbidding "breaking" the
fantasy console barriers. I looked at doing some changes but I was really
not sure how to do it properly. If you would be generous enough to do
the needed changes, it would be really amazing!

Thank you so much for your help!

On Fri, Feb 3, 2023 at 8:32 AM <bil at ccrma.stanford.edu> wrote:

> Do you need to disallow reading a file?  If it's just
> creating or altering a file that needs to be blocked,
> you could redirect fopen and fwrite (in s7.c) to
> functions that raise an error.  I don't think s7 uses
> creat, open (except with O_RDONLY), or write.  Also
> build it with WITH_C_LOADER=0 (to disallow dynamic
> loading of C object code), and maybe WITH_SYSTEM_EXTRAS=0.
> Hmmm... as I type this, this seems interesting --
> maybe I'll tackle it later today.  It might be
> equally easy to disallow reading a file -- fread etc.
> Oh, and for fopen, check the mode doesn't have "w" or "x"
> or whatever else might change a file.  I'm probably
> forgetting something obvious.
> (There's also the sandbox procedure in stuff.scm, but
> it's been years since I looked at it).

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://cm-mail.stanford.edu/pipermail/cmdist/attachments/20230203/f2da3795/attachment-0001.html>

More information about the Cmdist mailing list