W.A.S.P XML Parser and Randomizer for Protocol++® (ProtocolPP®)
W.A.S.P is an interface to Protocol++® to allow it to connect to a testbench and generate XML files with Protocol++® data. W.A.S.P accepts two input types either PPP (constraint file for random generation of packets) or PROTPP (data file containing packets to be driven into a testbench).
PPP Format
The PPP format (i.e., input.ppp) contains only stream, protocol, and security information. W.A.S.P interprets this type of file as either generating an output PROTPP file if the output is provided, or as generating random descriptors for the testbench that will subsequently be driven into the bench after generation.
The PPP has three possible formats as follows. NOTE: For all of these formats, any values not provided by the user are randomized
- FORMAT1 - Format #1 allows full randomization of seed, streams, packets, datalen, protocol, and security association run
- FORMAT2 - Format #2 allows randomization of streams, packets, datalen, and security association for the protocol(s) specified
- FORMAT3 - Format #3 allows randomization of streams, packets, and datalen for the protocol and security association specified
name='ipsecsa'
dir='ENCAP'
mode='tunnel'
audit='false'
tfclen='22'
authkey=
'AAAABBBBCCCCDDDDEEEEFFFF00001111'
iv=
'AAAABBBBCCCCDDDDEEEEFFFF00001111'>
</stream>
PROTPP Format
The PROTPP formation (i.e., input.protpp) contains stream, protocol, security, input, output, and expected values. W.A.S.P interpretes this type of input as the user wants to drive the testbench with the input file.
The PRTOPP format is as follows :
<stream name="test1"/>
name="tlsa"
dir='ENCAP'
version="DTLS"
type="APPLICATION"
iv=
"AABBCCDDFFEEDDCC0011223344556677"
authkey=
"AAAABBBBCCCCDDDDEEEEFFFF00001111"
<input name="nahdskdnac" stream="test1" prev="begin" write="vsmubmflmq">
<data width="1" len="44">
</data>
</input>
<output name="vsmubmflmq" stream="test1" len="109"/>
<
expect name=
"qmripfhnmo" stream=
"test1" read=
"vsmubmflmq" status=
"0">
<data width="1" len="109">
</data>
<input name="lrmgetesdc" stream="test1" prev="nahdskdnac" write="jmivnieulm">
<data width="1" len="35">
</data>
</input>
<output name="jmivnieulm" stream="test1" len="93"/>
<
expect name=
"drqtlqemmf" stream=
"test1" read=
"jmivnieulm" status=
"0">
<data width="1" len="93">
</data>
<input name="xbadryuyhd" stream="test1" prev="lrmgetesdc" write="qjwsjajebf">
<data width="1" len="5">
</data>
</input>
<output name="qjwsjajebf" stream="test1" len="61"/>
<
expect name=
"cafhfwghrk" stream=
"test1" read=
"qjwsjajebf" status=
"0">
<data width="1" len="61">
</data>
Using W.A.S.P
To use W.A.S.P, you can use one of the three constructs to pass in the XML input. W.A.S.P will parse the input and either
- If the input is a PPP file and no output file is passed, will generate random descriptors and then run them
- If the input is a PPP file and output file is passed, will generate a output.protpp file
- In the input is PROTPP file, will run the parsed input
Usage :
wasp mywasp(input, output, seed);
- input - either a character string reprenting an XML file, a string representing a filename, or an XMLDocument
- output - a string representing a filename for the output
- seed - seed for the random number generator to reproduce results
W.A.S.P Supported Schema
The W.A.S.P parser and randomizer supports the following schema
<
xs:
element name=
"general" type=
"xs:string"/>
<
xs:
element name=
"protocol" type=
"xs:string"/>
<
xs:
element name=
"security" type=
"xs:string"/>
<
xs:
element name=
"protocol" type=
"xs:string"/>
<
xs:
element name=
"security" type=
"xs:string"/>
<
xs:
element name=
"security" type=
"xs:string"/>
<
xs:
element name=
"protocol" type=
"xs:string"/>
<
xs:
attribute name=
"polynomial" type=
"xs:unsignedInt"/>
<
xs:
attribute name=
"extseqnum" type=
"xs:unsignedLong"/>
<
xs:
attribute name=
"urgpointer" type=
"xs:unsignedShort"/>
<
xs:
attribute name=
"framectl" type=
"xs:unsignedShort"/>
<
xs:
attribute name=
"ptkident" type=
"xs:unsignedShort"/>
<
xs:
element name=
"data" type=
"xs:hexBinary"/>
<
xs:
element name=
"data" type=
"xs:hexBinary"/>
Definition aead_chacha_poly1305.h:241
For API Documentation:
- See also
- ProtocolPP::jdata
-
ProtocolPP::jpacket
-
ProtocolPP::jstream
-
ProtocolPP::jprotocolpp
-
ProtocolPP::wasp
-
tinyxml2::XMLPrinter
-
tinyxml2::XMLVisitor
For Additional Documentation:
- See also
- jdata
-
jpacket
-
jstream
-
jprotocolpp
-
wasp
-
tinyxml2::XMLPrinter
-
tinyxml2::XMLVisitor
Protocol++® (ProtocolPP®) written by : John Peter Greninger • © John Peter Greninger 2015-2024 • All Rights Reserved All copyrights and trademarks are the property of their respective ownersThe source code contained or described herein and all documents related to the source code (herein called "Material") are owned by John Peter Greninger and Sheila Rocha Greninger. Title to the Material remains with John Peter Greninger and Sheila Rocha Greninger. The Material contains trade secrets and proprietary and confidential information of John Peter Greninger and Sheila Rocha Greninger. The Material is protected by worldwide copyright and trade secret laws and treaty provisions. No part of the Material may be used, copied, reproduced, modified, published, uploaded, posted, transmitted, distributed, or disclosed in any way without prior express written consent of John Peter Greninger and Sheila Rocha Greninger (both are required)
No license under any patent, copyright, trade secret, or other intellectual property right is granted to or conferred upon you by disclosure or delivery of the Materials, either expressly, by implication, inducement, estoppel, or otherwise. Any license under such intellectual property rights must be express and approved by John Peter Greninger and Sheila Rocha Greninger in writing
Licensing information can be found at www.protocolpp.com/license with use of the binary forms permitted provided that the following conditions are met:
- Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution
- Any and all modifications must be returned to John Peter Greninger at GitHub.com https://github.com/jpgreninger/protocolpp for evaluation. Inclusion of modifications in the source code shall be determined solely by John Peter Greninger. Failure to provide modifications shall render this license NULL and VOID and revoke any rights to use of Protocol++®
- Commercial use (incidental or not) requires a fee-based license obtainable at www.protocolpp.com/shop
- Academic or research use requires prior written and notarized permission from John Peter and Sheila Rocha Greninger
Use of the source code requires purchase of the source code. Source code can be purchased at www.protocolpp.com/shop
- US Copyrights at https://www.copyright.gov/
- TXu002059872 (Version 1.0.0)
- TXu002066632 (Version 1.2.7)
- TXu002082674 (Version 1.4.0)
- TXu002097880 (Version 2.0.0)
- TXu002169236 (Version 3.0.1)
- TXu002182417 (Version 4.0.0)
- TXu002219402 (Version 5.0.0)
- TXu002272076 (Version 5.2.1)
- TXu002383571 (Version 5.4.3)
The name of its contributor may not be used to endorse or promote products derived from this software without specific prior written permission and licensing
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER AND CONTRIBUTOR "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE