You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @bklop,
we are aware that there are coding issues with choice sequences. These are somewhat special and require special handling.
Yet according to the requirements [V2G2-771] (ISO 15118-2) and [V2G20-771] (ISO 15118-20) ("The following message elements of the XML Signature framework shall not be used"), the KeyInfo element is not to be used. The only choice sequences occur in PGPData, which is an element in KeyInfo. (And in DIN 70121, messages and their elements are not signed.)
As long as there is no actual use for choice sequences, and the generated code compiles correctly, we see no need to implement them correctly.
In case of a choice sequence (for example in
din_PGPDataType
), the generated encoding code looks wrong/weird.For example. in
encode_din_PGPDataType
we find this:So if choice_1 is not used (i.e.
choice_1_isUsed
is 0), we still accesschoice_1.PGPKeyPacket
in theelse
case.The text was updated successfully, but these errors were encountered: