Re: Updated output for scripts

[Ron <ron () skullsecurity net>]

I made the requested change to remove some of the horizontal space. Here
is how running --script=all against a patch Windows 2003 system looks:


Host script results:
|_smb-brute: guest:<blank> => Password was correct, but user's account
is disabled
| smb-system-info:
|_|_ERROR: NT_STATUS_ACCESS_DENIED
| smb-security-mode:
| | Account that was used for smb scripts: <blank>
| | User-level authentication
| | SMB Security: Challenge/response passwords supported
|_|_Message signing disabled (dangerous, but default)
|_smb-server-stats:
| smb-enum-domains:
|_|_ERROR: NT_STATUS_ACCESS_DENIED (samr.connect4)
| smb-enum-groups:
|_|_ERROR: Couldn't enumerate groups: NT_STATUS_ACCESS_DENIED
(samr.connect4)
|_smb-enum-processes: ERROR: NT_STATUS_ACCESS_DENIED
| smb-os-discovery:
| | OS: Windows Server 2003 3790 Service Pack 2 (Windows Server 2003 5.2)
| | Name: SKULLSECURITY\WINDOWS2003
|_|_System time: 2009-11-14 19:22:34 UTC-6
| smb-enum-users:
|_|_ERROR: Access denied while trying to enumerate users; except against
Windows 2000, Guest or better is typically required
| smb-enum-shares:
| | ERROR: Enumerating shares failed, guessing at common ones
(NT_STATUS_ACCESS_DENIED)
| | ADMIN$ (WARNING: Couldn't get details for share:
NT_STATUS_ACCESS_DENIED)
| | |_Anonymous access: <none>
| | C$ (WARNING: Couldn't get details for share: NT_STATUS_ACCESS_DENIED)
| | |_Anonymous access: <none>
| | IPC$ (WARNING: Couldn't get details for share: NT_STATUS_ACCESS_DENIED)
|_|_|_Anonymous access: READ
| smb-check-vulns:
| | MS08-067: NOT VULNERABLE
| | Conficker: Likely CLEAN
| | regsvc DoS: CHECK DISABLED (add '--script-args=unsafe=1' to run)
|_|_SMBv2 DoS (CVE-2009-3103): CHECK DISABLED (add
'--script-args=unsafe=1' to run)

And here is the output from a couple scripts running with full output:
| smb-enum-sessions:
| | Users logged in
| | |_WINDOWS2003\ron since 2009-11-06 13:25:28
| | Active SMB sessions
|_|_|_RON is connected from 192.168.102.1 for [just logged in, it's
probably you], idle for [not idle]
| smb-enum-shares:
| | ADMIN$
| | | Type: STYPE_DISKTREE_HIDDEN
| | | Comment: Remote Admin
| | | Users: 0, Max: <unlimited>
| | | Path: C:\WINDOWS
| | | Anonymous access: <none>
| | |_Current user ('ron') access: READ/WRITE
| | C$
| | | Type: STYPE_DISKTREE_HIDDEN
| | | Comment: Default share
| | | Users: 0, Max: <unlimited>
| | | Path: C:\
| | | Anonymous access: <none>
| | |_Current user ('ron') access: READ/WRITE
| | IPC$
| | | Type: STYPE_IPC_HIDDEN
| | | Comment: Remote IPC
| | | Users: 1, Max: <unlimited>
| | | Path:
| | | Anonymous access: READ <not a file share>
|_|_|_Current user ('ron') access: READ <not a file share>



Personally, I think we should stick with the extra whitespace. It feels
too squished together for me.

Thoughts?

Ron

-- 
Ron Bowes
http://www.skullsecurity.org/
_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://seclists.org/nmap-dev/