Eraser6

Page42 · Post by **Page42** » Wed May 30, 2012 2:35 pm

Somebody remind me again, what is the problem with Eraser6 and SBIE?
They don't cooperate well together, as I recall.
Has that changed?
Anybody using Eraser6 with SBIE successfully?
Thank you

Guest10 · Post by **Guest10** » Wed May 30, 2012 3:01 pm

I'm not using v6, but it works with Sandboxie Control now.
tzuk had to revise the "%SANDBOX%" variable in the command line, to "%SANDBOX\\%" so that it works.
That's done for you when you navigate to the eraser.exe file using:
Sandbox Settings > Delete > Delete Command > "Eraser-6" button

Page42 · Post by **Page42** » Thu May 31, 2012 12:48 pm

Thanks, Guest10.
I'll be installing that soon, I believe.
I miss having Eraser in the context menu. It's not there for me with 5.3 in Win7, despite having it enabled in preferences.

w0lfrun · Post by **w0lfrun** » Fri Jun 01, 2012 4:13 pm

Page42 wrote:Somebody remind me again, what is the problem with Eraser6 and SBIE?
They don't cooperate well together, as I recall.
Has that changed?
Anybody using Eraser6 with SBIE successfully?
Thank you

I'm currently using eraser 5.7 with over write of 7 passes. Page, if you're going to install eraser 6.0 would you give us some feedback as to how it's working for you as to, say speed of deletion etc.. Thanks.

Guest10 · Post by **Guest10** » Fri Jun 01, 2012 6:37 pm

If I remember the numbers correctly, Sandboxie Control uses a DeleteCommand= setting for Eraser that specifies 3 passes to overwrite the files in the sandbox.
However, when using Eraser in Windows, the default could be the 35 pass method - and that is definitely overkill. Be sure to open the Eraser program's window and check the options for the erasing method. Personally, I would choose 1 pass of random data for the overwrite. It's all that you need, and anything else is just a waste with today's hard drives.

Also, if you have a sandbox on a solid state drive or a flash drive, you would be better off using the standard RMDIR (ReMove DIRectory) method of deleting files in sandboxes, to avoid shortening the life of the drive.

Page42 · Post by **Page42** » Sun Jun 03, 2012 12:15 pm

w0lfrun wrote:Page, if you're going to install eraser 6.0 would you give us some feedback as to how it's working for you as to, say speed of deletion etc.. Thanks.

Yes, I'll definitely post back with some findings after I get 6 installed.
Right now I've been bumping into other things that need doing, so 6 keeps getting pushed further down the list.
I am bugged, however, by the puzzling lack of erase in the right-click menu, and that will eventually propel me into installing 6, i'm sure.
FWIW, I have 5.3 running currently with 3-pass erase selected on Win7 and lightening fast would be an understatement.

Page42 · Post by **Page42** » Sun Jun 03, 2012 11:05 pm

Guest10 wrote:I'm not using v6, but it works with Sandboxie Control now.
tzuk had to revise the "%SANDBOX%" variable in the command line, to "%SANDBOX\\%" so that it works.
That's done for you when you navigate to the eraser.exe file using:
Sandbox Settings > Delete > Delete Command > "Eraser-6" button

