If you're referring to the "cryptographic key" people have been posting, it isn't one (FBMD = Facebook metadata). People like to jump to conclusions too quickly.
There is no certainty behind the reason for the "Q" IG post, though it could very likely have been triggered by the same deadman switch that would send out all of the data he claimed to have had.
To that last question: If anyone were to find it BEFORE something happened to him, it wouldn't be "insurance". You'd want it under lock and key for use when the "time was right".
If you're referring to the "cryptographic key" people have been posting, it isn't one (FBMD = Facebook metadata). People like to jump to conclusions too quickly.
There is no certainty behind the reason for the "Q" IG post, though it could very likely have been triggered by the same deadman switch that would send out all of the data he claimed to have had.
To that last question: If anyone were to find it BEFORE something happened to him, it wouldn't be "insurance". You'd want it under lock and key for use when the "time was right".
Sure.
But what better way to throw them off the track than to make people believe the "encryption key" is long?
Wouldn't any attempted hack skip over using just one simple letter, and the files remain encrypted?
Not a bruteforce method using standard and non standard dictionaries.
Ridiculous.
Data is data and you can copy it infinitely.
81TB is nothing.
Any organization that has compute resources doesn't even blink at 81 TB files.
You may be right. But why encrypt this kind of evidence? It likely includes child porn, of which possession is a felony.
Exactly.