3 ms·
This would be more useful if it used a virtual file system. What happens if the program writes a bunch of stuff to disk then later on tries to read it?
by burrows 11y ago
This would be more useful if it used a virtual file system.
What happens if the program writes a bunch of stuff to disk then later on tries to read it?
- gruez 11y agobased on the README, the syscalls are intercepted and are not emulated, so the program will read back the original file.
- peteretep 11y agoAn additional value of that approach would be you could then decide you wanted to keep the results
- qb45 11y agoI wonder if it would be possible to use btrfs snapshotting for that.
- whenov 11y ago#!/bin/bash touch x if [ -f "x" ]; then rm -rf / else echo "I'm just an innocent little script." fi
- singlow 11y agorm -rf --no-preserve-root
- justinjlynn 11y agoNever put salt in your eyes. -- Kids In The Hall
- mapcars 11y agoIn Plan9 one could create clean separate filesystem and run unsafe program there, or, make a filesystem server which logs each of ~20 api calls of 9p protocol, since they are all you have to manipulate files.
- deleted 11y ago[deleted]
- qb45 11y agoSomething like unionfs/overlayfs, which are the magic allowing Linux Live CDs to "modify" files and directories stored on read-only medium. https://www.kernel.org/doc/Documentation/filesystems/overlayfs.txt https://www.kernel.org/doc/Documentation/filesystems/overlay...
- widdma 11y agoMbox does exactly this: https://pdos.csail.mit.edu/archive/mbox/ https://pdos.csail.mit.edu/archive/mbox/