Jump to content


  • Content Count

  • Joined

  • Last visited

About Sworddragon

  • Rank
  1. The conclusion based on this would be: - Why one of the erasing options is exposed as being secure (for sensitive data) as it would give the user wrong expectations. - If the secure full erasing should be still enhanced as solving the issues mentioned in the startpost might still make things better.
  2. This is probably less secure than overwriting-only the disc as several fragments are going likely to be big enough to make a forensically extraction possible. In that case I would overwrite the disc first and then destroy it to be more secure. However, this will be more reliable as more secure the overwriting is being performed of course.
  3. Years ago (and retested with the current version of CDBurnerXP) I noticed that using the secure erase option on specific burner/media combinations makes the data track on the disc only a tiny bit more transparent (the last sample is an unformatted DVD-RW). Since the data track is still very good visible I'm wondering if and how reliable data could be recovered especially with better equipment from advanced forensic institutions. On talking about this with another developer of burning software he told me he uses for his application the BLANK command (code A1h) to blank the disc. But he also told me he doesn't know exactly what the drive writes in this mode. I guess CDBurnerXP uses the same command. If so, it is probably not secure for some reasons: - On trying to find some (vendor-specific) documentations the command seems to be described with varying detail. From what I have found some actions performed are described sometimes as optional or some media types can refuse to blank on media which the device thinks is already blank. - To the user blanking reflects a potential undefined behavior while requesting actual data to securely overwrite the disc reflects a defined behavior. To make it clear what this means: Data burning casually on a disc proofs to any user that this action works as expected as the user sees that the data could be written succesfully (besides being a probably more used and well-tested command as blanking) while it is hard to actually verify for a user that full blanking worked successfully leaving more room for drive-specific errorneous/unsecure implementations. If those concerns are more or less true it might make sense to improve the secure erase option to make it more secure. Alternatively options could be provided to choose between different variants like: - Relying on the drives implementation of blanking - Zeroing the disc by explicitly requesting the data to be written from the start to the end - Randomizing the disc by explicitly requesting the randomly generated data to be written from the start to the end
  4. Interestingly my optical drive/Windows XP doesn't seem to have problems anymore with these discs and CDBurnerXP doesn't crash due to this. The event logs were already cleared before but if I'm encountering this problem again I will update this thread with the informations of the event viewer.
  5. With bad luck I got DVD-RW that my optical drive doesn't like. Trying to write anything on it will result in a scsi error. I wanted also to try to burn something with CDBurnerXP on it but because my optical drive doesn't like the media CDBurnerXP got a busy message from Windows after a few seconds (shown in the screenshot). After clicking on OK a few seconds later CDBurnerXP crashed with this information (It seems not to be possible to copy the detailed informations with Windows XP): EventType : clr20r3 P1 : cdbxpp.exe P2 : P3 : 52328ee7 P4 : cdbxpp P5 : P6 : 52328ee7 P7 : 541 P8 : 3f P9 : pszqoadhx1u5zahbhohghldgiy4qixhx Here are some informations of my system and the media: Operating System: Windows XP SP3 CDBurnerXP version: Drive: "vendor 'HL-DT-ST' product 'DVDRAM GH24LS50' revision 'YP02'" Media: "INFOMEDIAA20 , InfoMedia Inc."
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.