search for: shredded

I've got an old RAID that I attached to a box. LSI card, and the RAID has 12 drives, for a total RAID size of 9.1TB, I think. I started shred /dev/sda the Friday before last... and it's still running. Is this reasonable for it to be taking this long...? mark

Hi, I have a wishlist item. Is there an appropriate place for me to post it? Basically, I would like to know that my email isn't recoverable from the local disk on the mail server after I delete it. So instead of just deleting the file from my Maildir, I'd like the option to exist for Dovecot to shred it.. Ie, overwrite the file with random data and/or null bytes before deletion. In the

Hi, if we were to use shred to delete a file on a gluster volume, will the correct blocks be overwritten on the bricks? (still using Gluster 3.6.3 as have been too cautious to upgrade a mission critical live system). Cheers, Kingsley.

On 11/08/2017 11:36 PM, Kingsley Tart wrote: > Hi, > > if we were to use shred to delete a file on a gluster volume, will the > correct blocks be overwritten on the bricks? > > (still using Gluster 3.6.3 as have been too cautious to upgrade a > mission critical live system). When I strace `shred filename`, it just seems to write + fsync random values into the file based on

...rote: >> Anyone have any clues about how to sanitize a dead SSD? We haven't had it >> yet, but we're sure it's coming. Esp. since I'm a federal contractor, a >> dead disk gets deGaussed, but what the hell do you do with a SSD? >> > > SSD disks must be shredded as the data has been written over multiple > sectors many times to 'even the writes'. This allows for even a 'dead' > disk to be disassembled with 'off-the-shelf' equipment to extract > items from the dead places. Depending on the data involved, there may > be di...

Anyone have any clues about how to sanitize a dead SSD? We haven't had it yet, but we're sure it's coming. Esp. since I'm a federal contractor, a dead disk gets deGaussed, but what the hell do you do with a SSD?

Greetings all, I am curious if anyone knows why utilities such as 'GNU shred' (part of coreutils) and 'wipe' say they are not effective on journalled file systems- especially EXT3. Is it because you can't "guarantee" that the journal has been flushed/wiped (i.e. you have the journal 'between' you and the actual data blocks on the physical disk), or because

On Wed, 31 May 2017, m.roth at 5-cent.us wrote: > I've got an old RAID that I attached to a box. LSI card, and the > RAID has 12 drives, for a total RAID size of 9.1TB, I think. I > started shred /dev/sda the Friday before last... and it's still > running. Is this reasonable for it to be taking this long...? Unless you specified non-default options, shred overwrites each

On 05/31/2017 08:04 AM, m.roth at 5-cent.us wrote: > I've got an old RAID that I attached to a box. LSI card, and the RAID has > 12 drives, for a total RAID size of 9.1TB, I think. I started shred > /dev/sda the Friday before last... and it's still running. Is this > reasonable for it to be taking this long...? Was the system booting from /dev/sda, or were you running any

...to sanitize a dead SSD? We haven't had it >> > > yet, but we're sure it's coming. Esp. since I'm a federal contractor, a >> > > dead disk gets deGaussed, but what the hell do you do with a SSD? >> > > >> > >> > SSD disks must be shredded as the data has been written over multiple >> > sectors many times to 'even the writes'. This allows for even a 'dead' >> > disk to be disassembled with 'off-the-shelf' equipment to extract >> > items from the dead places. Depending on the data inv...

On 5/31/2017 8:04 AM, m.roth at 5-cent.us wrote: > I've got an old RAID that I attached to a box. LSI card, and the RAID has > 12 drives, for a total RAID size of 9.1TB, I think. I started shred > /dev/sda the Friday before last... and it's still running. Is this > reasonable for it to be taking this long...? not at all surprising, as that raid sounds like its built with

James Szinger wrote: > Disclaimer: My $dayjob is with a government contractor, but I am speaking > as private citizen. > > Talk to your organization's computer security people. They will have a > standard procedure for getting rid of dead disks. We on the internet > can't > know what they are. I'm betting it involves some degree of paperwork. > > Around

John R Pierce wrote: > On 5/31/2017 8:04 AM, m.roth at 5-cent.us wrote: >> I've got an old RAID that I attached to a box. LSI card, and the RAID >> has 12 drives, for a total RAID size of 9.1TB, I think. I started shred >> /dev/sda the Friday before last... and it's still running. Is this >> reasonable for it to be taking this long...? > > not at all

On 5/31/2017 10:13 AM, m.roth at 5-cent.us wrote: > If I had realized it would run this long, I would have used DBAN.... For > single drives, I do, and choose DoD 5220.22-M (seven passes), which is > *way* overkill these days... but I sign my name to a certificate that gets > stuck on the outside of the server, meaning I, personally, am responsible > for the sanitization of the

On 5/31/2017 12:46 PM, m.roth at 5-cent.us wrote: > Not dealing with "secret", dealing with HIPAA and PII data. And*sigh* > Homeland Security Theater dictates.... We run all used disks through a shredder before surplusing any systems, and we are just a manufacturing company dealing with internal corporate IT stuff. the shredder is a truck from a 'data destruction'

On 31/05/17 21:23, John R Pierce wrote: > On 5/31/2017 12:46 PM, m.roth at 5-cent.us wrote: >> Not dealing with "secret", dealing with HIPAA and PII data. And*sigh* >> Homeland Security Theater dictates.... > > We run all used disks through a shredder before surplusing any systems, > and we are just a manufacturing company dealing with internal corporate > IT

On Tue, 2018-05-08 at 15:46 -0400, Stephen John Smoogen wrote: > SSD disks must be shredded as the data has been written over multiple > sectors many times to 'even the writes'. This allows for even a 'dead' > disk to be disassembled with 'off-the-shelf' equipment to extract > items from the dead places. Depending on the data involved, there may > be di...

Hi, I need to securely wipe out a disk on a remote machine, but I don't have access to that machine. Therefore I cannot use the LiveCD+shred (or dd) combination. Besides manually shreding known data files, I am wondering if there is a (free) tool that can be used in my case. Thanks.

...exit 1 + else + printf " %s successully unpersisted\n" $f + fi fi fi fi @@ -550,17 +574,26 @@ remove_config() { # WARNING: file is shredded and removed # ovirt_safe_delete_config() { - if grep -q " /config ext3" /proc/mounts; then - for f in "$@"; do - if grep -q " $f ext3" /proc/mounts ; then - umount -n $f - fi - # unregister in /config/files us...

John R Pierce wrote: > On 5/31/2017 10:13 AM, m.roth at 5-cent.us wrote: >> If I had realized it would run this long, I would have used DBAN.... For >> single drives, I do, and choose DoD 5220.22-M (seven passes), which is >> *way* overkill these days... but I sign my name to a certificate that >> gets stuck on the outside of the server, meaning I, personally, am