From: Florian Philipp <lists@binarywings.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Secure Cloud Backup
Date: Tue, 03 Jan 2012 02:16:00 +0100 [thread overview]
Message-ID: <4F0256D0.2050906@binarywings.net> (raw)
In-Reply-To: <CA+hid6EBM0QKqqPEQ_RBzzo5WL5K6pkZ5X3Lb7XHwVSZ1qYOVg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2045 bytes --]
Am 02.01.2012 22:50, schrieb James Broadhead:
> I have a pile of files, and a personal svn repo totalling around 13GiB
> which I want to back up to cheaply to 'the cloud'. I would also like
> it to be non-trivial for someone with access to the cloud servers to
> decrypt my data.
>
> I have a 50GB free account for Box.net, but would consider others if
> they have significant advantages. The box.net account is only allowed
> upload files of max 100MiB at a time.
>
> Now one problem facing me is that most cloud services don't give
> assurances of bit parity, so I'd like to be able to recover most of
> the files if I lost my local copies and there were bits missing from
> the uploaded backup. This makes the one-big-encrypted-file approach a
> no-go.
>
> My current approach is to use split-tar, with the intention of
> encrypting each file separately. (Is this worse / equivalent to having
> one big file with ECB ? )
I could be wrong but I don't think you will find any reasonable
encryption tool that only offers encryption equivalent to ECB. The
number of files should not matter as the encryption tool can use a
randomized IV with CBC.
> http://www.informatik-vollmer.de/software/split-tar.php
> ...but this seems to have difficulty sticking below the 100MiB
> individual file limit (possibly there are too many large files in the
> svn history).
>
Why not split them further when the files are still above the 100M limit
after splitting them with that tool? split + cat should do the trick.
> Any thoughts? I'm sure that many of you face this problem.
>
Well, I have no experience with their service (although I always planned
to use them), but maybe you can try these guys [1]. They don't have file
size limits and support everything working over ssh (including sshfs) as
well as duplicity for file encryption. Of course, having only US
locations could be a no-go depending on your legal
considerations/restrictions.
[1] http://www.rsync.net/
Regards,
Florian Philipp
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2012-01-03 1:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-02 21:50 [gentoo-user] Secure Cloud Backup James Broadhead
2012-01-03 1:16 ` Florian Philipp [this message]
2012-01-03 19:08 ` Doug Hunley
2012-01-03 1:27 ` Pandu Poluan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F0256D0.2050906@binarywings.net \
--to=lists@binarywings.net \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox