Hiding sensitive data using encryption plus MicroSD cards

All you need-
•MicroSD card
•Encryption program with plausible deniability features and keyfiles
Old versions of Truecrypt have both of these. I don't know about DMCrypt and other Linux programs.

A 64-128GB MicroSD card is very handy for storing large amounts of data you don't want people getting into.
Use your encryption program to encrypt the entire device.
The WAY you encrypt is important for security. In Truecrypt, use all three available AES protocols. Use RIPEMD-160 as your Hash algorithm.
If you're making a hidden volume inside your standard one(and of course you are, stupid!), you want to reverse the order of your AES methods.
For example, if you use "AES-Twofish-Serpent" to encrypt the outer volume, use "Serpent-Twofish-AES" on the hidden one.
The key for the outer volume should be much easier to brute force than the hidden volume key. This ensures that, if anyone manages to try to force your volume open, they will decrypt the outer volume first without knowing about the hidden volume. And unless you say otherwise, they won't be able to know.
What you put in your outer volume is important. It should be legal or quasi-legal, but bad enough to look like you'd wanna hide it from eyes.
Bestiality porn, MLP porn, rape fetish shit, anything that appears fucked up but is not actually illegal. Give them a red herring.
Make sure, when creating your volumes, to randomly move that mouse pointer when it tells you, for at least 30 seconds to be safe.

As far as your passwords go, a good idea of how to do it is provided-
Outer volume key-
"78OnioN03*vira1d34TH" without quotes
That's just convoluted enough to be hard to crack and look secure and easy to remember so you can give it up after feigning resistance for a while.

Hidden volume key-
5H^mQ%3N6Ks!9d$lW4P8#?aQw4B7~0SovV4@\1<s%3c?X2+FO6
That's 50 random characters, using CAPITAL and lower case letters, numbers 0-9, and symbols.
26+26+10+32 standard symbols. 94 total characters available JUST on the keyboard.
To give you an idea of how strong that can make a password, a standard numeric password of 4 characters using 0-9 equals 10000 different combinations.
Using the above 94 characters, a simple 2-character-long password(94x94) has 8836 possible combinations. Add one more character making a 3-character-long pass and you get 830,584 possible combinations just from a 3-long code.
TEN characters long? That's 53,861,511,409,489,970,176 possible combinations. Many orders of magnitude can be had.
Basically, it's impossible to brute force a key like this even with every super computer on the earth and every other computer running through keys.

It's not known whether quantum computers can/will be able to crack AES encryption.
But it should be noted that governments around the globe still use AES.
If the government is hot enough on you to warrant using quantum computers they probably don't have, it would be easier for them just to infect your machine with a keylogger or some other hidden program that phones home your dealings, and there's probably not much you're going to do to
stop this anyway. Not unless you know a way to detect their trojans. Keeping an eye on all of your network transfers, logging every bit and byte, can help with this.

Your local or state authorities aren't going to be able to run ops like that though, so unless you become PE#1 you're likely safe.

Now then, it's time to talk more about that long randomized password. Obviously, unless you're some kinda freak, remembering that beast will be impossible.
However, encrypting it is not, and such a process is very effective at obfuscating the password and making it impossible to know what it is.
So, let's say you have the above 50-character-pass there, and you wanna save it for easy copy-pasting. But you don't want your password out there open and naked.
So you clothe it. Like this-

1. Take the code [ 5H^mQ%3N6Ks!9d$lW4P8#?aQw4B7~0SovV4@\1<s%3c?X2+FO6 ]

2. Paste it into an encoder, like Base64, Binary, Hex, ASCII85, etc. This is done by using tools on the internet to change shit up. So for example, we'll tave [ 5H^mQ%3N6Ks!9d$lW4P8#?aQw4B7~0SovV4@\1<s%3c?X2+FO6 ] and turn it into a Base64 string- [ NUhebVElM042S3MhOWQkbFc0UDgjP2FRdzRCN34wU292VjRAXDE8cyUzYz9YMitGTzY= ]

3. These can be stacked almost like a password made up of passwords, so we go and take the above Base64 and turn it into Ascii85- [ <~:/tt=@TGp69e\CZ;_q-]:KLD/@Rai]<CCJ7:bkL<A9q-@:,=_N<AHQi<bbMu=@>S;@sM(#=
aE)29ke]><-h\1~> ]

4. You can do this as many times as you feel, and all you have to remember is the order in which you encoded your original key.
Ex-
"ENCODED - Base64, Hex, Base64, Ascii85, Hex, Ascii85"
would be
"DECODED - Ascii58, Hex, Ascii85, Base64, Hex, Base64"

Using this, we can obtain the following-
Original - 5H^mQ%3N6Ks!9d$lW4P8#?aQw4B7~0SovV4@\1<s%3c?X2+FO6
Turned into Base64- NUhebVElM042S3MhOWQkbFc0UDgjP2FRdzRCN34wU292VjRAXDE8cyUzYz9YMitGTzY=

