This project has moved and is read-only. For the latest updates, please go here.

Hidden OS write protection

Topics: Feature Requests
Jun 26, 2014 at 1:37 PM
On Truecrypt, when you are on the Hidden OS, you can't write on USB keys and other hard drives for "security reasons" (it's on read only). The problem is, when you have the Hidden OS, your space is /2 and I need more space by using other drives (fully encrypted). I would like to know if you can add a function that can disable this protection.
Also, can we migrate from truecrypt (Hidden OS) to veracrypt without doing a full wipe? (I don't think but maybe)

Jun 26, 2014 at 11:24 PM
Preventing hidden OS leaks is one of the most important feature and this is achieved by forbidding write operations to unencrypted or non-hidden volumes. Adding an option to disable this protection is a bad idea as it will break the hidden OS security model. It can also create issues when the system is hibernated because we can have a filesystem mismatch between the decoy OS and the hidden upon resume.
Anyway, security always comes with a price and in this case the price is loosing storage space.

As for migrating from TrueCrypt, in the case of Hidden OS it is a little bit tricky but feasible. Actually, migrating standard TrueCrypt volumes and partitions is already a feature on the roadmap but we are not sure if we should include it in VeraCrypt or provide it as a standalone tool. These need some work and I can't give any ETA for them. We have to adapt the available coding resources with the list of features that we need to include in future versions.

Jun 26, 2014 at 11:37 PM
Edited Jun 26, 2014 at 11:46 PM
Okay, at this time I use a VM to bypass this but may have a button to mount a crypted volume without the write protection (with all warning for inexperimented users) on the hidden OS will not be a bad idea. I saw a topic but this is now dead.

I also saw that :

Does veracrypt will be ended to create another encryption tool?
Jun 27, 2014 at 8:58 AM
Of course not. As I wrote in forum post that is refereed by this article, the idea is to combine efforts in order for the community to advance quickly the development of key features. Here is the link to my statement :

VeraCrypt is older than the other projects with its own roadmap that is still on track. We have no problem sharing efforts with the others. Moreover, this is necessary if we need to accelerate the development speed since we are talking about free tools that generate no revenue.
Dec 9, 2015 at 2:15 AM
sorry to reopen this thread, but i am wanting to know what I need to do to be able to write from inside a hidden volume. i made a hidden container in another partition and can't write in it even so.