Enterprise Admins.org

Sometimes it is really easy to figure out a user’s password.  Just check out that picture to the right.  Other times the password is less obvious but could come from a list of passwords you already know.  For example, if your helpdesk always resets passwords to the same few values, many users could be using one of those default passwords.  Here is a simple process for those who would like to audit your directory for such accounts.

Document: Homegrown Dictionary/Rainbow Table Password Discovery

Scripts: Homegrown Dictionary/Rainbow Table Password Discovery

I thought I would share the script I made to create 10,000 test users in an NT 4.0 domain for my test lab.  I should note a couple of things:

• When I first ran this script, my domain only had the default ‘guest’ and ‘administrator’ accounts.
• I used Visual Basic Script (VBS) which does not require pre-defining of variables or variable types (adding ‘option explicit’ requirements would case the script to fail)
• The script was ran from a command line as ‘cscript.exe CreateUsersWinNtObj.vbs’
• No checking was performed to verify that the user ID was unique (in a ‘real’ domain this could cause a problem.
• This script was not tested with Active Directory domains.  However, the code would most likely work — creating all 10,000 users in the default “cn=users” container.

If you have any questions please let me know.

Create10kTestUsers

Again, some earlier code.  I’m not sure how good this works…I had ran it for a few weeks awhile back.  However, my IP address changed and I received a lot of notifications before I had a chance to resolve it.  The script would be better if it contained some sort of logic so that it only sent one notification.

Monday, 08 October 2007

• The purpose of this script is to:
• lookup a domain name with nslookup, returning an IP address
• find the external network address translation (NAT) using whatismyip.org
• compare the two IP addresses
• send a notification if they are not the same

This script was designed to run as a scheduled task and in my scenario it runs every 30 minutes.  The purpose is to work similiar to the www.no-ip.com service that will dynamically update DNS based on your external IP address.  Since I do not typically have a scripting interface into my hosted external DNS, I use a simple CDO email to let me know when DNS needs to be manually updated.


NatName = "publicnat.domainname.com"
NotifyContact = " scripting.user@domainname.com"
smtpserver = "smtp.domainname.com"

IP_in_DNS = DNSLookup(NatName)
IP_on_OutSide = ExternalIP()

If Not IP_in_DNS = IP_on_OutSide Then
SendEmail NotifyContact,NatName & " issue","The network address translation for " & NatName & " (IP_" & IP_in_DNS & ") does not match the current external address of IP_" & IP_on_OutSide & "."
End If

msgbox "Done."

Function DNSLookup(sDNSName)
On error resume next

Const OpenAsDefault = -2
Const FailIfNotExist = 0
Const ForReading = 1

Set oShell = CreateObject("WScript.Shell")
Set oFSO = CreateObject("Scripting.FileSystemObject")
sTemp = oShell.ExpandEnvironmentStrings("%TEMP%")
sTempFile = sTemp & "\" & oFSO.GetTempName

Sub SendEmail(strTo, strSubject, strBody)
Set objEmail = CreateObject("CDO.Message")
objEmail.From = NotifyContact
objEmail.To = strTo
objEmail.Subject = strSubject
objEmail.HTMLBody = strBody
'objEmail.AddAttachment (txtOutFile)
objEmail.Configuration.Fields.Item _
("http://schemas.microsoft.com/cdo/configuration/sendusing") = 2
objEmail.Configuration.Fields.Item _
("http://schemas.microsoft.com/cdo/configuration/smtpserver") = smtpserver
objEmail.Configuration.Fields.Item _
("http://schemas.microsoft.com/cdo/configuration/smtpserverport") = 25
objEmail.Configuration.Fields.Update
objEmail.Send
End Sub