Technology

59566 readers

4696 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago

MODERATORS

361

OpenAI accidentally deleted potential evidence in NY Times copyright lawsuit (techcrunch.com)

submitted 11 hours ago* (last edited 11 hours ago) by misk@sopuli.xyz to c/technology@lemmy.world

60 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] mosiacmango@lemm.ee 3 points 5 hours ago* (last edited 5 hours ago) (2 children)

It's an option, but not the default. It takes forever to run, so someone using it is being very intentional.

It's also considered wildly overkill, especially with modern drives and their data density. Even a single pass of zeros, the fastest and default dban option, wipe data at a level that you would need a nation state actor to even try to recover data.

[–] Saik0Shinigami@lemmy.saik0.com 9 points 5 hours ago (1 children)

so someone using it is being very intentional.

Not if you're used to taking DoD requests. It was my default for a very long time because I simply defaulted to it for compliance reasons.

It’s also considered wildly overkill

Absolutely is. Doesn't mean that people like me aren't out there in droves.

But SSDs make this all moot and HDD are being phased out of many environments. SSDs with chucking the key is more than sufficient as well.

[–] mosiacmango@lemm.ee 2 points 2 hours ago* (last edited 2 hours ago) (1 children)

DoD dropped it 7 and 3 pass requirements in 2006.

Later in 2006, the DoD 5220.22-M operating manual removed text mentioning any recommended overwriting method. Instead, it delegated that decision to government oversight agencies (CSAs, or Cognizant Security Agencies), allowing those agencies to determine best practices for data sanitization in most cases.

Meanwhile, the U.S. National Institute of Standards and Technology (NIST), in its Guidelines for Media Sanitization of 2006 (PDF), stated that “for ATA disk drives manufactured after 2001 (over 15 GB) clearing by overwriting the media once is adequate to protect the media.” When NIST revised its guidelines in late 2014, it reaffirmed that stance. NIST 800-88, Rev. 1 (PDF) states, “For storage devices containing magnetic media, a single overwrite pass with a fixed pattern such as binary zeros typically hinders recovery of data even if state of the art laboratory techniques are applied to attempt to retrieve the data.” (It noted, however, that hidden areas of the drive should also be addressed.)

For ATA hard disk drives and SCSI hard disk drives specifically, NIST states, “The Clear pattern should be at least a single write pass with a fixed data value, such as all zeros. Multiple write passes or more complex values may optionally be used.”

[–] Saik0Shinigami@lemmy.saik0.com 2 points 2 hours ago* (last edited 2 hours ago) (1 children)

Congrats? DBAN was made prior to 2006... IT people existed before 2006. What's your point? You think that people just spawned into existence in 2006 with decades of IT knowledge? So like I said... "It WAS my default for a very long time because I simply defaulted to it for COMPLIANCE reasons"... eg. my contracts at the time required it and I ran boatloads of wipes.

Regardless... DOD 5220.22-M now states

The National Industrial Security Program Operating Manual (NISPOM) is now Part 117 of Title 32, Code of Federal Regulations.

So let's go look at the NISPOM stuff which says... NOTHING! So what you end up with is companies referencing the old DOD 5220.22-M because old government contracts will actually say that specific document in contracts as something that must be adhered to for a long long time. So even though it "died" on 2006, contracts may not be renewed for some time after that which still keeps the document alive.

Now DOD 5220.22-M actually specified and defines short wipes (3 pass) and long wipes (7 pass). And in theory, could be superceded by NIST 800-88 (and probably is the default on modern contracts). And regardless of all of that... DoD internally has it's own standards, which after wipe often requires degaussing or outright destruction of the disk, I remember having a dedicated device for it that would document serials and stuff. I'd have to pull up my army documents to remember which specific rules required that type of stuff, but I'm not going to dig out shit from 2010 just to argue with someone on lemmy.

So I guess this boils down to... The world didn't spawn into existence in 2006. People are older than 2006 and are allowed to talk about their experiences from before the "old times".

Edit: And in current contracts... all our shit is NVMe and secure erase. But I'm willing to bet muscle memory would still kick in for me if I saw the DBAN screen.

[–] sugar_in_your_tea@sh.itjust.works 1 points 44 minutes ago* (last edited 44 minutes ago) (1 children)

And honestly, if you're going to do a single pass, might as well do multiple. It doesn't take any more of my time for 1 pass vs 7, assuming I only have a handful to do. I'll probably just start one before I leave for the day, swap to another when I come in, and repeat until the pile is cleared.

If something is worth doing, and overdoing doesn't take any extra effort, I'll overdo it.

[–] Saik0Shinigami@lemmy.saik0.com 1 points 19 minutes ago

That was basically the workflow. On smaller drives you could do one when you get in, one at lunch and one before you left. Eventually drives got large enough that it was just once in the morning and once before leaving.

I’ll overdo it.

Half the contracts you didn't know if they wanted the short wipes or long wipes. So you just do long wipes to cover your ass. It's not like there was a rush, it was a simply menial task that became a second nature set of bashing the keyboard. Like typing some of my passwords and pins... I have no fucking clue what they are anymore... but put in front of the keyboard and I can type them by muscle memory.

[–] hemko@lemmy.dbzer0.com 2 points 3 hours ago (1 children)

Okay so what you think is wildly overkill, is about 10% of the effort some organizations go through to make sure data is not restoreable.

[–] mosiacmango@lemm.ee 3 points 2 hours ago* (last edited 2 hours ago) (1 children)

My org shreds discs entirely with a mechanical grinder, so I'm well aware of overkill.

Multiple overwrites being unnecessary isnt really an opinion. Here is the company that owns dban agreeing with security orgs like NIST, that anything past 1 write is unnecessary. .

I think the issue comes down to whether the org in question does that 7 passes consistently on all discs, or if it just so happened to start that policy with those that had evidence on them.

[–] Saik0Shinigami@lemmy.saik0.com 2 points 1 hour ago

I think the issue comes down to whether the org in question does that 7 passes consistently on all discs, or if it just so happened to start that policy with those that had evidence on them.

No? If 1 is sufficient, any additional shouldn't matter in any considerations at all. Could have simply been somebody who hit the preset on accident.