[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Manually 'obliterating' some nodes from a repository

From: Karl Auer <kauer_at_biplane.com.au>
Date: 2006-01-19 00:03:54 CET

> I've just stumbled into a problem I really never thought I would.
> I'm in the need of 'obliterating' some files that pose a privacy concern on some
> of my clients. I need to remove every trace of the content of this files; I
> don't care if the nodes survive the wiping off, but I need them 'cleared'.

This isn't an answer to your question, but is related.

Don't forget that you also need to remove the offending information from all your backups. If you back up to unerasable media, you will need to copy to an erasable medium, remove the information from the copy, and write a new backup. Remember that all the backups need to be treated or destroyed - unofficial, temporary, off-site, hot and cold.

If your repository backups are separate, you could just modify your repository now, then when you are sure everything is OK, take a new set of backups. Distribute them to the normal backup locations, and when they've arrived safely, simply destroy all the backups from 9 months ago up until now. That's risky, because you can't really be *sure* everything is OK :-)

A (probably better) solution than all that is to make a written agreement with the client to place all your backups from 9 months ago until now in escrow until they are out of date, then modify your repository to remove the offending material.

Regards, K.

Karl Auer (kauer@biplane.com.au)                   +61-2-64957160 (w/h)
http://www.biplane.com.au/~kauer/                  +61-428-957160 (mob)
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jan 19 02:28:22 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.