Coverity issue

[shankru5]

Coverity complains that inside cyaml_sign_pad, for size = 0 case, the padding becomes ((8-0) * 8) = 64 and left shifting of 1UL by more than 63 bits is undefined behavior. Any idea what is the use case of size = 0 ? Could you please clarify what should be the resolution for this ?

[tlsa]

That could only happen with an invalid data_size in the client schema. So it's not something that can happen if you have a meaningful schema. The load code explicitly rejects it, but to create such a schema the user supplied schema has to be explicitly crafted to be broken.

[tlsa]

In fact, the save code will return CYAML_ERR_INVALID_DATA_SIZE anyway. Because the cyaml_data_read call will return an error.

I can rearrange it slightly which will hopefully suppress Coverity's false positive.

[shankru5]

Thank you @tlsa !