3 ms·
A possible approach would be: keep the data encrypted, just decrypt it at the endpoint. Tarsnap for example does that. Or keep the keys on servers that are acti
by Xylakant 12y ago
A possible approach would be: keep the data encrypted, just decrypt it at the endpoint. Tarsnap for example does that. Or keep the keys on servers that are acting as proxies and decrypt the data. Or actually loose all data on door opening. Just drop it and use a replication like backblaze and S3 use. A harddrive lost? Allocate a shard somewhere else. A unit looses enough harddrives to require service? Just pull it, trash it, plug in a new one.
Given that the units are spread out further than servers in a datacenter, you probably want that anyways. Your service teams don't want coordinate access to the device, drive there and the homeowner does not show up for something as mundane as an HDD swap.
- valarauca1 12y agoLikely extreme mirroring + no keys actually kept on the unit. They just store N byte chunks of data which a master somewhere fetches an decrypts at its leisure would be the best approach. (with key value pairs stored on that said machine). Best approach not necessarily being the one that was put into production. The fastest approach would be to store your key value pairs encrypted on the host device, and do your map/reduce functions locally so you only forward relatively useful data.
- scott_karana 12y agoThe rack is for asynchronous, data-heavy loads. I doubt "storing unencryptable data on a slow pipe" fits with that goal :)