Jeffrey J. Kosowsky wrote:
>
> As I proved in my earlier post, the chance of a collision on even a
> Petabyte sized pool is about 1 in 10^38.
Note that we've all gotten used to trusting tcp crcs for error detection
and it's probably much weaker.
However, it would still be disturbing to realize that your backup
integrity could be compromised by anyone with access to the files.
Consider a scenario where a disgruntled employee who still has access to
files first prepares the 'evil twin' file with the hack to force an md5
value and puts it somewhere that the backup system will find it. Later
he makes the matching alteration to critical files in a way that doesn't
break normal use. Then he waits for any backups of the unaltered data
to expire, then destroys the working copies and leaves.
Assuming it's your job to restore a working copy, what happens next?
--
Les Mikesell
lesmikes...@gmail.com
------------------------------------------------------------------------------
OpenSolaris 2009.06 is a cutting edge operating system for enterprises
looking to deploy the next generation of Solaris that includes the latest
innovations from Sun and the OpenSource community. Download a copy and
enjoy capabilities such as Networking, Storage and Virtualization.
Go to: http://p.sf.net/sfu/opensolaris-get
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
