Though, I'm not sure how to actually go about having a separate but still useful storage system,
Exactly. RAID over Internet ? Adding a layer of insecurity in the process (Internet) while destroying performance.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Though, I'm not sure how to actually go about having a separate but still useful storage system,
I hate to say this and offend you, but even you obviously don't know what I'm talking about. You've clearly stated in your wording just like the guys here that you have no clue what I was trying to say, which is yet the simplest thing in the world. It has gone right over head.
Encryption is more than just "A = Z, B = Y, ... Y = B, Z = A". It takes a mix of all sorts of data and combines them in mathematically reversible ways. So a file may not be split across the drive in an array, but the information needed to decrypt it very likely will be. If you keep the drives separated, that gives you more time to destroy at least one drives worth of data making it virtually impractical to ever recover anything on the drive that might be compromised. Though, I'm not sure how to actually go about having a separate but still useful storage system,
Encryption is more than just "A = Z, B = Y, ... Y = B, Z = A". It takes a mix of all sorts of data and combines them in mathematically reversible ways. So a file may not be split across the drive in an array, but the information needed to decrypt it very likely will be. If you keep the drives separated, that gives you more time to destroy at least one drives worth of data making it virtually impractical to ever recover anything on the drive that might be compromised. Though, I'm not sure how to actually go about having a separate but still useful storage system,
Striping doesn't improve security at all. You think if the NWO Soros Eugenics Fluoride Goons can get your first disk, they'll somehow be unable to get your second disk?
If you have a small Word doc with all of your account numbers on it, written to an encrypted striped array... Most of that is on one disk, encrypted or not.
Even if it's an internet iSCSI RAID0 and you manage to have your accomplice trash the other disk, that means they only get half of the data when they waterboard you for the passphrase. It doesn't increase the security of your data set.
In the case of AES block size is 128-256 bits. Far below stripe width. Are they doing something else to make the encryption blocks larger?
Striping doesn't improve security at all. You think if the NWO Soros Eugenics Fluoride Goons can get your first disk, they'll somehow be unable to get your second disk?
If you have a small Word doc with all of your account numbers on it, written to an encrypted striped array... Most of that is on one disk, encrypted or not.
Even if it's an internet iSCSI RAID0 and you manage to have your accomplice trash the other disk, that means they only get half of the data when they waterboard you for the passphrase. It doesn't increase the security of your data set.
In the case of AES block size is 128-256 bits. Far below stripe width. Are they doing something else to make the encryption blocks larger?
The block size maybe 128 bits, but I was talking about where the key to decrypt it, or the algorithm that generates the key permutations that encrypted it is stored.
You're lost buddy. Thus I have no desire to explain it to you and your arrogance.
In the case of rotating disks they may have some success interrupting the power. With SSDs you may be able to issue a TRIM for the whole disk. Forensics people have complained about SSDs continuing to erase when power is later attached to the drive for copying operations:There is secure erase builtin to the drive but that would take hours and need power.
The X axis shows time and the Y axis shows the approximate percentage of the drive that has been zeroed out. In all three SSD runs, around 160 seconds from the log-in time (i.e. around 200 seconds from power-on), the SSD begins to wipe the drive. After approximately 300 seconds from log-in, the SSD consistently appears to pause briefly before continuing. 350 seconds after log-in, the SSD’s pre-existing evidence data has been almost entirely wiped.
In the case of most XTS implementations the key is stored in RAM. Dropping a drive in a RAID0 array is a separate issue. If your decryption algorithm isn't stored on the encrypted stripe set, then what does breaking the array offer? You might lose the salt but that's 50/50 at that point.
Make claim that is criticized by myself who has my head up my ass for being ridiculous and implausible.
Claim that everyone but yourself is ignorant and arrogant.
Perhaps you would like to take part in the discussion.
Perhaps you'd like to get your head out of the box and be open to learning before opening your mouth.