RUNZ known issues
From hacktolive.org
Bugs on RUNZ:
not fixed
- clicking "no" on kdialog launches the file (only if "no" is selected using tab), bug on Kdialog: https://bugs.kde.org/show_bug.cgi?id=194698
- .runz file is unmounted too soon if autorun file contains: "gnome-terminal --title "DO NOT CLOSE THIS WINDOW" -x gksu ./installer.sh"
- If there is no free space on the system, the RUNZ dialog contains no text. Possible fix: check if there is free space available.
Possible features
- check arguments for invalid arguments and warn user: ./ .. .
- hashes (MD5/SHA1) inside ISOs to detect corruption
- option to add .runz file to whitelist
- timeout to auto-kill dialog and unmount
- in case fuse.conf is not readable and/or the allow_other option is not enabled, then we must mount with the regular options
- Check if it is really required to reboot for FUSE to work or the user just needs to logout/login
- Add ability to disable the question dialog ("Are you sure you want to run this file?"), file at /etc/runz/question with "no" or "yes". If files does not exist, then RUNZ must create it with "yes"
- Change user_allow_other to user_allow_root in /etc/fuse.conf
- Put "minor-locks" inside the "fake-folder" to avoid conflict with files with similar names
- check if sandbox is writable
- trap to KILL runz-launch in the end
- create symlink to autorun, and then launch it: friendlier view on process monitor
- more specific error messages (test is mounting operation goes well, and only then test for autorun)
- Check if file exists before trying to run it
- Make fuse.conf readable by all users on install script inside deb
- List of dependencies inside the ISO/RUNZ (for users of other distros)
