Questions.

[kolet]

1, is that possible to recover the password using the recovery key?

2, how long does it take to crack the recovery key? (with 1080 and whats the hashrate?)

3, what a concept would u go for, would u attack the password which is much slower. (1k~ per sec) or go for the recovery key

4, if i have a bitlocker encrypted 2tb hdd drive , is that possible to dd just a part of it and not all of it, for example the first bytes of the sectors ? like in truecrypt/veracrypt(first 512bytes)?

5, related to question 2 just want to make it right, doing the calculation , 10 powered by 48 thats 1000000000000000000000000000000000000000000000000 options.

if each 1080 theoretically does 3MHs and i have 5 rigs with 8 1080 in each which mean 40 1080 cards
i could do 120MHs

1000000000000000000000000000000000000000000000000 / 120000000 = 8333333333333333333333333333333333333333 seconds

8333333333333333333333333333333333333333 = 138888888888888888888888888888888888888 minutes = 2314814814814814814814814814814814815 hours = 96450617283950617283950617283950617 days.

which make it impossible to BF it, is that right ?

@e-ago thanks for answering all of these questions :)

[e-ago]

1. In file utils.cu we extract the recovery key from the input recovery password. You can try to reverse that procedure

2. Recovery password hashrate is similar to the user password rate (I published some result in the main page with different GPUs)

3. If your device has been encrypted with an user password I would choose this method because it may be easier to get the proper input dictionary. Otherwise, recovery password is the unique option you have

4. Yes, BitCracker just needs the metadata part that is the one beginning with the -FVE-FV- signature

5. Yes the problem with the recovery password relies on the magnitude of the possible candidate passwords. Anyway in file utils.cu we check if the format of the input recovery password follows some simple rules: this removes some possible candidates.