Sample profile files in 20110630_X3PSampleFiles_NanoFocus.zip contain dummy y-values in the <datalist>s. These values were clearly taken from uninitialised memory when the file was created. It is possible to convert the floating point data back to binary and recover (up to some flipped bits) the original contents of the uninitialised memory.</datalist>
I cannot tell if these specific files contain any sensitive information but some ASCII and UTF-16 text segments are evident and more could be relealed by a detailed analysis.
The files should be created in a way that avoids the dump of uninitialised values (and, preferably, the dummy y-values altogether).
I am attaching some hexdumps of the uninitialised memory obtained from the profile files.
Another hexdump.
Related to [#3]
Related
Tickets: #3
In fact all three following files contain dumps of unitialised memory in the dummy y-values:
They can be easily spotted due to the values with weird exponents ±300 which is what you often get when you get some random rubbish and interpret it as doubles. So the ticket title is less accurate now. I don't think it makes sense to open a ticked for each file separately...