[ The milestone is likely inaccurate on this ticket. I don't know, because DBAN committed suicide. ]
DBAN will happily nuke a writable boot medium from which it was started (like the 16GB thumbdrive I had 25 setup hours in, which I lost this afternoon, and which will cost me at least as many hours to recover, if I can at all); this behaviour, while understandable, still seems suboptimal in the extreme, particularly given how common a thread it forms through reports of people doing it to themselves.
You can recategorize this as an RFE, or you can close it WONTFIX... but it would be good if you were on record that you don't care how many people blow their heads off with it, regardless of how much you believe that's the users' fault.
This really seems like something you should change about autonuke's behavior, unless there really is no way to detect it, which would surprise me greatly.
At the very least, it would seem not to violate the functional expectations of autonuke if it displayed the list of things that would be nuked, and gave a 10 second abort countdown.
Appears the current version, 2012.02, has a prevention measure for this issue.
Last edit: David McNeill 2014-08-01
http://sourceforge.net/projects/dban/files/dban/dban-2.2.8/
2012.02, Release November 22nd, 2013:
....
- "nousb" option added in autonuke mode (in auto mode USB sticks/hdds will not be erased).
....