Ok so basically I'm wondering about true crypt . I want to know about the good the bad and the dam right nasty. Any horror stories, say with drives getting corrupted, unable to access your own data when you know your password , when you don't know your password. When you have accidentally changed something and messed it up, or alternatively when everything works perfectly.

Basically I want to know is it good, is it bad and more importantly why?

PS: Oh and I want to know if this is compatible with cloud services e.g. Sugarsync

Thanks!

Oh and i'm a new member if you didn't know

Dani AI

Generated

Short summary for the thread: TrueCrypt was a solid, widely used tool in 2012, but its official distribution and support ended abruptly on 28 May 2014 and the project was marked “not secure” on the official pages. An independent community audit (Open Crypto Audit Project / iSEC + follow‑ups) found no deliberate backdoor but did highlight real weaknesses and maintenance issues; the community moved to maintained forks such as VeraCrypt. (arstechnica.com)

Clarifying risks that aren’t always obvious from the replies by , and : encrypted volumes can become effectively irrecoverable if a header is damaged or the password/keyfiles are lost. Modern forks (and the old tools) provide a “backup volume header” and hidden‑volume protection features—create external header backups and store them offline, and use the hidden‑volume protection option when relevant. Also, mounting a container while a cloud client is syncing (or when two machines mount the same container) is a leading cause of corruption; the safest pattern is to dismount before sync resumes or pause sync while mounted. (veracrypt.io)

Cloud compatibility (SugarSync and others): storing a file‑hosted container in a synced folder will work, but behavior depends on the provider. Some services use block/delta sync (so only changed parts are uploaded), others reupload entire files and may create conflicted copies—both affect reliability and bandwidth. For cloud workflows, per‑file client side encryption (Cryptomator, rclone crypt, etc.) is usually safer and far more cloud‑friendly than single huge container files. (cloudwards.net)

Practical checklist (compress into a workflow): prefer a maintained fork (VeraCrypt) over original TrueCrypt; use a strong password + PIM or Argon2id where available; create and securely store external header backups (and a rescue disk for system volumes); never mount a synced container on multiple devices simultaneously; pause syncing while mounted or use per‑file encryption for cloud use; test restores regularly. These steps address the “good, bad and damn nasty” scenarios described in the thread without guessing at your exact setup. (veracrypt.io)

Recommended Answers

All 2 Replies

TrueCrypt works on a drive (HD, USB, floppy), so I doubt it will work with a service (since you have to run/install it). Personally, I never had any problems with it. If your drive becomes corrupted, then yes, it may happen that you lose the data, but that's why they invented backup software. What did happen to me once, is that I forgot my password. There is no way for recovery if that happens. In my case, since it contains sensitive files, I'd rather lose them completely, then lose them to someone.

Truecrypt doesn't change the backup equation, just some constants in the equation.

The software itself works fine, as far as I can tell, and it's as convenient as conceivably possible.

If by "cloud services" you're referring to networked drives that live in the cloud, it should be compatible with those, in the worst case you can have a TrueCrypt volume stored in a file (unless it's assuming it could access direct i/o on the storage device).

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.