Actual/Practical Use: Tomb size #591

Hi Folks,

Before I ask the question implied in the title...

I've been going over the code in this neat little cough script and I can only say DAMN!!! I'm impressed. While there are always things to nitpick (especially if you were starting from scratch) or that may relate to style more than anything else. And there are things in there that I know I never would have thought of (like overwriting the used memory variables when finished).

Very nice indeed.

So a big tip-o-the-hat from this old programming (started prof. in the 1980s)

Now the actual question. From a real practical standpoint how big is too big? I get the 1GB and less use cases. Even the double layering of using a tomb stored on a fully encrypted drive - regardless of if it's on the local internal drive or on an encrypted usb key/drive. Triple layering with a tomb on an encrypted "drive" in a virtual machine sitting on an encrypted drive (and so on....)

But when we talk about the actual size of the tomb itself, I was looking at things I might want to put in a tomb and some of the directories where the info sits on my system contain upwards of 10 or 20 gb worth of stuff - client files, medical data, etc.

This also interacts with how you make your backups. With smaller files it's easier to recover from losing 1 file than an entire directory tree.

You'll notice I'm purposefully avoiding anything related to threat models, deniability, what-have-you. My question is downstream from there.

Thanks