From: "akuster" <akuster808@gmail.com>
To: yocto@lists.yoctoproject.org
Subject: [meta-security][PATCH 4/6] tpm2-pkcs11: update 1.2.0
Date: Fri, 12 Jun 2020 10:14:20 -0700 [thread overview]
Message-ID: <20200612171422.3380-4-akuster808@gmail.com> (raw)
In-Reply-To: <20200612171422.3380-1-akuster808@gmail.com>
add yaml package
Updated LICNESE
Signed-off-by: Armin Kuster <akuster808@gmail.com>
---
.../{tpm2-pkcs11_0.9.9.bb => tpm2-pkcs11_1.2.0.bb} | 11 +++++------
1 file changed, 5 insertions(+), 6 deletions(-)
rename meta-tpm/recipes-tpm2/tpm2-pkcs11/{tpm2-pkcs11_0.9.9.bb => tpm2-pkcs11_1.2.0.bb} (67%)
diff --git a/meta-tpm/recipes-tpm2/tpm2-pkcs11/tpm2-pkcs11_0.9.9.bb b/meta-tpm/recipes-tpm2/tpm2-pkcs11/tpm2-pkcs11_1.2.0.bb
similarity index 67%
rename from meta-tpm/recipes-tpm2/tpm2-pkcs11/tpm2-pkcs11_0.9.9.bb
rename to meta-tpm/recipes-tpm2/tpm2-pkcs11/tpm2-pkcs11_1.2.0.bb
index 351e03e..ce2dac0 100644
--- a/meta-tpm/recipes-tpm2/tpm2-pkcs11/tpm2-pkcs11_0.9.9.bb
+++ b/meta-tpm/recipes-tpm2/tpm2-pkcs11/tpm2-pkcs11_1.2.0.bb
@@ -2,15 +2,14 @@ SUMMARY = "A PKCS#11 interface for TPM2 hardware"
DESCRIPTION = "PKCS #11 is a Public-Key Cryptography Standard that defines a standard method to access cryptographic services from tokens/ devices such as hardware security modules (HSM), smart cards, etc. In this project we intend to use a TPM2 device as the cryptographic token."
SECTION = "security/tpm"
LICENSE = "BSD-2-Clause"
-LIC_FILES_CHKSUM = "file://LICENSE;md5=93645981214b60a02688745c14f93c95"
+LIC_FILES_CHKSUM = "file://LICENSE;md5=0fc19f620a102768d6dbd1e7166e78ab"
-DEPENDS = "autoconf-archive pkgconfig dstat sqlite3 openssl libtss2-dev tpm2-tools"
+DEPENDS = "autoconf-archive pkgconfig dstat sqlite3 openssl libtss2-dev tpm2-tools libyaml"
-SRC_URI = "git://github.com/tpm2-software/tpm2-pkcs11.git \
- file://bootstrap_fixup.patch \
- "
+SRC_URI = "git://github.com/tpm2-software/tpm2-pkcs11.git;branch=1.X \
+ file://bootstrap_fixup.patch "
-SRCREV = "6de3f6f9c6e0a4983f3fb90e35feb34906f8aea7"
+SRCREV = "8d8f137f65f1d61d66cc191947b59c378f23e97d"
S = "${WORKDIR}/git"
--
2.17.1
next prev parent reply other threads:[~2020-06-12 17:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-12 17:14 [meta-security][PATCH 1/6] tpm2-tools: update to 4.1.3 akuster
2020-06-12 17:14 ` [meta-security][PATCH 2/6] tpm2-tss: update to 2.4.1 akuster
2020-06-12 17:14 ` [meta-security][PATCH 3/6] tpm2-tss-engine: add branch to SRC_URI & update to tip akuster
2020-06-12 17:14 ` akuster [this message]
2020-06-12 17:14 ` [meta-security][PATCH 5/6] libtpm: update to 0.7.2 akuster
2020-06-12 17:14 ` [meta-security][PATCH 6/6] openscap: update to 1.3.3 akuster
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=20200612171422.3380-4-akuster808@gmail.com \
--to=akuster808@gmail.com \
--cc=yocto@lists.yoctoproject.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