RegQueryValueEx problem

I have an application that stores and retrieves binary data from the registry. The application writes the data correctly to the registry but it cannot read all the data from the key if a 0x00 (zero, NULL) appears anywhere in the data written to the registry key. RegQueryValueEx appears to only read all the binary data up to the 0x00. For example, if I store 7b d1 13 74 00 d8 24 a3 in the registry, RegQueryValueEx only returns 7b d1 13 74. The key is a REG_BINARY key.

The data that is written to the key is first encrypted using the Rijndael method. So, I have no control over what is written to the reigstry. The Rijndael method occassionally generates a 0x00 when encrypting.

The code that I use to read the binary data is as follows:

Code:

---

char szEncryptedHAIKey[81] = {0};
char szHAIKey[81] = {0};

 memset(szHAIKey, 0, sizeof szHAIKey);
 iDatasize = sizeof (szEncryptedHAIKey);
 RegQueryValueEx(hKey, "HAIKey",
    NULL, NULL, (unsigned char *)&szEncryptedHAIKey, (unsigned long *)&iDatasize);
 Decrypt(szEncryptedHAIKey,szHAIKey , 80, ECB);

---

Any assistance would be greatly appreciated.

Never hit that issue, can you work round it?

Can you check the string and generate a new one if it contains nulls?

Can you store the data in another format that allows nulls?

Can you store the length or the string so you know how much to read?

Can you store the info somewhere else (windows ini file)?

Can you use a diff API call that will not present this error?

Quote:

---

Can you check the string and generate a new one if it contains nulls?

---

Unfortunately, I cannot do this. The app acquires a 16 byte hex string from a security controller and passes this string onto the Rijndael encryption function. The encryption function will always generate the same binary encrypted values. I'm using the Electronic Code Book Rijndael method that is required by the controller which as indicated above always generates the same encrypted values. I do have a temporary solution that requires the end user to change the hex value on the controller that generates the 0x00 to some other value. But this is a major inconvenience to the end user.

Quote:

---

Can you store the data in another format that allows nulls?

---

I'm currently using the REG_BINARY type for the key. I'm not aware of any other registry type that would allow a null value, 0x00 in particular and binary data in general.

Quote:

---

Can you store the length or the string so you know how much to read?

---

I can store the length of the string in another key. But how would I use the registry API to read past the 0x00 value? RegQueryValueEx stops reading at the 0x00 value.

Quote:

---

Can you store the info somewhere else (windows ini file)?

---

I'm currently working on moving this data out of the registry and into a Sqllite3 database. Sqllite3 has an "extension" for lack of a better description to store BLOB data in a field.

Quote:

---

Can you use a diff API call that will not present this error?

---

I'm not aware of any other API to read/write the registry.

Thanx

novacain,

I just realized that I made a really stupid mistake in another part of my code. I used strlen instead of sizeof. Thus, the problem with the 0x00, NULL terminator. This was the source of my problem.

I wish to apologize for not reviewing my code more carefully before posting and to thank you for the response.

In the future, I'll try to be more careful.

Not a problem, glad to help.

What matters that your bug has been resolved, not what caused it....

Quote:

---

I just realized that I made a really stupid mistake in another part of my code.

---

If your like me, this won't be the first or the last really stupid mistake (this week)......

IMO the test of a programmer is how you deal with your mistakes/bugs...