Ticket #330 (closed defect)

Opened 5 years ago

Last modified 4 years ago

False identification of compressed/encrypted/sparse files

Reported by: DavidHB Owned by: Joel
Priority: critical Milestone: Eraser 6.0.8
Component: Core Version:
Keywords: Cc:
Processor Architecture: x64 (64-bit) Blocked By:
Blocking: Operating System:

Description

This ticket arises from the thread "Problem shredding compressed file" on the Eraser Support forum. In a post timed Fri Mar 05, 2010 4:17 pm, Joel stated, "But the files itself aren't, so I don't understand why this is happening either. could you set up a Trac ticket for me to investigate this? ". This was in response to the following statement by DavidHB, "What caught me was that the files were not compressed, but the folder they were contained in was"

Blocking

IdSummaryMilestone
#330False identification of compressed/encrypted/sparse filesEraser 6.0.8

Blocked by

IdSummaryMilestone
#330False identification of compressed/encrypted/sparse filesEraser 6.0.8

Change History

comment:1 Changed 5 years ago by Joel

  • Owner set to Joel
  • Status changed from new to accepted
  • Priority changed from major to critical
  • Component changed from BlackBox to Core
  • Milestone set to Eraser 6.0.7

comment:2 Changed 5 years ago by Joel

  • Status changed from accepted to pending

I've done these steps, and the problem doesn't seem to manifest itself.

  1. Create a new folder, "New Folder"
  2. Create file A (can be anything), and copy the file A, to Copy of A (within the same folder)
  3. Right-click on "New Folder", Properties, Advanced, and check "Compress contents..."
  4. When asked whether to apply on the folder only or both folder and subcontents, select subcontents
  5. Unset the compressed attribute on A
  6. Erase "New Folder"

The result is that A is erased, Copy of A isn't, which is the expected behaviour.

What gives?

comment:3 Changed 4 years ago by trac-robot

  • Status changed from pending to closed

This ticket was closed automatically by the system. It was previously set to a Pending status and hasn't been updated within 14 days.

Note: See TracTickets for help on using tickets.