Timeline for Shortest code to secure wipe a disk
Current License: CC BY-SA 3.0
24 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 30, 2018 at 7:13 | vote | accept | MathuSum Mut | ||
| Oct 30, 2018 at 2:36 | answer | added | user36046 | timeline score: 2 | |
| Oct 29, 2018 at 21:06 | vote | accept | MathuSum Mut | ||
| Oct 30, 2018 at 7:13 | |||||
| Oct 29, 2018 at 17:25 | answer | added | user36046 | timeline score: 2 | |
| Oct 29, 2018 at 8:25 | answer | added | Jason | timeline score: 1 | |
| Oct 29, 2018 at 7:49 | vote | accept | MathuSum Mut | ||
| Oct 29, 2018 at 21:06 | |||||
| Oct 28, 2018 at 17:13 | answer | added | William Shipley | timeline score: 3 | |
| Oct 7, 2016 at 6:38 | comment | added | Winny | On Linux, one can set up a file as a disk, partition it, and formats the partitions, and go from there. These utilities do not care if they are accessing block devices or simple files. The same goes for FreeBSD (and I'm certain it is possible in other BSD's and OSX). | |
| Aug 7, 2016 at 11:17 | history | edited | MathuSum Mut | CC BY-SA 3.0 |
deleted 96 characters in body
|
| Aug 4, 2016 at 14:15 | comment | added | Peter Taylor | The referenced standard is for wiping "real" disks (i.e. ones with discs of magnetic material in them). To securely wipe an SSD (or an SD card) you have to get access to the CPU in the disk itself which controls which sectors are available, because otherwise wear levelling means that you can't guarantee that the writes are covering the full address space. | |
| Aug 4, 2016 at 14:01 | review | Close votes | |||
| Aug 4, 2016 at 19:12 | |||||
| Aug 4, 2016 at 13:48 | comment | added | MathuSum Mut | I would argue otherwise. This challenge asks for code that promotes privacy and information security. | |
| Aug 4, 2016 at 13:45 | comment | added | AdmBorkBork | I'm voting to close this question as off-topic because this challenge asks for malicious code. | |
| Jun 18, 2016 at 17:29 | comment | added | MathuSum Mut | It does not matter what drive you do it on, as long as I can use the same generic code and run it on a popular operating system. | |
| Jun 18, 2016 at 15:52 | comment | added | nanofarad | What assumptions, if any, can we make on the interface of the SSD if we are doing this on an FPGA? Can it be a simple SPI flash that is sufficiently fast to operate with single clock cycle turnaround? | |
| Apr 15, 2016 at 16:17 | comment | added | MathuSum Mut | Try it on a flash drive or something you don't use. | |
| Apr 15, 2016 at 12:16 | comment | added | Michelfrancis Bustillos | Really want to try and tackle this...also really don't want to sacrifice my HDD to test it. | |
| Apr 13, 2016 at 0:04 | history | tweeted | twitter.com/StackCodeGolf/status/720039878671605760 | ||
| Apr 4, 2016 at 0:41 | comment | added | R. Kap | Seriously, what did your SSD do to you to deserve this kind of treatment? Did it kill your entire teddy bear collection or something? | |
| Apr 3, 2016 at 17:25 | comment | added | cat | The problem with that link is that there are links on that page to "free" software but said "free" software isn't actually open source | |
| Apr 3, 2016 at 15:46 | history | edited | MathuSum Mut | CC BY-SA 3.0 |
deleted 59 characters in body
|
| Apr 3, 2016 at 15:46 | comment | added | MathuSum Mut | Good point :-/. | |
| Apr 3, 2016 at 15:16 | comment | added | DJMcMayhem | I doubt this will get any answers because of how hard it will be to test. | |
| Apr 3, 2016 at 11:41 | history | asked | MathuSum Mut | CC BY-SA 3.0 |