-
Notifications
You must be signed in to change notification settings - Fork 13.8k
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
implement vnc hash types #16341
implement vnc hash types #16341
Conversation
|
@msjenkins-r7 retest this please |
@gwillcox-r7 I just assigned @sjanusz-r7 to this, but it looks like you're already testing this functionality in a separate PR? 👀 #16207 Is it worth assigning this to yourself too? |
@adfoster-r7 Happy to pick this up seeing as the two are related 👍 Otherwise no issues with @sjanusz-r7 picking this up if he is interested |
Verified can capture and crack the hash:
And cracking it:
|
And looks like we no longer crash:
|
LGTM will land this now 👍 |
Release NotesFixed a bug where the |
Heads up for whoever is doing wrapup this week, this is technically both a bug fix and an enhancement merged into one PR hence the dual labels here. |
@gwillcox-r7 I believe the wrapup generator will preference placing this in the |
fixes #16296
@smashery I know you had claimed the issue, but figured I could help with the hash stuff since I wrote it. Hopefully these changes are easy to merge into the changes you've been working on.
creds
commandvnc
module to not tack on$vnc$
because that is most likely JTR specific, we'll do that when we export to jtr.hash_identify
so we can properly detect them, along with a libjtr
export forvnc
hashesvnc
type, so I linked the latest I could find and just left it at thatVerification
password
)creds -o /tmp/vnc.jtr
john /tmp/vnc.jtr
creds add hash:*00112233445566778899aabbccddeeff*6feb3cb1f07b66151656b5832341f223
creds -o /tmp/hashes.jtr