xmlsecurity: fix AES-GCM code differently
commit4a532e651b9fd4c9b24b017d2e1d099ee76ceed8
authorThorsten Behrens <thorsten.behrens@allotropia.de>
Fri, 22 Dec 2023 21:44:15 +0000 (22 22:44 +0100)
committerThorsten Behrens <thorsten.behrens@allotropia.de>
Sat, 23 Dec 2023 23:29:34 +0000 (24 00:29 +0100)
treeb6e3c935d1f1347e1ad60e3aefd28b9963f6c845
parentdbe05a624ca53db83bedbc049791cc215ee6d46b
xmlsecurity: fix AES-GCM code differently

With PCH, the earlier workaround with NSS_PKCS11_2_0_COMPAT breaks -
so lets fix this with conditionals, its only two places.

Follow-up commit to 9276d5338ef04209b007bbc705e4c023cf181456

Change-Id: I7d3292304d83d784ee9dce5cdc62b4a028ff333a
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/161204
Tested-by: Jenkins
Reviewed-by: Thorsten Behrens <thorsten.behrens@allotropia.de>
xmlsecurity/source/xmlsec/nss/ciphercontext.cxx