To protect XML Files created by Navision, from external manipulators, I add a node-tag 'hashed', with the result of a Hashing Method. The result is like this :
<HASHED><![CDATA[çc Hg€~ð…Kàç—h‚Ô7™‹D?"h9œgc]]></HASHED>
So the file remains readable by human.
BUT at the other end of the process, in Navision, when the parser needs to re-open this XML File, it returns an error like this : XML Parsing Error: not well-formed
In fact, I suppose that some of the characters generated by the Hashing Method SHA1 are not supported by the document encoding. (hexa values like 03, 07, etc)
<?xml version="1.0" encoding="UTF-16"?>
Has anyone a good idea to resolve this issue ? Another encoding, another routine, another approach.
TIA and Happy NY 2007.
Louis
Automation : 'Xceed Encryption Library v1.1'
0
Comments
You could pehaps try looking at this?
.NET has some classes for dealing with this in the System.Security.Cryptography.Xml namespace.
I'm sure other languages will have similar libraries to support this standard
If that sounds like overkill for your needs then you could Base64 encode the hash before writing it the file.