On Wed, Mar 20, 2024 at 10:04:13AM +0100, Dmitry Belyavskiy wrote:
> > Hi,
> >
> > In systemd, we recently added support for engines in various tools:
> > - systemd-{repart,measure} have --private-key-source=file|engine|provider
> > (this is C code).
> >
>
> As `provider` is a possible source, you will have to replace `engine` with
> a particular provider.
> tpm2 provider is on the way to rawhide, and pkcs11 provider has already
> landed, so TPMs and Yubikeys
$ nm build/src/shared/libsystemd-shared-256.so.0 |rg 'ENGINE.*OPENSSL'
U ENGINE_by_id@OPENSSL_3.0.0
U ENGINE_free@OPENSSL_3.0.0
U ENGINE_init@OPENSSL_3.0.0
U ENGINE_load_private_key@OPENSSL_3.0.0
That's how it looks with the upcoming systemd 256.
Zbyszek
--
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
