Yes. Version 2.2 (and later) of Permanent Eraser runs natively on Intel and PowerPC based Macs.
Yes. This was a new feature introduced with Permanent Eraser 2.3.
Yes, resource forks are erased.
Yes, aliases can be erased if they are in the Trash.
Yes, before the file is unlinked, the original file name is renamed with a random set of characters to make it even more difficult to discover the former name of the file.
Permanent Eraser 2.2.3 introduced a feature where a dialog box would appear once the application had launched. This warning gives the user the option to either quit or continue with the program. To prevent this warning from appearing, hold down the Option key when launching Permanent Eraser.
To make this setting permanent, open up the General Preferences and uncheck the Warn before erasing option.
Permanent Eraser 2.4 (and later) offers a feature in the warning dialog to suppress this warning. Click the "Do not show this message again" checkbox and the warning will be disabled.
Yes. Go to the General Preferences and uncheck the Play sounds option.
At this time, Permanent Eraser cannot shred the free space on a disk. If you have Mac OS 10.4 or later, you can use Disk Utility to erase the free space on your drives.
Due to the differences in how flash-based drives read and write data (versus traditional magnetic media hard drives), it is not recommended to use Permanent Eraser or any other traditional hard drive wiping method on flash-based drives. At this time, there does not seem to be a reliable method via software to erase data from flash-based drives. The best advice is to encrypt your drive, which can help provide some measure of protection for your data.
However, if Permanent Eraser that a file is located on a SSD, the file will only be erased once to prevent unnecessary overwriting.
This is a known issue with Permanent Eraser 2.5.3 which can be resolved by upgrading to the latest version of Permanent Eraser. Permanent Eraser has been updated for the Mac App Store which resolves the problem encountered with macOS Sierra.
Technical details: This issue was caused by Apple removing the
srm utility from macOS Sierra, which is a necessary component for Permanent Eraser to run. Later versions of Permanent Eraser included a custom version of
srm, so the application is not dependent upon the operating system to provide this utility.