Date formats for structured output

[David Fifield <david () bamsoftware com>]

On Wed, Aug 15, 2012 at 08:00:00PM -0700, commit-mailer () insecure org wrote:
> Author: dmiller
> Date: Wed Aug 15 20:00:00 2012
> New Revision: 29601
>
> Log:
> Add @xmloutput nsedoc to ssh-hostkey, smb-os-discovery
>
> Modified: nmap/scripts/smb-os-discovery.nse
> ==============================================================================
> --- nmap/scripts/smb-os-discovery.nse (original)
> +++ nmap/scripts/smb-os-discovery.nse Wed Aug 15 20:00:00 2012
> @@ -56,7 +56,18 @@
>  -- |   NetBIOS computer name: SQL2008
>  -- |   NetBIOS domain name: LAB
>  -- |_  System time: 2011-04-20 13:34:06 UTC-5
> ------------------------------------------------------------------------
> +--
> +--@xmloutput
> +-- <script id="smb-os-discovery" output="...">
> +--   <elem key="OS">Windows Server (R) 2008 Standard 6001 Service Pack 1 (Windows Server (R) 2008 Standard 
> 6.0)</elem>
> +--   <elem key="Computer name">Sql2008</elem>
> +--   <elem key="Domain name">lab.test.local</elem>
> +--   <elem key="Forest name">test.local</elem>
> +--   <elem key="FQDN">Sql2008.lab.test.local</elem>
> +--   <elem key="NetBIOS computer name">SQL2008</elem>
> +--   <elem key="NetBIOS domain name">LAB</elem>
> +--   <elem key="System time">2011-04-20 13:34:06 UTC-5</elem>
> +-- </script>

As for this part of the output,
> +--   <elem key="System time">2011-04-20 13:34:06 UTC-5</elem>
I think there will be a lot of value if we use a common date format in
all scripts that use structured output. I have been using
os.date("%Y-%m-%dT%H:%M:%SZ") which looks like
        2012-08-16T05:03:30Z
This is ISO 8601. However, this supposes UTC, so we would have to
represent the "UTC-5" in the date above separately. Perhaps we should
settle on a date format that also includes a time zone?

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