-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Version should be 1 . #3
Comments
@pawp81 |
Thank you. I see DKM key extracted from Active Directory already comes in HEX. |
yes, DKMkey.bin should be HEX representation of actual ANSI bytes. |
Hi! In my case I used 'cat DKMkey.txt | tr -d "-" | xxd -r -p > DKMkey.bin'. I think it works the same but I did not get the zeros :) |
Thank you I am getting closer What do you do with EncryptedPFX? Do you just base64 decode the output from ADFSDump? |
Ha!
Have fun! |
Thank you! It worked, though only on Linux. On Windows I am getting installation error when installing crypthography. |
Hey!
|
Hey @0xMazen @duzvik Calculated MAC did not match anticipated MAC i have tried to install this but its not being installed at any other version of cryptography im able to install |
Same issue, having all kinds of version issues even in a venv with requirements.txt |
When running python ADFSpoof.py -b Token_sign_blob.bin DKMkey.bin dump
I am getting "Version should be 1" message and script dies.
I modified EncryptedPfx.py to output what the actual version is. The version is: "538976257"
Probably the problem lies in the way I saved EncryptedPfx and DKMkey from ADFSDump
What I did:
EncryptedPfx
a) I took everything between: [-] Encrypted Token Signing Key Begin and [-] Encrypted Token Signing Key End, which looks like this:
AAAAAQAAAAAEEGXuqoRBIwFInUU[....]q6YTotIB2BA8v+zfmKuMDPw==
b) I based64 decoded and saved the output to Token_sign_blob.bin
DKM key
a) I took Private Key: B7-12-96-C1-50-89-CA-54-B7-D2-ED-E5-F0-8E-24-AA-4F-27-2F-1B-2C-9E-2E-8A-43-47-42-FD-55-B0-72-CB
b) I removed dashes.
c) I base64 decoded it and saved the output to DKMkey.bin
Is there any other type of conversation that needs to be done?
The text was updated successfully, but these errors were encountered: