From: jacobmyers-codeninja <jacobmyers-codeninja@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: tpm2-totp-0.3.0
Date: Mon, 08 Aug 2022 23:43:54 +0200 [thread overview]
Message-ID: <20220808214354.jva9G1HK-_l5UIb0g3SA41DRUAD1J-0SF6vWHzBplnk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38515@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 511 bytes --]
New comment by jacobmyers-codeninja on void-packages repository
https://github.com/void-linux/void-packages/pull/38515#issuecomment-1208643723
Comment:
tpm2-tss is in the packages already, and it appears to be what tpm2-tools is using for everything. It might make sense to just include tools to also get the bonus of all the unit tests for all the tooling.
At least if it looks like that would be easy enough to include, the tools does seem to include a lot of useful small utilities for tpm2 management.
next prev parent reply other threads:[~2022-08-08 21:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-07 10:38 [PR PATCH] " tranzystorek-io
2022-08-07 10:39 ` tranzystorek-io
2022-08-08 4:18 ` jacobmyers-codeninja
2022-08-08 9:10 ` tranzystorek-io
2022-08-08 9:13 ` tranzystorek-io
2022-08-08 21:43 ` jacobmyers-codeninja [this message]
2022-08-08 21:52 ` [PR PATCH] [Updated] " tranzystorek-io
2022-08-08 22:02 ` [PR PATCH] [Updated] New packages: tpm2-totp-0.3.0, tpm2-tools-5.2 tranzystorek-io
2022-08-08 22:13 ` tranzystorek-io
2022-08-08 22:31 ` tranzystorek-io
2022-08-08 23:24 ` tranzystorek-io
2022-08-09 3:03 ` jacobmyers-codeninja
2022-08-09 6:54 ` tranzystorek-io
2022-08-09 17:38 ` jacobmyers-codeninja
2022-08-13 6:40 ` [PR PATCH] [Updated] " tranzystorek-io
2022-08-24 10:37 ` tranzystorek-io
2022-09-10 13:48 ` paper42
2022-09-10 13:51 ` [PR REVIEW] " paper42
2022-09-10 14:27 ` [PR PATCH] [Updated] " tranzystorek-io
2022-09-10 14:32 ` [PR REVIEW] " tranzystorek-io
2022-09-13 20:12 ` [PR PATCH] [Merged]: " paper42
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=20220808214354.jva9G1HK-_l5UIb0g3SA41DRUAD1J-0SF6vWHzBplnk@z \
--to=jacobmyers-codeninja@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).