public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Joonas Niilola" <juippis@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/libtpms/
Date: Wed, 27 Apr 2022 10:19:18 +0000 (UTC)	[thread overview]
Message-ID: <1651052487.e40f9c59e293df44f1cae8ac2a28d7efec9fdd15.juippis@gentoo> (raw)

commit:     e40f9c59e293df44f1cae8ac2a28d7efec9fdd15
Author:     Christopher Byrne <salah.coronya <AT> gmail <DOT> com>
AuthorDate: Mon Apr 25 21:21:17 2022 +0000
Commit:     Joonas Niilola <juippis <AT> gentoo <DOT> org>
CommitDate: Wed Apr 27 09:41:27 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e40f9c59

dev-libs/libtpms: add 0.9.4

Signed-off-by: Christopher Byrne <salah.coronya <AT> gmail.com>
Signed-off-by: Joonas Niilola <juippis <AT> gentoo.org>

 dev-libs/libtpms/Manifest             |  1 +
 dev-libs/libtpms/libtpms-0.9.4.ebuild | 47 +++++++++++++++++++++++++++++++++++
 2 files changed, 48 insertions(+)

diff --git a/dev-libs/libtpms/Manifest b/dev-libs/libtpms/Manifest
index 90ac3d3e08ab..1daa4b399f98 100644
--- a/dev-libs/libtpms/Manifest
+++ b/dev-libs/libtpms/Manifest
@@ -1 +1,2 @@
 DIST libtpms-0.9.3.tar.gz 1263192 BLAKE2B a58cc2f76775f0a0a266cf6da898d6c8e310998c201dc47a802d67fc07dbe1632a68e81b78da68a6350e1d64727c7b47154479b4d9bc19a55324a2d881cad94f SHA512 8616c712f958c28a415b0a97a3a24f439f757682c4b60642584eb13e4ab2d7895838e8e6e57936ff583259506f9b379ec47c76d5780c1b257f25513a5911c3cb
+DIST libtpms-0.9.4.tar.gz 1264030 BLAKE2B 56731b913145afcd49fae13f0fcbe4fc147edf206a44849cef45ed34a7644f0894bb6ab5dcb72d620eb1ab121bf4e821fe7893557508af394585171133d659e2 SHA512 ae3e2613bc31d98c10def546c70d0c25bd1246af5090268afa0411502bfd0e454967046ebcd9025350976817441e595fa4e21562f800285db98331e4c2743505

diff --git a/dev-libs/libtpms/libtpms-0.9.4.ebuild b/dev-libs/libtpms/libtpms-0.9.4.ebuild
new file mode 100644
index 000000000000..fc15af9bf0f4
--- /dev/null
+++ b/dev-libs/libtpms/libtpms-0.9.4.ebuild
@@ -0,0 +1,47 @@
+# Copyright 1999-2022 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=8
+
+inherit autotools
+
+DESCRIPTION="Library providing software emultion of a TPM"
+HOMEPAGE="https://github.com/stefanberger/libtpms"
+SRC_URI="https://github.com/stefanberger/libtpms/archive/v${PV}.tar.gz -> ${P}.tar.gz"
+LICENSE="BSD"
+SLOT="0"
+KEYWORDS="~amd64 ~arm ~arm64 ~ppc ~ppc64 ~riscv ~x86"
+
+DEPEND="dev-libs/openssl:="
+RDEPEND="${DEPEND}"
+BDEPEND="virtual/pkgconfig"
+
+PATCHES=(
+	"${FILESDIR}/${PN}-0.9.0-Remove-WError.patch"
+)
+
+src_prepare() {
+	default
+	eautoreconf
+}
+
+src_configure() {
+	econf \
+		--with-openssl
+}
+
+src_install() {
+	default
+	find "${ED}" -name '*.la' -delete || die
+}
+
+pkg_postinst() {
+	if [[ ${REPLACING_VERSIONS} ]] && ver_test ${REPLACING_VERSIONS} -lt 0.8.0; then
+		elog "Versions of libtpms prior to 0.8.0 generate weaker than expected TPM 2.0 RSA"
+		elog "keys due to a flawed key creation algorithm. Because fixing this would render"
+		elog "existing sealed data inaccessible, to use the corrected algorithm, the old"
+		elog "TPM state file must be deleted and a new TPM state file created. Data still"
+		elog "sealed using the old state file will be permanently inaccessible. For the"
+		elog "details see https://github.com/stefanberger/libtpms/issues/183"
+	fi
+}


             reply	other threads:[~2022-04-27 10:19 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-27 10:19 Joonas Niilola [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-01-06  4:16 [gentoo-commits] repo/gentoo:master commit in: dev-libs/libtpms/ Sam James
2025-01-06  3:35 Sam James
2025-01-06  3:32 Sam James
2025-01-06  3:28 Sam James
2025-01-06  3:24 Sam James
2025-01-06  3:24 Sam James
2023-04-19  4:29 John Helmert III
2023-03-30 17:17 Arthur Zamarin
2023-03-17 11:44 Arthur Zamarin
2023-03-17 11:38 Arthur Zamarin
2023-03-17  9:04 Arthur Zamarin
2023-03-11 17:15 Sam James
2023-02-20 14:47 Arthur Zamarin
2023-02-20 13:50 Sam James
2023-02-20 13:50 Sam James
2023-02-20  9:39 Joonas Niilola
2022-07-09 12:26 Matthew Smith
2022-05-20  9:17 Agostino Sarubbo
2022-05-19  9:27 Agostino Sarubbo
2022-05-17 12:38 Agostino Sarubbo
2022-05-17 12:37 Agostino Sarubbo
2022-05-17  9:59 Agostino Sarubbo
2022-04-27 10:19 Joonas Niilola
2022-03-11  0:04 Ionen Wolkens
2022-03-11  0:04 Ionen Wolkens
2022-03-10  6:48 Yixun Lan
2021-11-28  0:20 Ionen Wolkens
2021-11-28  0:20 Ionen Wolkens
2021-09-14  7:39 Joonas Niilola
2021-09-14  7:39 Joonas Niilola
2021-09-13  6:33 Joonas Niilola
2021-09-08  1:25 Sam James
2021-09-04  6:26 Joonas Niilola
2021-09-04  6:26 Joonas Niilola
2021-09-04  6:26 Joonas Niilola
2021-07-24 15:22 Sam James
2021-07-15  6:01 Ionen Wolkens
2021-07-12 21:59 Sam James
2021-07-06 17:59 Sam James
2021-06-27 17:29 Matthias Maier
2021-06-22  9:02 Joonas Niilola
2021-06-22  9:02 Joonas Niilola
2021-05-01  7:37 Mikle Kolyada
2021-04-25  8:00 Michał Górny
2020-11-01  6:14 Joonas Niilola
2020-11-01  6:14 Joonas Niilola
2020-10-08  6:57 Joonas Niilola
2020-08-05 12:19 Joonas Niilola
2020-08-05 12:19 Joonas Niilola
2020-06-24 15:58 Joonas Niilola
2020-02-19 13:32 Joonas Niilola
2020-02-19 13:32 Joonas Niilola
2019-08-02 11:25 Joonas Niilola

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=1651052487.e40f9c59e293df44f1cae8ac2a28d7efec9fdd15.juippis@gentoo \
    --to=juippis@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox