Thank you idrassi.
But what I'm not clear on still is: I used RIPEMD-160 on the drives when I re-created and converted my TrueCrypt headers to VeraCrypt only because it was the default and I wasn't sure what to use at the time. But as I mentioned, my keyfile was created using the default setting of SHA-512. So I guess my question is: Was there an advantage to using a SHA-512 key file even though the drive uses RIPEMD-160?
I don't get how the key file and the volume header work together. If the volume header on the drive uses RIPEMD-160 but the key file was made with SHA-512, would using the key file straighten the weak code by providing an advantage of strength that is missing from the weak RIPEMD-160 header?
I guess what I'm trying to ask is. What happens to the overall strength of an encrypted volume if you use a strong SHA-512 key with a weak RIPEMD-160 header on a drive? Is the end result any different?
But what I'm not clear on still is: I used RIPEMD-160 on the drives when I re-created and converted my TrueCrypt headers to VeraCrypt only because it was the default and I wasn't sure what to use at the time. But as I mentioned, my keyfile was created using the default setting of SHA-512. So I guess my question is: Was there an advantage to using a SHA-512 key file even though the drive uses RIPEMD-160?
I don't get how the key file and the volume header work together. If the volume header on the drive uses RIPEMD-160 but the key file was made with SHA-512, would using the key file straighten the weak code by providing an advantage of strength that is missing from the weak RIPEMD-160 header?
I guess what I'm trying to ask is. What happens to the overall strength of an encrypted volume if you use a strong SHA-512 key with a weak RIPEMD-160 header on a drive? Is the end result any different?
