]> git.ipfire.org Git - people/ms/strongswan.git/commit
signature-params: Reject schemes other than RSASSA-PSS with parameters
authorTobias Brunner <tobias@strongswan.org>
Mon, 4 Oct 2021 10:10:37 +0000 (12:10 +0200)
committerTobias Brunner <tobias@strongswan.org>
Thu, 14 Oct 2021 16:59:07 +0000 (18:59 +0200)
commit02e4f994ecadd4f2fa2858d01b0530be45e9794d
tree13aac8ea65da11372b48581f5a531b3e5aef09c5
parentf061dedcb70ed88214e730fff842d06e7857b333
signature-params: Reject schemes other than RSASSA-PSS with parameters

NULL parameters (for classic PKCS#1 signature schemes) are explicitly
allowed (for any schemes for now), but we only expect parameters for
RSASSA-PSS.  Before enforcing this, it was possible to modify the
parameters in the signatureAlgorithm field of the outer X.509 Certificate
structure to something different than the signature field of the signed,
inner tbsCertificate structure, allowing generating infinite versions
of valid certificates with different binary encodings.  Now we accept at
most two (NULL and absent parameters).
src/libstrongswan/credentials/keys/signature_params.c
src/libstrongswan/tests/suites/test_signature_params.c