Dave,
Thanks again to you for your support.
I test your new 2.6b code and works fine. No more lang & anyURI datatypes
errors. But when I try to test the generated lib with any xml sample files
conformant to this xsd schema, I got the following error:
$ python iodeflib.py rfc5070-scan-sample.xml
Traceback (most recent call last):
File "iodeflib.py", line 5616, in <module>
main()
File "iodeflib.py", line 5609, in main
parse(args[0])
File "iodeflib.py", line 5560, in parse
rootObj.build(rootNode)
File "iodeflib.py", line 466, in build
self.buildChildren(child, node, nodeName_)
File "iodeflib.py", line 483, in buildChildren
obj_.build(child_)
File "iodeflib.py", line 815, in build
self.buildChildren(child, node, nodeName_)
File "iodeflib.py", line 860, in buildChildren
ReportTime_ = self.gds_validate_string(ReportTime_, node, 'ReportTime')
AttributeError: 'Incident' object has no attribute 'gds_validate_string'
I'm attaching to this post the sample 'rfc5070-scan-sample.xml' file, that
was extracted from iodef rfc standard (rfc 5070). Any other samples
extracted from this rfc report the same error.
I would appreciate any help or advice.
technoman.
2011/10/13 Dave Kuhlman <dkuhl...@pacbell.net>
> >From: TECHNOMAN
> >Sent: Monday, October 3, 2011 12:49 PM
> >
> > First of all, thanks for your very useful code and superb support!
>
>
> You are welcome. Hope it's of use.
>
> More below.
>
> >
> > Sorry, but the last error I reported to you, missed to say that was
> > generated after a generateDs.py & gends_extract _simple_types.py &
> > gends_generate_django.py step-by-step invocation, not
> > gends_run_gen_django.py as you did.
> >
> > Using your instructions, if I run ' gends_run_gen_django.py' got
> > this new error:
> >
> > $ ./gends_run_gen_django.py -f iodef.xsd
> > *** error ***
> > Unhandled simple type: lang language
> > Unhandled simple type: lang language
> > Unhandled simple type: lang language
> > Unhandled simple type: URL anyURI
> > Unhandled simple type: URL anyURI
> > Unhandled simple type: URL anyURI
> > *** error ***
> >
> > But anway, the script generates the same models, forms & admin
> > script that you sent me by mail. If I run with your new 2.6b code,
> > reports the same error.
> >
> > I think it may be a schema content/conversion error, not associated
> > with your new changes to code. I'm using python 2.6.5 and Django
> > 1.3.0, if it helps.
>
> There is a new version. I believe that it fixes the problems with
> "language" and "anyURI" datatypes.
>
> Thanks for reporting this and helping me identify that problem.
>
> You can find the new version here:
>
> - Python Package Index -- http://pypi.python.org/pypi/generateDS/
> - Source Forge -- http://sourceforge.net/projects/generateds/
>
> When you have more comments, please send them along. Thanks again.
>
> - Dave
>
>
>
> --
>
>
> Dave Kuhlman
> http://www.rexx.com/~dkuhlman
>
<?xml version="1.0" encoding="UTF-8" ?>
<!-- This example describes reconnaissance activity: one-to-one and
one-to-many scanning -->
<IODEF-Document version="1.00" lang="en"
xmlns="urn:ietf:params:xml:ns:iodef-1.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="urn:ietf:params:xml:schema:iodef-1.0">
<Incident purpose="reporting">
<IncidentID name="csirt.example.com">59334</IncidentID>
<ReportTime>2006-08-02T05:54:02-05:00</ReportTime>
<Assessment>
<Impact type="recon" completion="succeeded" />
</Assessment>
<Method>
<!-- Reference to the scanning tool "nmap" -->
<Reference>
<ReferenceName>nmap</ReferenceName>
<URL>http://nmap.toolsite.example.com</URL>
</Reference>
</Method>
<!-- Organizational contact and that for staff in that
organization -->
<Contact role="creator" type="organization">
<ContactName>CSIRT for example.com</ContactName>
<Email>cont...@csirt.example.com</Email>
<Telephone>+1 412 555 12345</Telephone>
<!-- Since this <Contact> is nested, Joe Smith is part of the
CSIRT for example.com -->
<Contact role="tech" type="person" restriction="need-to-know">
<ContactName>Joe Smith</ContactName>
<Email>sm...@csirt.example.com</Email>
</Contact>
</Contact>
<EventData>
<!-- Scanning activity as follows:
192.0.2.1:60524 >> 192.0.2.3:137
192.0.2.1:60526 >> 192.0.2.3:138
192.0.2.1:60527 >> 192.0.2.3:139
192.0.2.1:60531 >> 192.0.2.3:445
-->
<Flow>
<System category="source">
<Node>
<Address category="ipv4-addr">192.0.2.200</Address>
</Node>
<Service ip_protocol="6">
<Portlist>60524,60526,60527,60531</Portlist>
</Service>
</System>
<System category="target">
<Node>
<Address category="ipv4-addr">192.0.2.201</Address>
</Node>
<Service ip_protocol="6">
<Portlist>137-139,445</Portlist>
</Service>
</System>
</Flow>
<!-- Scanning activity as follows:
192.0.2.2 >> 192.0.2.3/28:445 -->
<Flow>
<System category="source">
<Node>
<Address category="ipv4-addr">192.0.2.240</Address>
</Node>
</System>
<System category="target">
<Node>
<Address category="ipv4-net">192.0.2.64/28</Address>
</Node>
<Service ip_protocol="6">
<Port>445</Port>
</Service>
</System>
</Flow>
</EventData>
</Incident>
</IODEF-Document>
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
_______________________________________________
generateds-users mailing list
generateds-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/generateds-users
