Jump to content

How do I extract usernames and Passwords from AD to make a CSV file ?


Recommended Posts

Posted

I don't think that there is going to be any way to list passwords from AD - I certainly hope not. A few years ago you could have used something called L0phtcrack from @Stake, but that doesn't work with modern systems. Think of the security risks.

 

You CAN use an Active Directory Migration Tool to move accounts from one AD to another though if you like.

 

http://www.microsoft.com/downloads/details.aspx?FamilyID=6f86937b-533a-466d-a8e8-aff85ad3d212&displaylang=en

 

What do you want this information for?

Posted

We asked ourselves this very question some years ago when we moved to AD. - We then decided that rather than let AD dictate what the data was, we supplied the data to AD so we always have a record which comes in ever so useful when some xyz software wishes the users to "log onto it".

 

To answer your question, I too doubt you can without considerable effort.

 

Have a look here for some information.

Posted

I was asked about this at Friday's Northants IT Managers' meeting ... but from the point of testing the complexity of passwords used.

 

There is a possible hypothetical scenario that has some major caveats ... and I do mean major.

 

Should you wish to perform a brute force attack using some of the tools previously mentioned or other more interesting tools (rainbow hash, etc rather than brute force) then to protect yourself, your network and your users I was always told to do certain things (not that I have ever tried!!! erm ... )

 

First, you need to use these tools on a closed network. You are performing this on a machine that has no connections to anything at all!!!! It is a machine that has been set up specifically for this purpose and will be securely wiped as soon as you are happy with it. Any files you remove from it (csv or otherwise) will be scanned with every possible AV and anti-spyware scanner possible. Not all tools (or copies of tools) that you pull down to do the password attack are done by white hat / grey hat coders ... some that you pull down will have backdoors that will then send you info to a remote box and you could be leaving yourself open to attack.

 

Second ... the machine that you are running this on, you can now separate it a lot easier than a few years ago by using virtualisation tools. Build a server on VMWare, make it a DC (global catalogue, etc) and make sure everything is hunky dory with it on the network. Then shut it down, clone the image of it, move the image onto a machine that will be away for the network. The Original VMWare box can now be demoted from being a DC and then removed from the domain. Make sure it is completeley removed just in case. If possible also change the admin password too. (it is not paranioa ... it is being safe!)

 

So ... we have this VMWare image of a working DC that has all the info on it.

 

Make sure that you are not sharing the network or have an shared folders between the image and the host machine. Once you are confident that *nothing* can get from the guest to the host then you can start.

 

I would recommend 3 weeks for a brute force attack, and other attacks can be completed a lot sooner (according to information I have read!)

 

There are other ways of doing things but the above is the safest I can find / think of.

 

Remember that I do not advocate anyone using any form of cracking, hacking, man-in-the-middle or other forms of attack to get information out of systems that is encrypted or protected in anyway, even if it is your network and you need to get the info to complete a body of work.

 

All of these attacks rely on physical access (or remote administrator access) to start and complete. Protect your systems by keeping machines secure and patched.

Posted
I was asked about this at Friday's Northants IT Managers' meeting ... but from the point of testing the complexity of passwords used.

 

There is a possible hypothetical scenario that has some major caveats ... and I do mean major.

 

Should you wish to perform a brute force attack using some of the tools previously mentioned or other more interesting tools (rainbow hash, etc rather than brute force) then to protect yourself, your network and your users I was always told to do certain things (not that I have ever tried!!! erm ... )

 

First, you need to use these tools on a closed network. You are performing this on a machine that has no connections to anything at all!!!! It is a machine that has been set up specifically for this purpose and will be securely wiped as soon as you are happy with it. Any files you remove from it (csv or otherwise) will be scanned with every possible AV and anti-spyware scanner possible. Not all tools (or copies of tools) that you pull down to do the password attack are done by white hat / grey hat coders ... some that you pull down will have backdoors that will then send you info to a remote box and you could be leaving yourself open to attack.

 

Second ... the machine that you are running this on, you can now separate it a lot easier than a few years ago by using virtualisation tools. Build a server on VMWare, make it a DC (global catalogue, etc) and make sure everything is hunky dory with it on the network. Then shut it down, clone the image of it, move the image onto a machine that will be away for the network. The Original VMWare box can now be demoted from being a DC and then removed from the domain. Make sure it is completeley removed just in case. If possible also change the admin password too. (it is not paranioa ... it is being safe!)

 

So ... we have this VMWare image of a working DC that has all the info on it.

 

Make sure that you are not sharing the network or have an shared folders between the image and the host machine. Once you are confident that *nothing* can get from the guest to the host then you can start.

 

I would recommend 3 weeks for a brute force attack, and other attacks can be completed a lot sooner (according to information I have read!)

 

There are other ways of doing things but the above is the safest I can find / think of.

 

Remember that I do not advocate anyone using any form of cracking, hacking, man-in-the-middle or other forms of attack to get information out of systems that is encrypted or protected in anyway, even if it is your network and you need to get the info to complete a body of work.

 

All of these attacks rely on physical access (or remote administrator access) to start and complete. Protect your systems by keeping machines secure and patched.

 

 

I just need it to populate Mylittlehelpdesk..... Ozan asaid that he had a way of doing it but he seems to have vanished just before we go live leaving us up the creek...

Posted
I just need it to populate Mylittlehelpdesk..... Ozan asaid that he had a way of doing it but he seems to have vanished just before we go live leaving us up the creek...

 

Ah ... you are talking about the AD integration? Pretty sure there are a few members that have it set up already for that. I think Plexor does ...

Posted
Ah ... you are talking about the AD integration? Pretty sure there are a few members that have it set up already for that. I think Plexor does ...

 

 

 

Thanks for the advise..

 

But not really he is hosting it so it wouldn't be cahtting to my DC AD...,

 

Thanks for the Lonks.. I can add bulk users but what I need is the passwords from AD

Posted
I can add bulk users but what I need is the passwords from AD

 

User passwords are stored in Active Directory using one-way encryption, - ie. you can't reverse the process (without resorting to a brute-force approach which could take a while!). There is a security policy option to change this, but it's not a recommended approach (I'm also not sure what it'll do to existing passwords).

 

Stephen

Posted

You can do this by using csvde to get an export of usernames.

forgot all the switches and so on but i'm sure a quick google will bring something up.

Posted
I don't think that there is going to be any way to list passwords from AD - I certainly hope not. A few years ago you could have used something called L0phtcrack from @Stake, but that doesn't work with modern systems. Think of the security risks.

 

You CAN use an Active Directory Migration Tool to move accounts from one AD to another though if you like.

 

http://www.microsoft.com/downloads/details.aspx?FamilyID=6f86937b-533a-466d-a8e8-aff85ad3d212&displaylang=en

 

What do you want this information for?

 

Because he has the administrator password and system access this would not be to difficult with either l0pthcrack also known as LC5, (Symantec who owns the code no longer provide sale or support) or pwdump.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...