FWIW, this is what a text editor that will open binary files shows.  I don't actually have a
hex editor installed.  Trust whatever Michael finds over this. :)

Liz


On 10 Mar 2023 15:02, Peter wrote:
> That's disappointing. The next step would be to pursure encrypting the employee names and
other figures.
> 
> Given Tom Krieg's suggestion of keeping in mind my target audience, I'm leaning towards
a "that's good enough".
> 
> I am still intrigued however. I created another library. This time I am wondering if any
information can be had without me providing any details of what to look for. Any takers?
> 
> 
> 
> 
> On 03/10/2023 10:14 a.m., Michael Kennedy wrote:
>> Peter,
>>
>> On 10/03/2023 02:28, Peter wrote:
>>
>>> dynInt["Jack"] = 99
>>> dynInt["Jill"] = 5
>>> dynInt["Sam"] = 105
>>>
>>> The names can be seen but can the smallint value be seen?
>>
>> Yes.
>>
>> In hex, those values are 63, 05, and 69. They're in both files, a few bytes just before
the three names.
>>
>>
>>> dynName[99] = "Jack"
>>> dynName[5] = "Jill"
>>> dynName[105] = "Sam"
>>>
>>> Again, the names can be seen but can the elements be seen?
>>
>> Yes - as above.
>>
>> If, for example, your data had the salaries of three folks (one being myself, Jill),
and I knew my salary was 12345 (that's 39 30 in hex, reverse order), I could then easily extract
the salaries of the other two entries.
>>
>> Probably OK if the data is not super-sensitive.
>>
>> If the data is very sensitive, such as passwords, then maybe all file copies should
be encrypted. And, if any data is S-U-P-E-R sensitive, then all memory copies should probably
remain encrypted, except for the moments the actual decrypted values are used.
>>
>>    - Michael