Test results for Solaris x86 |
Test for the generation of correct messages digests. If a byte-order-mark is present then that data is also included in the message digest calculations.
Pass
echo "MD5 of static input file without BOM:" cat _INPUT_DATA_IN_1 ¦ openssl md5 ¦ sed 's/(stdin)= //' echo "MD5 of static output file without BOM:" cat _INPUT_DATA_OUT_1 ¦ openssl md5 ¦ sed 's/(stdin)= //' echo "xmlfy MD5 without BOM" cat _INPUT_DATA_IN_1 ¦ xmlfy -s ¦ grep "md5_" echo "" echo "MD5 of static input file with BOM:" cat _INPUT_DATA_IN_2 ¦ openssl md5 ¦ sed 's/(stdin)= //' echo "MD5 of static output file with BOM:" cat _INPUT_DATA_OUT_2 ¦ openssl md5 ¦ sed 's/(stdin)= //' echo "xmlfy MD5 with BOM" cat _INPUT_DATA_IN_2 ¦ xmlfy -X BOM -s ¦ grep "md5_"
+==================================================+ ¦ Static input file without BOM: _INPUT_DATA_IN_1 ¦ ¦ Static input file with BOM: _INPUT_DATA_IN_2 ¦ +==================================================+ word1 word2 +==================================================+ ¦ Static output file without BOM _INPUT_DATA_OUT_1 ¦ ¦ Static output file with BOM _INPUT_DATA_OUT_2 ¦ +==================================================+ <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE xmlfy SYSTEM "xmlfy.dtd"> <xmlfy> <line> <field>word1</field> </line> <line> <field>word2</field> </line> </xmlfy>
MD5 of static input file without BOM: 940ab68e2a1b8c635139bea5963535bc MD5 of static output file without BOM: be49181c581c09bb60e92efa03d1e717 xmlfy MD5 without BOM <md5_input>940ab68e2a1b8c635139bea5963535bc</md5_input> <md5_output>be49181c581c09bb60e92efa03d1e717</md5_output> MD5 of static input file with BOM: a344a6e23c2d672c1e8ec3a058ea1172 MD5 of static output file with BOM: 90b81f1abfa38b8de54ac049689e385b xmlfy MD5 with BOM <md5_input>a344a6e23c2d672c1e8ec3a058ea1172</md5_input> <md5_output>90b81f1abfa38b8de54ac049689e385b</md5_output>