Existing users, 
Safe Terminal
prevent shell script execution without user confirmation
Version: 0.3
Prediction...
Feedback Type: Commentary
Contributed by: lkrupp Thursday, February 23 2006 @ 04:15 PM PST
Product Platform: MacOSX
Used Product For: Have Not Tried
Recommend Product: NO
I would not install this under any circumstances. I would bet some serious money that, when Apple releases their fix for this problem (and they will), anyone who has installed this will find their systems hosed after the update. There are NO reports of this being exploited to date. Wait until Apple officially fixes it. You'll be happy you did.
Comments
I agree, don't install this! - MyMac8MyPC
I also agree that it would be better to wait until Apple addresses this issue, which they are already working on. In the mean time you can go to Preferences > General and UNclick "Open safe files after opening". Better safe than sorry, and the less programs like this on your Mac, the less chance for other security holes to pop up. The answer is not to use a band-aid approach (like this program) to fix this issue, the answer is to let Apple plug the hole and then there is no problem to worry about.Friday, February 24 2006 @ 04:06 PM PST
I will not wait for Apple, and it is safe - Nir Soffer
Safe Terminal does not change Terminal.app or the system in any way, and should continue to work with new versions of Terminal.app and the system.Technically, it disable dynamically one documented method in Terminal.app, used to verify files before they are opened. When the Terminal ask "should I open this file?" Safe Terminal say NO.
If Apple will change Terminal, for example, to show a warning before executing new shell script, the change code will not be used, because Safe Terminal will still block all files.
To use Apple fix, when and if they will fix this problem, you simply uninstall Safe Terminal.
Reply to This
Thursday, February 23 2006 @ 05:08 PM PST