I never knew about even half the stuff kmfkewm posted here. Good go, mate! Thanks for sharing all this knowledge with us.
I feel a bit stupid that I never knew about the possibility of using chroot like this, since I use it daily for other purposes.
I know OpenbSD has a modified version of chroot that offers decent isolation, but many distros are probably still using versions with chroots that can be broken out of fairly easily. Look into the security of chroot on your distro.
Even with disk encryption, if they want to crack it they will.
Welcome to the 'says a bunch of bullshit' club, if you are using a strong encryption algorithm like AES or Serpent with a 128 or 256 bit key, nobody is going to be cracking it. These symmetric encryption algorithms are even highly resistant to quantum computing attacks that are able to break asymmetric algorithms like RSA (which is often used for session key exchange with GPG). An attacker with a quantum computer with enough stabilized qubits can use Shors algorithm to quickly break this sort of asymmetric encryption, but the best known quantum computer attack against symmetric algorithms is grovers algorithm and it only reduces key size by 1/2 (giving a 256 bit symmetric algorithm the still unbreakable key space of 2^128). Even 128 bit symmetric keys are going to be unbreakable by such quantum computers. And anyway it is likely that nobody currently has any quantum computer with such capability, and if anyone does it is the NSA and they are sure as fuck not going to reveal that they have such abilities by using them against you.
Most of the time frame quotes you here about encryption like "it would take them over a thousand years to brute force that" are bullshit. Those time scales estimations are routinely based on trying to crack the encryption using cpu power. While this does get the job done eventually, the future is in using GPU computing(using your video card's processing power).
GPU does have more processing power for cracking things like encryption than the average CPU does but you still are not going to brute force shit when it comes to strong encryption, even with a large cluster of GPU power.
It's the same hashing method used in the bitcoin protocol itself. When people solve a block, all they have done is generate hashes until one of them matched the transactions that were being verified. Anyone who has ever mined bitcoins can tell you how much faster a GPU can do this when compared to a CPU. Depending on the encryption scheme and the efficiency of the hashing code, it can cut the time needed to crack an encrypted volume by several orders of magnatude. This makes encryption just one part of a layered defense scheme. To rely on it alone is foolish.
If GPU is so powerful then bitcoin is fucked because it relies on algorithms that could then be brute forced, or even the keyspace of the hashing algorithm it uses would be exhausted. You are right that it is foolish to rely on encryption alone, but your reasons for why it is foolish are even more foolish.
This brings me to my original point. VMs have their image files running off of the hard drive most times, so once the volume is decrypted, they can just load the VM up in its normal software and have access to everything in it.
You are entirely missing the point of using a virtual machine for isolation. What you are doing is protecting from an attacker who remotely hacks / roots your VM using whatever network facing applications run in it as the vector. If an attacker does this and you use a virtual machine to isolate the exploited applications, the attacker can not trivially get to the host system from their position in the virtual machine.
Even worse is that you can manipulate the data in a VM's image file without loading it up and completely bypass all access controls and system permissions.
Sure, if you have access to the host OS. Again, you are entirely misunderstanding the benefits of using virtual machines.
So knowing this, what I did was invest in a device called a ramdisk. How does this help? Well RAM don't hold data after the power cuts out. If you VM is stored and run from a ramdisk, when the police show up, you just pull the plug and no more data for them to screw you with. I have my rig interfaced with a garage door remote on my keyring. One button push and my rig cuts off and all the data in the ram disk goes bye bye.
The RAM can be flash frozen for a significant period of time after power is cut, although the exact time frame depends on the specific sort of RAM.
Sorry but it you who is wrong.
I do not know if all RAM can be flash frozen, but I know a lot of it can. I also know different sorts have different data decay rates. However, considering the fact that you have already demonstrated willingness to talk out of your asshole instead of your mouth, I am inclined to think you have no idea what you are talking about. Please show me a citation.
There's only one type of DRAM chip used for actual computer RAM and it is stateless without power being supplied to it.
This I know is not correct, cold boot attacks have been demonstrated against several different sorts of RAM. It is a fairly common misconception that RAM is stateless without power being supplied to it, but it has been demonstrated with several sorts of RAM (all tested afaik) that state decay is not instant upon power being cut, taking as long as ten plus minutes in some cases. I believe this sort of attack was first shown by Jacob Appelbaum.
The actual "memory" in your computer is not like NAND memory used in usb sticks and flash drives. Data stored in NAND is in a persistent state until until altered and requires no power to hold data once it is written. Actual RAM holds nothing persistently.
You obviously have some understanding of computers, but your understanding is that of a 'computer guy' not a 'security expert'. It is a common misconception that RAM instantly loses its state upon power loss, but security professionals have demonstrated and proven that this is not true several years ago now.
This is why RAM constantly has to have the data refreshed every few nanoseconds. Freezing the ram with liquid nitrogen would do absolutely nothing as the only thing moving in the ram is electrons.
Please stop saying as fact things that you have no real idea about. Yes, you are technically correct that the only thing moving in RAM is electrons, however freezing the RAM with liquid nitrogen (or other things, some of which are far easier to work with) will indeed make the state of the electrons persist in RAM for an extended period of time. It also takes a substantial period of time, usually a few minutes, before the state of the RAM decays after power is cut.
It takes quite a bit of time to reach absolute zero (the point at which atoms stop moving as well as their components such as electrons) even using liquid Helium. So lets see here. Power goes off and data is GONE in lets say 25 milliseconds.
Why are you wasting your time making shit up and talking about things you don't know about? Let's try to keep the information here high quality and accurate instead of pulled out of our assholes please.
If the feds have people who can somehow alter the laws of physics and timespace I'm sure we would have heard about it by now so it's not even logical to expect human or machine to be able to remove a physical ramdisk device in that timeframe.
Your entire hypothesis is incorrect so you should stop basing your argument off of it.
On top of that, even liquid hellium could not cool it down fast enough to stop the electrons from dissipating before that data was gone forever. And let's not forget that you'd be shorting out the device by submerging it into Liquid Helium(i keep using helium because liquid nitrogen can't freeze electrons in place so is useless for the scenario you mentioned). So whoever told you that line of bullshit needs to go back to school and get their MS in Comp science as I did and would know what they were speaking about.
Blah blah blah more wrong information. This attack has been demonstrated, you can see the entire thing carried out on youtube for fucks sake not to mention the attack has been in published papers for a few years now. Any computer security should know about this attack by now, so maybe it is you who should go back to school in computer security instead of unrelated computer science fields.
Let's also point out the fact that all modern operating systems use memory address randomization to help counter buffer overflow attacks in poorly written software. Even if by some miracle the data got preserved in ram, once the OS is off there is no way to tell what bits were places where in RAM. All that would be left is jumbled masses of binary values with no real way to correlate them to what they belong to. 16 gigabytes = 17 179 869 184 bytes so if you think anyone could solve that jigsaw puzzle then I've got a really nice bridge in SF I'd love to part with very cheaply.
Not all modern operating systems use ASLR (freebsd comes to mind) and many of the operating systems that use any ASLR do so to a limited extent (thus not having full ASLR). Well, you know the key size of encryption is 128 bits of randomness or 256 bits of randomness, so I guess you could just filter out everything that isn't random and then make a dictionary of all 128 and 256 bit strings of randomness that are left. ASLR doesn't randomize the content of ram it randomizes where data is stored in RAM. Stop talking out your asshole.
Also forgot to respond to this. The registers in your cpu hold data exactly as long as RAM cells do man. They also have to be refreshed like RAM or they also lose their data.
This is true. The only way I have heard of protecting from a cold boot attack when the attacker actually has physical access to the machine is to use encapsulation material to slow their ability to access the RAM, and intrusion detection systems to begin a wipe process in RAM as soon as physical penetration of the case is detected. Even systems that use encapsulation material and similar systems for protecting RAM have been defeated by military hackers, I read about one hacker who worked for the united states government using a combination of I believe liquid helium and an acid wash to remove the encapsulation material from flash frozen RAM, and then he used a highly precise tool with a tip on it about the width of a human hair to obtain the state of the memory. Sorry I can't explain this attack in more technical detail, it is beyond my level of expertise, but I will try to find the article.
Seriously, pick up a book and actually read up on this.
Given the large amount of bullshit that you have said I think you have no place in lecturing other people on reading up on anything.
Also you're arguing with someone with a masters in computer science based on shit you read on fucking wikipedia? You just served yourself son. I can cite thousands of goverment papers and studies claiming weed is as addictive as heroin and causes everything from crime sprees to phsycosis. Does that make them true? Hell no because even idiots get bullshit papers published. The things I've stated here come from actual learning, hands on experience working in this field, and basic damn common sense when it comes to the laws of physics.
If you have a masters in computer science I really am impressed with myself that I have managed to become self educated past the point of a masters degree so quickly! It really is hard to determine my skill level considering that fact, but I routinely do find myself pwning the shit out of anyone who has recieved their computer/security training from a school or corporation. He is basing his argument about RAM on a paper / attack discovered by Jacob Appelbaum, a well known security professional and one of the Tor developers. You really have pwnt yourself very hard if you are not trolling.