![]() ![]() Which is a simply way to suggest that Bruce, Greenwald, et al. Another line of thought goes like this: If the NSA really really really wants to know WHAT Snowden had access to, and wanted to say, use a tempest solution to grab that information, one way to to that would be to spook someone known to have received those info using psy_ops to persuade that someone to decrypt the entire data from whatever air-gapped machine is on into some other machine. to FINISH their audit just for posterity.ĭ. ![]() Was the original Truecrypt itself an NSA project and the shenanigans yesterday designed to keep people using the 7.1a and earlier versions (assuming there’s some sort of subtle compromise)? Was the change some sort of “dead man’s switch” that was spring loaded by the developer? Whatever the case, the Truecrypt project is now that friend who usually seems like a good guy, but suddenly turned sketchy. The update to to where the truecrypt site is redirected has a much more amateurish quality than the original site. ![]() Of if Bruce pulled this page, sought to deprecate Blowfish/Twofish and instead told everyone “Hey, you should really be using MacGuffin”Ĭ. Almost as if Phil Zimmerman shut down all his web sites and told people to stop using PGP and that they should use something called Bass-o-matic. The endorsement of BitLocker feeds into the later point above. It could also be the modern analog to something like this: ī. Its the sort of thing that would be automated in a development environment for a contractor doing work for the. The odd source code edit where comments referring to “U.S.” had the text altered to “United States” seems noteworthy. In an instance like this, for example, I would suggest trying to mount the backup volume on another machine (before wiping the one the backup is from) to make sure it mounts successfully, and perhaps verifying some of the content while it is mounted there (running a checksum of some of the files there and on the original location and comparing, or perhaps using rsync -dry-run between the two machines, if they can see each other over the network, which would be a relatively efficient way to see if there was any big chunk of the data that looks different or missing on the backup).A. A backup is not a good backup until it has been tested, no matter how recently it was made and what checks were made of the backup system/medium beforehand. You should really have tested the backup after making it, as well as checking the disk for physical problems before hand. If you thought that last paragraph was a little preachy I apologise in advance for the next one. When you say mounting the volume "took a couple of attempts", what happened in response to the failed attempts? Any error message or status information output at all? And what commands did you try (and which eventually got you as far as you are now)? This information might trigger a memory in the mind of a passing truecrypt expert, that could be useful to you! Before trying each recovery method it is recommended that you backup the volume (yes: backup the corrupt volume (the truecrypt file, not the apparently corrupt filesystem within it) in case the attempt makes things worse (so you can go back to the bad-but-not-quite-as-bad state in order to try something else). It might be worth mounting the truecrypt volume under Linux, to see if the filesystem checking tools available there can by some fluke do something the other tools you have tried could not but you are most likely out of luck there too. Unfortunately there is probably very little that you can do. It shouldn't be a bad disk because it's brand new, and I tested it before backing everything up to it. The disk was formatted as NTFS and encrypted using AES and a passphrase. CHKDSK aborted" Windows claims that the disk is "unformatted" but truecrypt see's one partition on it. Windows cannot recover master file table. Windows will attempt to recover master file table from disk. When running CHKDSK, I get the error "Corrupt master file table. I have it mounted now (i.e., I know the password and truecrypt has 'decrypted' it and assigned it a drive letter), but chkdisk cannot do anything with it, windows says I have 0 bytes out of 0 bytes free on the partition, and using the "Fix Disk Errors" option on disk properties results in a "The disk check could not be performed because Windows can't access the disk" Once I managed to mount it, I could not view anything inside of it. Once I reinstalled windows, I managed to mount the Truecrypt partition, even though it took a few tries. I made a complete backup of all my data to it, and wiped my hard drive and reinstalled my operating systems. I have a 2 TB external hard drive that I've encrypted using Truecrypt. ![]()
0 Comments
Leave a Reply. |