package/tpm2-tss: force libopenssl as openssl provider
authorCarlos Santos <casantos@datacom.com.br>
Wed, 21 Nov 2018 02:44:37 +0000 (00:44 -0200)
committerThomas Petazzoni <thomas.petazzoni@bootlin.com>
Sat, 24 Nov 2018 14:08:39 +0000 (15:08 +0100)
commitb122623145a963d009e105131d0eeac099c3759b
tree254c08fa35af5b66d53b2f50b33cb4c144155f36
parente0f49e6484015351f697ab843da25b5421c23fd6
package/tpm2-tss: force libopenssl as openssl provider

Select BR2_PACKAGE_OPENSSL_FORCE_LIBOPENSSL and drop the patch to
compile with libressl.

The discussion with the tpm2-tss developers led to the conclusion that
libressl lacks some required functionalities. Quoting Andreas Fuchs[1]:
"LibreSSL does not support OAEP-mode with labels at all, even though the
internal OAEP-padding-function includes the parameters already. [...]
Further, the internal OAEP-padding-function does not support variable
hash algs, but staticly uses SHA1."

Notice that there will NOT be an option to use libgcrypt. OpenSSL will
soon become the default ESAPI crypto backend to prevent the problem of
forcing applications to link against both libgcrypt and libssl[2].

1. https://github.com/tpm2-software/tpm2-tss/pull/1207#issuecomment-440217659
2. https://github.com/tpm2-software/tpm2-tss/issues/1169

Signed-off-by: Carlos Santos <casantos@datacom.com.br>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
package/tpm2-tss/0001-ESYS-Fix-build-with-LibreSSL.patch [deleted file]
package/tpm2-tss/Config.in