I don't know what you mean by erasure-coded. I am only talking about
storing something the size of a private key - say, 2K - on three other
laptops. Your own private key would be 2K and you would, on average, have 3
other keys - a grand total of 8K average. Not going to break the back of
even the
Hi,
During the Sugar meeting today we talked about how to handle backup
and restore in the case where there is no school server or network.
Here are some of our thoughts:
* We should backup journal objects only, possibly with compression.
The USB disks being used for backup won't be huge,
On Tue, 2008-02-19 at 13:08 -0500, Chris Ball wrote:
* Encryption/privacy probably isn't desirable here -- we're dealing with
objects that the user has chosen to have backed up.
The Bitfrost spec refers to this as a primary backup. It is
inevitable, since in the case of hardware failure, any
* We could use the favorite flag, or a new backup flag, to signify
which jobjects the user would like to back up, and we can try to
accomodate them. We probably still need a per-user quota.
...
* Encryption/privacy probably isn't desirable here -- we're dealing with
objects that the
On Feb 19, 2008, at 3:32 PM, Jameson Chema Quinn wrote:
That's a separate issue - at the simplest, you just store the
encryption key on the first backup and only manually thereafter; a
more complicated scheme, for implementing later, would break it into
5 parts of which any 3 would
5 matches
Mail list logo
