+- Hack Forums (https://hackforums.net)
+-- Forum: Hacks, Exploits, and Various Discussions (https://hackforums.net/forumdisplay.php?fid=45)
+--- Forum: Blackhat • Red Team • Offensive Security (https://hackforums.net/forumdisplay.php?fid=447)
+---- Forum: Cryptography, Encryption, and Decryption (https://hackforums.net/forumdisplay.php?fid=126)
+---- Thread: What is real safety of encrypted partition (in file) using VeraCrypt (/showthread.php?tid=6155211)
What is real safety of encrypted partition (in file) using VeraCrypt - SuperNeo - May 23, 2021
Hi. I use VeraCrypt to keep files in encrypted partition which is stored as a file (.hc) on NTFS partition. My question is: how safe it really is? If someone determined steels my computer and really wants to dig the data out... will they be able to do that and much effort will they must put into that? I don't know exactly what are mechanisms of VeraCrypt, but doesn't it just encrypt header of a partition and... that's it!?
RE: What is real safety of encrypted partition (in file) using VeraCrypt - Stetsed - May 24, 2021
Well if you completed the generate random bar then first of all, brute forcing will be impossible, atleast in the age of the universe. Next to this the only real way is to bruteforce the password. So... uhhh... use a good password for it xD
RE: What is real safety of encrypted partition (in file) using VeraCrypt - Vyreazz - May 27, 2021
Better password in rarely used unicode characters
RE: What is real safety of encrypted partition (in file) using VeraCrypt - Lilith - May 28, 2021
(May 27, 2021 01:05 PM)Vyreazz Wrote: Better password in rarely used unicode characters
Well that's just entirely misleading. "*"8rLÄ_;{@" has an entropy of 66.60 "syjfxykMTt2h" has an entropy of 71.45. Length has just as much significance as the specific characters being used.
RE: What is real safety of encrypted partition (in file) using VeraCrypt - PerkyHash - May 28, 2021
This is an interesting one. Following
RE: What is real safety of encrypted partition (in file) using VeraCrypt - SIM-574702 - May 28, 2021
(May 28, 2021 07:37 AM)p4620389213847021 Wrote: Well that's just entirely misleading. "*"8rLÄ_;{@" has an entropy of 66.60 "syjfxykMTt2h" has an entropy of 71.45. Length has just as much significance as the specific characters being used.
I agree that length is important but I don't see how your calculation can be correct. Unicode has over 140k characters so I think you underestimated character pool size. What would your calculation of entropy for password like this be. "†‡Ž‰Šv(Ť"
That password shows 136 bits of entropy on This link when setting it up as 140k character pool and 8 character password. If I've missed something feel free to correct me.
RE: What is real safety of encrypted partition (in file) using VeraCrypt - Lilith - May 28, 2021
(May 28, 2021 02:30 PM)matemisic Wrote: I agree that length is important but I don't see how your calculation can be correct. Unicode has over 140k characters so I think you underestimated character pool size. What would your calculation of entropy for password like this be. "†‡Ž‰Šv(Ť"
That password shows 136 bits of entropy on This link when setting it up as 140k character pool and 8 character password. If I've missed something feel free to correct me.
I was using KeePassXC's password generator. The which it shows the entropy"†‡Ž‰Šv(Ť" to be 26.01.
![[Image: utJRPHo.png]](https://i.imgur.com/utJRPHo.png)
Additionally, using Kaspersky's Password Checker, the password you provided would take about 14 days to crack. The initial password I mentioned, "*"8rLÄ_;{@" would take 4 years, and "syjfxykMTt2h" would take 4 centuries. BitWarden has the passwords at 3 hours, 12 days, and 3 years respectively.
RE: What is real safety of encrypted partition (in file) using VeraCrypt - SIM-574702 - May 28, 2021
(May 28, 2021 02:40 PM)p4620389213847021 Wrote: I was using KeePassXC's password generator. The which it shows the entropy"†‡Ž‰Šv(Ť" to be 26.01.
Additionally, using Kaspersky's Password Checker, the password you provided would take about 14 days to crack. The initial password I mentioned, "*"8rLÄ_;{@" would take 4 years, and "syjfxykMTt2h" would take 4 centuries. BitWarden has the passwords at 3 hours, 12 days, and 3 years respectively.
Both of those sites actually use same library to check password and it's called Zxcvbn.js. Proof here but you can look it up yourself. As far as I've seen in it's source code it doesn't support full unicode which is why "qrhdcoig" has same entropy as "qrhdcoi1" and as "†‡Ž‰Šv(Ť". The way this library works is that it has multiple matchers but considering these passwords aren't going to be in dictionary I'll focus on brute force part.
If you take a look at this java implementation HERE you will see that is has a cardinality (estimation of character pool size) to be only 100 while unicode supports over 140k characters. That was java and I used that implementation to get basic insight in architecture but these websites use javascript so I looked into those as well and I found that cardinality is hardcoded at 10 HERE. It's used BELOW and as you can see again, it doesn't factor in that character poolsize is 140k.
If we take that Entropy formula is E = L log2( R) where R is size of the pool of unique characters from which we build the password and
L is password length, i.e., the number of characters in the password. (Formula copied from here) we can calculate entropy of "†‡Ž‰Šv(Ť" to be E = 8 log2(140k) = 136.760538413 Google Link
My calculation is correct under assumption that whole unicode character pool is usable and no two characters are treated as same. I have not checked Veracrypt's source code but I'm confident those assumptions are true.
RE: What is real safety of encrypted partition (in file) using VeraCrypt - cokecaine - May 28, 2021
Following. A very informative thread.
RE: What is real safety of encrypted partition (in file) using VeraCrypt - SuperNeo - Jun 23, 2021
Hi. Maybe I don't understand something here or maybe I didn't explain myself clearly enough...
so yes I filled the "random bar" with random mouse movements a lot and I have loooong password, but my question IS this: is the whole partition encypted somehow (I don't think so) or ONLY it's header? In other words (as far as I remember) if only header is encrypted, then someone can still analyze the data of the partition, no? It would be like looking for deleted files... they are not listed in master file table, but still present on disk, so they can be found by analyzing the data byte by byte. I am right here?
RE: What is real safety of encrypted partition (in file) using VeraCrypt - BigDap - Apr 7, 2023
interested in information, following!