Created
January 23, 2012 21:22
-
-
Save sc68cal/1665597 to your computer and use it in GitHub Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Date: Mon, 07 Feb 2011 21:28:53 -0800 | |
From: Colin Percival <[email protected]> | |
To: "Sean M. Collins" <[email protected]> | |
Subject: Re: Tarsnap 1.0.29 | |
User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.16) | |
Gecko/20101220 Thunderbird/3.0.11 | |
Hi Sean, | |
On 02/07/11 21:18, Sean M. Collins wrote: | |
> The inclusion of tarsnap-recrypt is a huge relief. The timing of the | |
> security issues had put me in a tough position: the most recent 8 months | |
> out of 3 years of backups were stored using tarsnap. Few enough months | |
> that I was considering leaving the service entirely, while at the same | |
> time being enough to leave a pretty big hole in my archives. | |
> | |
> Thank you. I am glad I do not have to make that kind of tough decision. | |
Yeah, this is why I wrote tarsnap-recrypt -- I started it as soon as I got | |
tarsnap 1.0.28 out, and it took longer than I expected due to needing to | |
take care of edge cases (e.g., checkpointed archives, inconsistent cache | |
directories, etc). | |
Let me know how much bandwidth you use running tarsnap-recrypt and I'll | |
credit your Tarsnap account for it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment