{5} Accepted, Active Tickets by Owner (Full Description) (12 matches)

List tickets accepted, group by ticket owner. This report demonstrates the use of full-row display.

Joel (12 matches)

Ticket Summary Component Milestone Type Created
Description
#278 Implement the Executor as a Service Core Eraser 6.1/6.2 task 12/15/2009

When using a service, get the service to assign task IDs and task progress can be queried by anyone with the correct permissions.

These features need to be implemented:

  • Users can manage their own task list
  • The executor engine will run with the permissions of the user who created the task
  • Logging will be done through the Windows Event Log, with the exception of Task logging which will remain to be logged on the task
#299 Don't run the Eraser process in the background User Interface (UX) Eraser 6.1/6.2 defect 1/8/2010

When I use eraser 6 a "tsr" icon, near the clock, appear. Eraser 5.8.8 was more "stealth" ... Why Eraser 6 "publicize" the process?

I love the "deniable plausibility" of version 6 but in embarassing to use in my office whith the boss around! :-)

#418 ObjectDisposedException when viewing the log as erase tasks execute User Interface (UX) Eraser 6.0.11 defect 3/13/2012

As detailed in ​the forum.

#70 Cleaning up of privacy leaks Core Eraser 6.1/6.2 enhancement 11/30/2008

temporary internet files, etc. Think open-source CCleaner

From ​http://eraser.wiki.sourceforge.net/Eraser+v6

#74 Pause erasures Core Eraser 6.1/6.2 enhancement 11/30/2008

​http://eraser.wiki.sourceforge.net/Eraser+v6

#83 Upgrade Remote Executor classes Core Eraser 6.1/6.2 enhancement 12/6/2008

The current Remote Executor classes only allow task addition and deletion, but the other functionality like events and other functions are not implemented like the DirectExecutor? class. The ideal implementation will allow clients to use the RemoteExecutorClient? class like it was doing DirectExecutor? now.

#210 Eraser not deleting very long filenames, round 3 Core Eraser 6.1/6.2 enhancement 6/1/2009

Follow-up to #41 and #135

I understand that handling of NTFS long filenames is not available in .NET, however, so it can't be fixed+forgotten, but the problem it creates is major _and_ there might be a workaround.. so please re-consider :)

Additions to the problem:

  • MSN file sharing and IE can easily create too long filenames, so the problem may be pretty common
  • On my PCs, erasing around too long filenames actually crashed Eraser, with only indirect hint (fragment of current filename string)
  • Even free space deletion crashes
  • The crash closes the parent process - even if it was explorer.exe
  • Crashing is not a way for a GUI programme to respond to an issue in the wild, IMO :)

Suggestion:

  • Catch exceptions around the erasing, (optionally?) skip on error and report it in the end
  • Even better, check for filename length (on NTFS of course) and explicitly report
  • Even better, move+rename the file to %TEMP% before processing, and restore afterwards (if needed). Not failproof (not sure about open files) + has a time window where power loss is problematic, so making it an option might be a good idea.

Using Eraser v5.84, Windows XP SP2, NTFS.

#277 Eraser Unified File Manager Core Eraser 6.1/6.2 task 12/15/2009
#355 Implement feature-complete CLI User Interface (UX) Eraser 6.1/6.2 task 4/22/2010

Implement a CLI for Eraser, usable in a batch script. Thus, we need to include a wait parameter so that when calling eraser erase, the program will not exit immediately but will wait for the erasure to complete before exiting.

We also need to refactor the code, ensuring that only one global TrueValues? property exists so that all clients will get the same values for true, and a common CLI will be presented (see Eraser.DefaultPlugins/ErasureTargets/ProgressArgument)

#147 Ballast File Creation. Core Eraser 6.1/6.2 enhancement 1/4/2009

I think it would be a great feature for Eraser V6 to enable the user to make ballast files.

A ballast file is a file that is used by Eraser users to fill up free space on a very large hard drive so regular free space erasures can be performed in much quicker time as the ballast files reduce the free space on the disk.

This would also help Truecrypt users with plausible deniability (yes I am still banging on and on about that !).

How it would work.

A user would have say a 500GB disk. Say 50GB was used with OS and some storage. If this user wishes to wipe his free space he would have to wipe 450GB of free space and also presumably the cluster tips of the first 50GB.

This would obviously take a long time and it would add considerable wear to the drive. In order to help the user Eraser should have an option to create ballast files.

The user should be able to open Eraser, click the “Create Ballast File” button and be presented with a new window.

Within this new window there should be an option to choose how many ballast files to make, a drop down ballast file size KB,MB,GB, a naming prefix (which could be left blank in which case a random name will be created) and to which drive they are to be saved.

The ballast files should be created with Erasers CSPRNG pass as this will help the Truecrypt plausible deniability feature as a truly random output from Eraser should be no different to a Truecrypt volume.

So as for the example above the user would perhaps select the following settings.

10 x 40GB files. (This would take up the bulk of the free space, the 40GB chunks can be deleted when a lot of drive space needs releasing).

4 x 10GB files. (This will enable fine tuning when only a small amount of free space is required at a later date).

So the user has created 440GB of ballast files reducing the free space to erase to only 10GB plus cluster tips.

Truecrypt users can claim their Truecrypt volumes are actually Eraser ballast files so there is no volume.

Thoughts Joel ?

#239 Add shortcut to the "erasure progress window" in systray. User Interface (UX) Eraser 6.1/6.2 enhancement 10/2/2009

This feature would have a similar functionality like that of the Windows 7 Network systray icon.

Clicking the Eraser systray icon once, would open the progress window of the current erasure. Clicking it again would close the window.

If possible, a double-click on the icon should open the main window GUI. If not possible a shortcut to the main window GUI could be added to the progress window, similar to the way the Windows 7 Network icon, has a shortcut implemented to the Network Center.

#385 Use of tool tips in the task editing dialog User Interface (UX) Eraser 6.1/6.2 enhancement 10/26/2010

A change has already been implemented in version 6.1, to replace the file paths (almost always truncated) of the items to be deleted in the task editing dialog with the file names only. This has greatly improved readability, but users have no access to the file path from the dialog. In the dialog, tool tips should therefore be used to show the full path of individual file and folder entries. It is suggested that this proposed improvement be implemented in version 6.2; accordingly the baseline used for comparison is the current (at the time of writing) 6.1 build (6.1.0.2258).

Note: See TracReports for help on using and creating reports.