Skip to content
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

Mimikatz Kerberox export issue #50

Closed
aldo1901 opened this issue Jun 22, 2016 · 3 comments
Closed

Mimikatz Kerberox export issue #50

aldo1901 opened this issue Jun 22, 2016 · 3 comments

Comments

@aldo1901
Copy link

I'm playing around with Kerberos dumping and cracking. I'm starting mimikatz and running "standard::base64" so that all the .kirbi files get exported using base64 encoding. However once I execute "kerberos::list /export" using base64, there are no output files in my directory. Mimikatz only saves .kirbi files when I DON'T use base64 encoding.

@gentilkiwi
Copy link
Owner

That's exactly the expected behavior: https://github.com/gentilkiwi/mimikatz/wiki/module-~-standard#base64

@aldo1901
Copy link
Author

aldo1901 commented Jun 22, 2016

So to manually put these into a blah.kirbi I would just copy the encoding alone without the ===== lines or with======?

"===================="
doIFOTCCBTWgAwIBBaEDAgEWooIELjCCBCphggQmMIIEIqADAgEFoREbD0NIT0NP
TEFURS5MT0NBTKIkMCKgAwIBAqEbMBkbBmtyYnRndBsPQ0hPQ09MQVRFLkxPQ0FM
...
GA8yMDE0MDQyNDIyNTE0NFqnERgPMjAxNDA1MDExMjUxNDRaqBEbD0NIT0NPTEFU
RS5MT0NBTKkkMCKgAwIBAqEbMBkbBmtyYnRndBsPQ0hPQ09MQVRFLkxPQ0FM
"===================="

@gentilkiwi
Copy link
Owner

If you want to have data in a file, don't use the base64 command.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants