Re: [vox-tech] Secure Wiping hard drives

2012-05-12 Thread Rick Moen
Quoting Brian Lavender (br...@brie.com):

 I would think that writing zeros to the disk would make the data
 unavailable in many cases and is relatively fast. IIRC, DBAN takes
 multiple passes with pseudorandom data. 

 What if the fact that a melted disk leaked information? 

Yeah, you go tell LLNL's Security Office that they don't know their
business.  Let us know how that works for you.

 Personally, I would go one step further and use a pseudo random feed
 from AES with Cipher Block Chaining (CBC) and perhaps throw some salt
 in the middle so that it isn't too predictable.

Really, because data are so much better hidden by overengineered
pseudorandom data than by, e.g., 'All work and no play makes Jack a dull
boy' over and over.  Sure, that makes all kinds of sense.  In some
universe.

___
vox-tech mailing list
vox-tech@lists.lugod.org
http://lists.lugod.org/mailman/listinfo/vox-tech


[vox-tech] C++ problem

2012-05-12 Thread Richard Harke
I'm working on a small C++ program. In one of the constructors I
create a local pointer variable
with double * var = new double [size]  I later return the memory with
delete [] var
Immediately after the delete I find that some of the class's private
variables have been over written. The variables are ok just before the
call to delete.

Does anyone have any ideas about this??

I'm running debian squeeze and the compiler is gcc 4.4.5
Also I did an apt-get upgrade this morning to pick up any fixes.

Richard Harke
___
vox-tech mailing list
vox-tech@lists.lugod.org
http://lists.lugod.org/mailman/listinfo/vox-tech


[vox-tech] C++ problem

2012-05-12 Thread Richard Harke
My last post seems to have gotten lost so I'll try again.

I'm working on a small C++ program. In one of the constructors I
create an array with
double * var = new double [size]   After use, before exiting the
constructor I return the memory with delete [] var  But after return
from the delete, several private class variables are written over.
I have checked that these variables are correct just before the delete
call and are modified right after. Does anyone have any idea what is
going on?

I'm running debian squeeze for amd64  with gcc 4.4.5 This morning I
did an apt-get upgrade to be sure I had any recent fixes.

Richard Harke
___
vox-tech mailing list
vox-tech@lists.lugod.org
http://lists.lugod.org/mailman/listinfo/vox-tech