News for hackers. Stuff that matters.

A comment on Man Who Refused to Decrypt Hard Drives Still in Prison After Two Years. Parent comment

Re:Man Who Refused to Decrypt Hard Drives Still in Prison Af... by poizan42 on Saturday September 02, 2017 @09:02AM (#15155758)
The correct order is hash then encrypt, exactly so you can't do that. Now I don't know if FileVault is doing this correctly, but hopefully it does.

Edit: So two people have downvoted me without explanation. Is what I'm saying wrong?

[ Parent | on HN ]
Re:Man Who Refused to Decrypt Hard Drives Still in Prison Af... by slaymaker1907 on Saturday September 02, 2017 @12:32PM (#15156854)
You could also hash, encrypt, then hash again if you wanted extra integrity without decrypting. This is technically done with HTTPS through the TCP hash.
[ Parent | on HN ]
Re:Man Who Refused to Decrypt Hard Drives Still in Prison Af... by mdekkers on Saturday September 02, 2017 @12:14PM (#15156723)
two people have downvoted me without explanation

Sadly, that is the new normal for HN (and, I'll be downvoted for saying something like this)

[ Parent | on HN ]
Re:Man Who Refused to Decrypt Hard Drives Still in Prison Af... by maaaats on Saturday September 02, 2017 @10:02AM (#15156008)
You can't unhash, so you could never retrieve the original file again.
[ Parent | on HN ]
Re:Man Who Refused to Decrypt Hard Drives Still in Prison Af... by poizan42 on Saturday September 02, 2017 @10:04AM (#15156020)
What do you mean? You obviously store the encrypted file together with the encrypted hash.
[ Parent | on HN ]
Re:Man Who Refused to Decrypt Hard Drives Still in Prison Af... by maaaats on Saturday September 02, 2017 @10:08AM (#15156044)
Then I guess me and the downvoters thought you meant hashing the files for encryption :)
[ Parent | on HN ]