Love veracrypt, and
it would be nice if i could
create File-Container without encryption.
I understant this feels like bad idea, but
let say, via cmd-line argument let user to choose
not to use encryption, just make container with a
files system.
Thanks.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
An ordinary windows folder is a container without encryption and you can specify the file system depending on the partition, anyone can see what is in it .
You need to be a lot more specific with what you are trying to do,, otherwise the answer is in the above 2 lines.
Last edit: Philip Smith 2020-02-08
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
VereCrypt for PartitionEncryption and FileContainers
I need FileContainers to group specific files, and
instead of using Folders i need VirtualFilesystems.
It has to do with MFT, and i decided, that is better for my
usage to quick mount/dismount specific container, than
always have VeraPartition mounted.
Plus i prefer to store 15k+ small files per container,
rather per folder, and not clutter the Main MFT.
I am looking at VHD and other solution, but
VeraCrypt for now works best, but it can be even better.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You don't need to encrypt the partition.
On a normal partition you can just make small containers as many as you want depending on partition size.
select the container you want put in password there you have your files.
No one else can see what is in the containers without the password.
To me that sound like what you want to do, if I am wrong advise where?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
A veracrypt container without encryption is basically a folder.
I can't see what you are trying to achieve.
Because if you make a container with a password no one without the password can see what is inside, you put in your password and can modify or do other things with what is inside.
The files as such inside the container are not technically speaking encrypted what is encrypted is where they are.
Now if you have a normal folder with your files in it you can encrypt them BUT every time you modify or change something you then have to delete the old encrypted files and encrypt the newer version of the file, with your password. With a veracrypt container you do not have to re-encrypt anything.
I still can't understand why you want a secure place for things BUT it can't be encrypted?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sometimes i Don't need an encryption, but still
need to use an FileContained filesystem that is
separated from the base drive, and for that
reason i don't need to use folders.
And i now using VC for FileContainers, but
it would be better, if there was an option Not
to use encryption on File based Contained filesystem.
What is your role in VeraCrypt development ?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have no connection to the development of veracrypt.
Personel opinion only - veracrypt is made for security therefore removing the encryption would render it useless for that purpose, even if it was as an option it could lead to problems for some users.
I am sure someone from development has seen your request, so time will tell.
π
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Use windows built in disk/partition manager It can create Virtual Hard Disk (VHD) file and you can create mbr or gpt partition table and fat or ntfs filesystem in that file without encryption google "bitlocker container" for more info and leave out bitlocker part Mounting/dismounting VHD is almost as simple as in veracrypt. https://www.howtogeek.com/193013/how-to-create-an-encrypted-container-file-with-bitlocker-on-windows/
Skip the bitlocker part at the end to not have encryption. You don't need windows pro/enterprise as you don't encrypt it. You don't need 64mb container as you don't encrypt it. Your disk don't get locked when you shut down your computer because it is non lockable=no encryption. You can still hide it by "Eject". Veracrypt is developed for encryption and is not disk manager.
π
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I know why Mox Falder may need that. The best workaround is to create a keyfile, set is as default, and then mount the container without a password (dont forget to check the 'try first to mount with an empty password" checkbox). The result will be the same as having no password at all.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes, it's will simplify, but would be even better, if by option
i be able Not to use the encryption, and then will be no need for
key/pass; Just filesystem in the container menaged by Veracrypt.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
TLDR; Veracrypt has been rock-solid for me. I love and use VC containers as non-system disk drives, which gives me great flexibility in organizing my data, taking backups, copying/moving data in and out, etc. I'd like to have an identically behaving VC container but with option no-password/no-encryption.
I came in here looking to ask this very question the OP asked. Like many, I found VC just after Truecrypt closed down and I've used VC ever since. I have a lot of VC containers to make multiple small "disk drives". Many of my VC containers do not need encryption, there is nothing sensitive being stored in them. If I had the option of no-password/no encryption, I would still want the "password" prompt (maybe as option) when the container mount is attempted at login. But I'd only need to provide the OK or Cancel.
Is something like this option possible?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Firstly, I'd like to extend my appreciation to all of you for taking the time to discuss and provide feedback on this feature request. It's always interesting to see the diverse ways in which users utilize VeraCrypt and the unique requirements they have.
To address the core request: The idea of having a VeraCrypt container without encryption is, at its face, a divergence from the primary aim of VeraCrypt, which is to provide a robust encryption solution. That being said, I understand the use case presented here. Some users are more interested in the file-containment functionality rather than the encryption aspect, especially when dealing with non-sensitive data.
A potential solution, as some of you have pointed out, is to allow users to choose an empty password when creating a volume. Currently, VeraCrypt forbids setting an empty password if no keyfile is used, but it's technically feasible to change this. By doing so, users could mount their containers by simply clicking "OK" without entering any password or selecting any keyfile. This would achieve the effect of having a non-encrypted container while still making use of VeraCrypt's container system.
However, before implementing such a feature, there are a few concerns to consider, primarily around user experience and potential security confusions. It's crucial that users don't accidentally create non-encrypted containers when their intention was to have encryption.
I'll evaluate the soundness of adding such a feature in future releases of VeraCrypt. Again, thank you all for your input and suggestions.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you for considering, my original idea, and
you bring good points, and i think it's best NOT to
introduce that "feature", as it can cause user mistakes
by creating unencrypted container.
Thank you.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
@idrassi, the most logical solution would be to force the user to always create the containers with password, as it is now. Then however, there may be an option to change the password to an empty thing. So nobody will create non-password container by accident.
Last edit: Alex 2023-10-14
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Love veracrypt, and
it would be nice if i could
create File-Container without encryption.
I understant this feels like bad idea, but
let say, via cmd-line argument let user to choose
not to use encryption, just make container with a
files system.
Thanks.
An ordinary windows folder is a container without encryption and you can specify the file system depending on the partition, anyone can see what is in it .
You need to be a lot more specific with what you are trying to do,, otherwise the answer is in the above 2 lines.
Last edit: Philip Smith 2020-02-08
For my usage i need:
Currentyl using:
I need FileContainers to group specific files, and
instead of using Folders i need VirtualFilesystems.
It has to do with MFT, and i decided, that is better for my
usage to quick mount/dismount specific container, than
always have VeraPartition mounted.
Plus i prefer to store 15k+ small files per container,
rather per folder, and not clutter the Main MFT.
I am looking at VHD and other solution, but
VeraCrypt for now works best, but it can be even better.
You don't need to encrypt the partition.
On a normal partition you can just make small containers as many as you want depending on partition size.
select the container you want put in password there you have your files.
No one else can see what is in the containers without the password.
To me that sound like what you want to do, if I am wrong advise where?
To be short:
VeraCrypt Container without encryption.
A veracrypt container without encryption is basically a folder.
I can't see what you are trying to achieve.
Because if you make a container with a password no one without the password can see what is inside, you put in your password and can modify or do other things with what is inside.
The files as such inside the container are not technically speaking encrypted what is encrypted is where they are.
Now if you have a normal folder with your files in it you can encrypt them BUT every time you modify or change something you then have to delete the old encrypted files and encrypt the newer version of the file, with your password. With a veracrypt container you do not have to re-encrypt anything.
I still can't understand why you want a secure place for things BUT it can't be encrypted?
Sometimes i Don't need an encryption, but still
need to use an FileContained filesystem that is
separated from the base drive, and for that
reason i don't need to use folders.
And i now using VC for FileContainers, but
it would be better, if there was an option Not
to use encryption on File based Contained filesystem.
What is your role in VeraCrypt development ?
I have no connection to the development of veracrypt.
Personel opinion only - veracrypt is made for security therefore removing the encryption would render it useless for that purpose, even if it was as an option it could lead to problems for some users.
I am sure someone from development has seen your request, so time will tell.
Making an option for the user to be able
to create FileContainer with fileSystem
without encryption Will extend functionality.
Cheers.
Use windows built in disk/partition manager It can create Virtual Hard Disk (VHD) file and you can create mbr or gpt partition table and fat or ntfs filesystem in that file without encryption google "bitlocker container" for more info and leave out bitlocker part Mounting/dismounting VHD is almost as simple as in veracrypt.
https://www.howtogeek.com/193013/how-to-create-an-encrypted-container-file-with-bitlocker-on-windows/
Skip the bitlocker part at the end to not have encryption. You don't need windows pro/enterprise as you don't encrypt it. You don't need 64mb container as you don't encrypt it. Your disk don't get locked when you shut down your computer because it is non lockable=no encryption. You can still hide it by "Eject". Veracrypt is developed for encryption and is not disk manager.
I'm aware of VHD, and VeraCrypt is more convenient for me to use, so
i rather have noCrypt additional option in VeraCrypt, since i use it everyday.
I know why Mox Falder may need that. The best workaround is to create a keyfile, set is as default, and then mount the container without a password (dont forget to check the 'try first to mount with an empty password" checkbox). The result will be the same as having no password at all.
Yes, it's will simplify, but would be even better, if by option
i be able Not to use the encryption, and then will be no need for
key/pass; Just filesystem in the container menaged by Veracrypt.
TLDR; Veracrypt has been rock-solid for me. I love and use VC containers as non-system disk drives, which gives me great flexibility in organizing my data, taking backups, copying/moving data in and out, etc. I'd like to have an identically behaving VC container but with option no-password/no-encryption.
I came in here looking to ask this very question the OP asked. Like many, I found VC just after Truecrypt closed down and I've used VC ever since. I have a lot of VC containers to make multiple small "disk drives". Many of my VC containers do not need encryption, there is nothing sensitive being stored in them. If I had the option of no-password/no encryption, I would still want the "password" prompt (maybe as option) when the container mount is attempted at login. But I'd only need to provide the OK or Cancel.
Is something like this option possible?
Firstly, I'd like to extend my appreciation to all of you for taking the time to discuss and provide feedback on this feature request. It's always interesting to see the diverse ways in which users utilize VeraCrypt and the unique requirements they have.
To address the core request: The idea of having a VeraCrypt container without encryption is, at its face, a divergence from the primary aim of VeraCrypt, which is to provide a robust encryption solution. That being said, I understand the use case presented here. Some users are more interested in the file-containment functionality rather than the encryption aspect, especially when dealing with non-sensitive data.
A potential solution, as some of you have pointed out, is to allow users to choose an empty password when creating a volume. Currently, VeraCrypt forbids setting an empty password if no keyfile is used, but it's technically feasible to change this. By doing so, users could mount their containers by simply clicking "OK" without entering any password or selecting any keyfile. This would achieve the effect of having a non-encrypted container while still making use of VeraCrypt's container system.
However, before implementing such a feature, there are a few concerns to consider, primarily around user experience and potential security confusions. It's crucial that users don't accidentally create non-encrypted containers when their intention was to have encryption.
I'll evaluate the soundness of adding such a feature in future releases of VeraCrypt. Again, thank you all for your input and suggestions.
Thank you for considering, my original idea, and
you bring good points, and i think it's best NOT to
introduce that "feature", as it can cause user mistakes
by creating unencrypted container.
Thank you.
@idrassi, the most logical solution would be to force the user to always create the containers with password, as it is now. Then however, there may be an option to change the password to an empty thing. So nobody will create non-password container by accident.
Last edit: Alex 2023-10-14
Windows and Linux support disk images. There is really no need to have Veracrypt support non encrypted containers.
https://www.tenforums.com/tutorials/138380-create-set-up-new-vhd-vhdx-file-windows-10-a.html
https://www.linuxandubuntu.com/home/creating-virtual-disks-using-linux-command-line
I guess MacOS can do the same.
And Simple vhd manager.@moxfalder @markus70
https://www.sordum.org/8705/simple-vhd-manager-v1-5/