Thanks. So the p/w is imbedded in the file?
I think if he just insalls VC, opens it, then uses the ‘select file’ and "mount’ it won’t be too difficult.
NO.
I would text them the pass word, telephone it. or use an encrypted phone app like Telegram Messenger.
That’s not what I meant. Can I take that file to my other computer, then use VC on that machine to open the file?
If so, the mount pw is within the file. If not, then where is the p/w kept?
For example, I send them excel files all the time. They are all pw protected, and sons can open them because I told them the pw.
Yes, I do that moving back and forth to/from my desktop and portable.
Good. So the pw is inside the file [somehow] I can create a new volume [in my thumb drive along with many others I already have] with a new p/w. Then send the encrypted file.
If correct, I like that.
It is my understanding that the password is used to encrypt the file and that it is not embedded in the file.
I believe that the software uses the password to decrypt the header of the file. If it finds a certain code or set of bits, then it knows the file in encrypted (and not just some random file with random bits). Then if it passes the initial test it can unencrypt the rest of the contents. The unencryption happen as you read the inside of the file. unenrypting as needed.
1 Like
Heh, I did say, ‘somehow’. Long as it works…
I just saved a 148K file to a new VC volume. The file in that volume is 5.3 mb…! Is 25X larger normal?
I think the file should show about the same size. Let me check. Understand that the container will be larger and all space allocated by veracrypt. That is so the container does not have to be recreated larger when you add a file to it. Once the container is built and allocated, it does not change size.
OK, I created a container file of 100 mb in a FAT format. Explorer says it is 104 mb.
I copied into it a program of 8.15 mb and that is what explorer shows the size is inside the container. I also only show that one file.
Did you perhaps create a file container that is 5 mb and then copy the 148k file in? If so, associate the file container with a drive letter, access the drive letter and you should see a 145k file and (5 mb - 148k) left in empty space.
I like Lavarock’s answere.
I don’t even pretend to understand, but somehow the file seems to absorb the space allowed. Does that make sense?
See pic below. I created two volumes: vc1 at 5mb and vc2 at 500kb. I mounted them one at a time and copied a 148kb into each one. The SAME file…
After dismounting, the file in vc1 is 5mb and the same file in vc2 is 500kb. The same file…
After using VC for many years, I realize I have NO idea how it works
I can only speak for Windows machines. Is this on windows or perhaps a different operating system?
On Windows when you create the file, it does not get larger as you put files in. The whole file is allocated on disc and it stays that way. When you map to it, it looks like a disk at that size. Other operating systems may not behave the same.
Windows 10. Yes, in my pic example above, after adding the small file to those new volumes, and then close the volume the file size remains the much larger size.
On the positive side, this does resolve my problem of sending encrypted files to my heirs. I can create individual volumes around 250-500k and easily email them.
Heirs will have VC and can easily decrypt and save them.