Burn it, burn it all
-
team solves DARPA Shredder Challenge in just 33 days [^]
Steve _________________ I C(++) therefore I am
-
team solves DARPA Shredder Challenge in just 33 days [^]
Steve _________________ I C(++) therefore I am
Reminds me of an episode of The Pretender where Jarod pieces together a bunch of shredded documents. Can't seem to find a clip online.
Somebody in an online forum wrote:
INTJs never really joke. They make a point. The joke is just a gift wrapper.
-
team solves DARPA Shredder Challenge in just 33 days [^]
Steve _________________ I C(++) therefore I am
More proof that security measures have to be based on the need to protect the material. If a document is sufficiently important that someone might be willing to go to these lengths to reconstruct it, it seems like a better measure than mere shredding ought to be used to destroy it. Shred the document, burn the shreddings, and toss the shredder into the Challenger Deep[^]. This reminds me of the de-classification procedure we were supposed to use for the old 300MB disk packs used on supermini's and mainframes, which went something like this: 1. Write all 0's to all sectors and verify. 2. Write all 1's and verify. 3. Write alternating 55/AA pattern and verify. 4. Repeat steps 1-3 three times. 5. Mechanically disassemble the disk pack into its component platters. 6. Sand-blast the face of each platter. 7. Crush the platters. Given how sensitive these things were to mechanical misalignment in the platters, it would have sufficed to drop the pack from a two foot height off the floor.
Software Zen:
delete this; -
More proof that security measures have to be based on the need to protect the material. If a document is sufficiently important that someone might be willing to go to these lengths to reconstruct it, it seems like a better measure than mere shredding ought to be used to destroy it. Shred the document, burn the shreddings, and toss the shredder into the Challenger Deep[^]. This reminds me of the de-classification procedure we were supposed to use for the old 300MB disk packs used on supermini's and mainframes, which went something like this: 1. Write all 0's to all sectors and verify. 2. Write all 1's and verify. 3. Write alternating 55/AA pattern and verify. 4. Repeat steps 1-3 three times. 5. Mechanically disassemble the disk pack into its component platters. 6. Sand-blast the face of each platter. 7. Crush the platters. Given how sensitive these things were to mechanical misalignment in the platters, it would have sufficed to drop the pack from a two foot height off the floor.
Software Zen:
delete this;Until someone dropped it from 1.9' and the data surivived... There are some fools out there. Anyway, you were being paid by the hour, right?
Don't forget to rate my post if it helped! ;) "He has no enemies, but is intensely disliked by his friends." "His mother should have thrown him away, and kept the stork." "There's nothing wrong with you that reincarnation won't cure." "He loves nature, in spite of what it did to him."
-
team solves DARPA Shredder Challenge in just 33 days [^]
Steve _________________ I C(++) therefore I am
-
team solves DARPA Shredder Challenge in just 33 days [^]
Steve _________________ I C(++) therefore I am
Interesting but not much to do with everyday, ordinary life. I will continue to shred everything and sleep well knowing that no one was interested in the un-shredded documents anyway!
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair. nils illegitimus carborundum me, me, me
-
More proof that security measures have to be based on the need to protect the material. If a document is sufficiently important that someone might be willing to go to these lengths to reconstruct it, it seems like a better measure than mere shredding ought to be used to destroy it. Shred the document, burn the shreddings, and toss the shredder into the Challenger Deep[^]. This reminds me of the de-classification procedure we were supposed to use for the old 300MB disk packs used on supermini's and mainframes, which went something like this: 1. Write all 0's to all sectors and verify. 2. Write all 1's and verify. 3. Write alternating 55/AA pattern and verify. 4. Repeat steps 1-3 three times. 5. Mechanically disassemble the disk pack into its component platters. 6. Sand-blast the face of each platter. 7. Crush the platters. Given how sensitive these things were to mechanical misalignment in the platters, it would have sufficed to drop the pack from a two foot height off the floor.
Software Zen:
delete this;I've just had our MD's disk cut in two with a plasma cutter. That should make it fairly tricky to recover... I hope :~ Andy B
-
More proof that security measures have to be based on the need to protect the material. If a document is sufficiently important that someone might be willing to go to these lengths to reconstruct it, it seems like a better measure than mere shredding ought to be used to destroy it. Shred the document, burn the shreddings, and toss the shredder into the Challenger Deep[^]. This reminds me of the de-classification procedure we were supposed to use for the old 300MB disk packs used on supermini's and mainframes, which went something like this: 1. Write all 0's to all sectors and verify. 2. Write all 1's and verify. 3. Write alternating 55/AA pattern and verify. 4. Repeat steps 1-3 three times. 5. Mechanically disassemble the disk pack into its component platters. 6. Sand-blast the face of each platter. 7. Crush the platters. Given how sensitive these things were to mechanical misalignment in the platters, it would have sufficed to drop the pack from a two foot height off the floor.
Software Zen:
delete this;We had to smash the CRTs of monitors we were getting rid of. Set 'em out out back by the antenna, and toss rocks at them. That wasn't the prescribed method, but it was fun. :)
So I rounded up my camel Just to ask him for a smoke He handed me a Lucky, I said "Hey, you missed the joke." My Mu[sic] My Films My Windows Programs, etc.