Turned into Hex- 4e5568656256456c4d30343253334d684f57516b624663305544676a50324652647a52434e33347755323932566a5241584445386379557a597a39594d697447547a593d

Turned into Base64- NGU1NTY4NjU2MjU2NDU2YzRkMzAzNDMyNTMzMzRkNjg0ZjU3NTE2YjYyNDY2MzMwNTU0NDY3NmE1MDMyNDY1MjY0N2E1MjQzNGUzMzM0Nzc1NTMyMzkzMjU2NmE1MjQxNTg0NDQ1Mzg2Mzc5NTU3YTU5N2EzOTU5NGQ2OTc0NDc1NDdhNTkzZA==

Turned into Ascii85- <~:.J;=:/k@Q:23ca9kmZ`:./);=aEt]9mT*O:..g%:/jr69mT]Q:24Dq>&%%n:/jY;=__)b:
./5?9mTNX:/k4I:./5@:2NES9gh^$:./5>9kmfb:,56m9kmOO:.J<19mTMf:3pD):/jr59mUT
$9kmZ`:2NES9kmOM:/kj[:..r69mUG-9mU;,:/k4L=]ABY:,57a:K1=O:.J/::K1gX:./SH:.
/W+:/l"T>!Y;7~>

Turned into Hex- 3c7e3a2e4a3b3d3a2f6b40513a32336361396b6d5a603a2e2f293b3d6145745d396d542a4f3a2e2e67253a2f6a7236396d545d513a323444713e2625256e3a2f6a593b3d5f5f29623a0d0a2e2f353f396d544e583a2f6b34493a2e2f35403a324e45533967685e243a2e2f353e396b6d66623a2c35366d396b6d4f4f3a2e4a3c31396d544d663a337044293a2f6a7235396d55540d0a24396b6d5a603a324e4553396b6d4f4d3a2f6b6a5b3a2e2e7236396d55472d396d553b2c3a2f6b344c3d5d4142593a2c3537613a4b313d4f3a2e4a2f3a3a4b3167583a2e2f53483a2e0d0a2f572b3a2f6c22543e21593b377e3e0d0a

And finally
Turned into Ascii85- <~1Li@T1LW%M1gr1L1Lr:M11iFR1b^dA1LW'p1G^pF2DI!J2I\RT2.8Bs1LW%M11i:%1L`.N2
DI$G2`*C&1H@@(2)I's1hJOP11`4P2E*BK1LW%N2ISO"1H%$L2In[%2.SR!1LW'p1GgpF2_d+
"1,^mF1,Ut$1LW%N2ISI'1L`.N2.e^X1-%6J1LVtJ0OZ_J11i="1M/F'2In[%1hAO(1LW%N2I
\I!1c[@#11`4Q1Gq!C1LW'p1hAL$2)@$K2E*NR2.\O"1LW%M11i="1M&@&2I\RT2E!HK1LW%K
1GpsH2InU(2I\RT1hJRV1LW%M1gr1M1GL[G2In[%1h8L&1LW'q2_['F1-%.!11iFQ2_m0H1H@
@(2)R6J0OukG1,LdI2I\RT2.8Bs1LW'p1hAL$2)@$K2I\RT1hJRT1LW%N2I\RQ2.A@M11`4P2
_m0I1H@@(2)R3L11W1$2In[&1L`+L1LW%N2I\I!1h/=P2.SNu1bppK1LW%K1GpsI2DI!r1h&6
q1Lr=S1LW%M1gr.O1LW(J1h&6q2E*KQ1LW%M11iC"1cR:"11`.M0OZ_K2)d:"1LW%N2IeKt2)
I+#1,1XH1L`.!2e=dV0OukG~>


So what we end up here with is, a way to store your password openly, safely, without any pesky authorities being able to know its true form.
And that last code can be divided up and hidden in various text files if you're really paranoid.
Say, one text file for every three lines.

You have this final code saved in a text file for easy copy pasta into decoders, and save the text file on a MicroSD card that can be hidden almost anywhere.
Another benefit of MicroSD is how easy it is to destroy them or even swallow them in an emergency.
They're the best security option for the would-be miscreant.
Finally, a tip about the law. If you're hiding something this tightly locked up, chances are it's data that can get you put in prison for a LONG time.
In any jurisdiction in the Anglosphere, you should probably refuse to give up your password even under threat of jail.
Likely, a charge of "obstruction of justice" or "contempt of court" or "evidence tampering" or whatever the pigs try to toss on you will be far less serious than the charge you get for whatever you have sealed up.
Those sex-offender registries are brutal, as is prison time. It's very hard to prove a serious crime without solid evidence. Even if the 5-0 has evidence you were transferring illegal materials, they won't have much of a case without contraband actually in your possession.