base: pkcs11-provider: add recipe

[quaresmajose]

A pkcs#11 provider for OpenSSL 3.0+

This is an Openssl 3.x provider to access Hardware or Software
Tokens using the PKCS#11 Cryptographic Token Interface

Signed-off-by: Jose Quaresma [email protected]

[ricardosalveti]

Please add a description of the recipe as part of your commit message (body).

[ldts]

is this patch something that can be proposed to meta-security?

[quaresmajose]

Please add a description of the recipe as part of your commit message (body).

Add the description on commit and on the PR

[quaresmajose]

is this patch something that can be proposed to meta-security?

since nothing exists, it might be useful. after we test for a while i can send.

[ldts]

also, do we need to add the recipe to lmp-feature-tpm2.inc?

[quaresmajose]

I think so, if the idea is to have it installed when we have a machine with tpm2.

[ricardosalveti]

Yeah, once we find a stable rev and we know it works correctly we can send to meta-security.

[ricardosalveti]

LGTM, @ldts merge when needed.

[ldts]

testing now. btw when I build this is not landing in my wic and I dont want to trigger a clean build so just copying it manually to the target for testing

[quaresmajose]

Move to draft because we need to propose a change of BBFILE_PRIORITY in meta-security.

[quaresmajose]

I have already sent the patch to meta-security to change the layer priority but it can take a while for they land on kirstone stable branch, this if they are accepted.

Another solution can be rename our fork recipe to tpm2-pkcs11-fio_1.9.0.bb renaming acordante also our tpm2-pkcs11_%.bbappend and create a bbappend to replace the upstream version with ours in packagegroup-security-tpm2.bbappend

RDEPENDS:packagegroup-security-tpm2 += "tpm2-pkcs11-fio"
RDEPENDS:packagegroup-security-tpm2:remove = "tpm2-pkcs11"

A quick local test show that it works.

[ricardosalveti]

Will close this one as we're not going to use provider atm, and the other changes were merged in the other pr.