So, I installed Eraser 6.0.10.2620.
Shell integration is now working, which has me pleased.
But I think something is not right when i select Eraser 6 in the Delete Command feature.
Here is the path I am getting...
"C:\Program Files\Eraser\Eraser.exe" addtask --quiet --method=ecbf4998-0b4f-445c-9a06-23627659e419 --schedule=now --dir="%SANDBOX\\%".
It seems to work okay (in Chrome), but when I configured my other sandboxes (IE9, FoxIt Reader, Outlook 2010) to use Eraser 6, all of a sudden I find I have scheduled tasks and IE keeps erasing something (I have no idea what at this point, but I keep getting a balloon popup saying the task is completed.
And I haven't even opened IE, and the last time I closed them the contents were securely deleted then!
It's very weird.
I know I haven't explained this very well, so let me start by asking folks if the path I posted above looks correct, and if not, what should it be?

Guest10 · Post by **Guest10** » Mon Jun 04, 2012 9:55 am

Page42 wrote:Here is the path I am getting...
"C:\Program Files\Eraser\Eraser.exe" addtask --quiet --method=ecbf4998-0b4f-445c-9a06-23627659e419 --schedule=now --dir="%SANDBOX\\%".

Yes, the Delete Command looks correct.
I installed Eraser6 in XP, not Win 7, and it didn't add any default Scheduled Tasks in Control Panel.
I'm not sure why you refer to IE erasing something, unless you mean that Eraser is deleting items in the sandbox used for IE.
That would occur after something used the IE sandbox, and auto-delete is turned on.

Page42 · Post by **Page42** » Mon Jun 04, 2012 2:40 pm

Okay, forget 6. I removed it.
Trying your old stand-by, 5.8.8.
But when I try to navigate to the eraser folder in order to set the delete command in SBIE, it has the file named eraserl pre-filled out in the SBIE search box, and to the best of my knowledge, there is no eraserl file in 5.8.8.
Sigh.
What did you do in this case?

w0lfrun · Post by **w0lfrun** » Mon Jun 04, 2012 3:49 pm

"C:\Program Files\Eraser\Eraser.exe" addtask --quiet --method=ecbf4998-0b4f-445c-9a06-23627659e419 --schedule=now --dir="%SANDBOX\\%".
It seems to work okay (in Chrome), but when I configured my other sandboxes (IE9, FoxIt Reader, Outlook 2010) to use Eraser 6, all of a sudden I find I have scheduled tasks and IE keeps erasing something (I have no idea what at this point, but I keep getting a balloon popup saying the task is completed

@Page, I had the same problem minus Chrome which I don't use, and I am in XP pro SP3. Finally got tired of "monkeying" around with the 6.0 and reverted back to 5.7 and it works like a charm. "If it ain't broke no need to fix it. "

Page42 · Post by **Page42** » Mon Jun 04, 2012 4:02 pm

Hi w0lfrun
Yeah. 6 was a hassle as far as deleting IE9.
5.8.8 would be fine, it has the right-click menu that was for some reason missing for me in 5.3, but I just need how to figure out the configuration path for delete.
That is, it's easy to navigate to the eraser5.8 folder, but the eraserl file (that SBIE seems to be asking for) is not there.

Guest10 · Post by **Guest10** » Mon Jun 04, 2012 5:06 pm

Look in Windows\System32
I copied it to the Eraser Program Files folder, so it's in both for me.

w0lfrun · Post by **w0lfrun** » Mon Jun 04, 2012 5:19 pm

Page42 wrote:Hi w0lfrun
Yeah. 6 was a hassle as far as deleting IE9.
5.8.8 would be fine, it has the right-click menu that was for some reason missing for me in 5.3, but I just need how to figure out the configuration path for delete.
That is, it's easy to navigate to the eraser5.8 folder, but the eraserl file (that SBIE seems to be asking for) is not there.

I was about to suggest that also, to look in system 32 for 5.8.8 for the eraserl file. Anyway as I said I am using 5.7 and the eraserl file is in program files and it works well for me. You can get it here if you are interested -http://www.oldapps.com/eraser.php?old_eraser=1

Page42 · Post by **Page42** » Mon Jun 04, 2012 11:41 pm

Thanks you guys for the windows32 folder heads up.
The file was there and I copied it and pasted it into the eraser folder.
But now it seems that deletion just is not working right for me at all.
The SBIE Control icon in the systray shows a continuous red X upon deletion, sometimes for many, many minutes, whereas when I started this endeavor, eraser5.3 was working and only taking a few brief seconds to delete the sandboxes.
(I only moved to a newer version of eraser for the context menu feature, which I did eventually get with every version of eraser after 5.3.
But at what a cost!)
Now I have lost my ability to perform secure deletion... even when reverting to what initially worked--- 5.3!!
If I recall correctly, even RMDIR and SDelete are causing the red X to hang.
When this happens, if I open SBIE window and click on delete sandbox, it says there is nothing to delete, and yet SBIE keeps trying to delete because I get popups saying deletion failed.
I have tried installing SBIE 3.7 again (over top without uninstalling), but that didn't change anything.
Very frustrating.
Deletion is all screwed up.
I will search the forum for any possible answers. Maybe I should start another thread?
I'm experiencing this on Windows 7 64-bit system and I am using Experimental Protection.

Guest10 · Post by **Guest10** » Tue Jun 05, 2012 8:35 am

This is on XP, not Win 7:
The default Sandboxie Delete Command for (v 5.8.8 ) EraserL specifies Dod_E (3 passes) as the erasing method to use.
I created a sandbox and copied 46.4 MB of files in it, just to get an idea of what difference it makes if a different erasing method is specified.
Dod_E: 32 seconds
Random 1: 25 seconds
vs. RMDIR (Windows non-secure delete) method: 2 sec.
Most of my sandboxes use RMDIR.
RMDIR should not cause the red X in Control's icon to show for very long at all.

Using SDelete can be a problem since your first run of SDelete.com must be inside a command window, so you can agree to the End User License Agreement (EULA). Otherwise the deletes you make from Sandboxie Control will appear to hang, because Sandboxie will hide the window that asks you to agree to the EULA. After that, it will work OK - except that I wasn't able to get SDelete v1.6 to work right. I use SDelete v1.51 for one of my sandboxes.

BTW: When using Eraser in Windows (Eraser.exe not EraserL.exe) the default erase method is Gutmann 35 passes.
This is absolutely, totally, without-a-doubt, a complete and utter waste.
Open Eraser from the Start menu and choose:
Edit > Preferences > Erasing > Pseudorandom Data 1 Pass

Sandboxie Support

Eraser6

Eraser6

Re: Eraser6

Re: Eraser6

Eraser6

Who is online