All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach via buildroot <buildroot@buildroot.org>
To: Jarkko Sakkinen <jarkko@kernel.org>
Cc: Stefan Berger <stefanb@linux.ibm.com>,
	"Yann E . MORIN" <yann.morin.1998@free.fr>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v4 2/3] package/libtpms: add host package
Date: Tue, 21 May 2024 13:39:16 +0300	[thread overview]
Message-ID: <877cfnphyj.fsf@tarshish> (raw)
In-Reply-To: <20240521103154.32660-3-jarkko@kernel.org> (Jarkko Sakkinen's message of "Tue, 21 May 2024 13:31:53 +0300")

Hi Jarkko,

On Tue, May 21 2024, Jarkko Sakkinen wrote:
> diff --git a/package/Config.in b/package/Config.in
> index 1b6a5b0dab..30b76349ec 100644
> --- a/package/Config.in
> +++ b/package/Config.in
> @@ -1569,6 +1569,7 @@ menu "Crypto"
>  	source "package/libssh/Config.in"
>  	source "package/libssh2/Config.in"
>  	source "package/libtomcrypt/Config.in"
> +	source "package/libtpms/Config.in"
>  	source "package/libuecc/Config.in"
>  	source "package/libxcrypt/Config.in"
>  	source "package/mbedtls/Config.in"
> diff --git a/package/libtpms/Config.in b/package/libtpms/Config.in
> new file mode 100644
> index 0000000000..335a5bc7b6
> --- /dev/null
> +++ b/package/libtpms/Config.in
> @@ -0,0 +1,20 @@
> +config BR2_PACKAGE_LIBTPMS

You are not adding a target package, right? So this config symbol
doesn't do anything.

baruch

> +	bool "libtpms"
> +	select BR2_PACKAGE_LIBTOOL
> +	select BR2_PACKAGE_OPENSSL
> +	help
> +	  Libtpms is a library that targets the integration of TPM
> +	  functionality into hypervisors, primarily into Qemu. Libtpms
> +	  provides a very narrow public API for this purpose so that
> +	  integration is possible. Only the minimum of necessary APIs
> +	  are made publicly available.
> +
> +	  It is assumed that the user of libtpms is familiar with the
> +	  concepts of the Trusted Platform Module (TPM). For the
> +	  interaction with libtpms it is necessary to know how to
> +	  construct valid TPM commands and to be able to parse their
> +	  results. It is not within the scope of libtpms's documentation
> +	  to provide background on this. See the section on references
> +	  below.
> +
> +	  https://github.com/stefanberger/libtpms/wiki

-- 
                                                     ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2024-05-21 10:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-21 10:31 [Buildroot] [PATCH v4 0/3] swtpm and libtpms host packages Jarkko Sakkinen
2024-05-21 10:31 ` [Buildroot] [PATCH v4 1/3] package/json-glib: add host build Jarkko Sakkinen
2024-05-21 10:31 ` [Buildroot] [PATCH v4 2/3] package/libtpms: add host package Jarkko Sakkinen
2024-05-21 10:39   ` Baruch Siach via buildroot [this message]
2024-05-21 10:47     ` Jarkko Sakkinen
2024-05-21 11:15       ` Baruch Siach via buildroot
2024-05-21 10:31 ` [Buildroot] [PATCH v4 3/3] package/swtpm: " Jarkko Sakkinen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877cfnphyj.fsf@tarshish \
    --to=buildroot@buildroot.org \
    --cc=baruch@tkos.co.il \
    --cc=jarkko@kernel.org \
    --cc=stefanb@linux.ibm.com \
    --cc=yann.morin.1998@free.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.