From: Scheie, Peter M <Petre.Scheie at gd-ms.com>
To: tpm2@lists.01.org
Subject: [tpm2] best way to verify tpm is alive
Date: Thu, 27 Sep 2018 20:24:39 +0000 [thread overview]
Message-ID: <3ca4069b2e3846fdba7e1d5d201b7e55@AZDC-MMB02.GD-MS.US> (raw)
[-- Attachment #1: Type: text/plain, Size: 746 bytes --]
What is the best way to verify the TPM is available, that is, that it hasn't died? I have a requirement to send an alert if the TPM stops working. We have snmp processes that run every five seconds, so I figure I can, say, check for something in /sys/class/tpm/tpm0 and as long as I get an expected response, I'll report that everything is fine. But what exactly should I look for? Is the simple presence of /sys/class/tpm/tpm0 sufficient, because it means the kernel thinks the TPM is there? If I cat /sys/class/tpm/tpm0/dev I get the major and minor numbers; I could look at those, or just test for the presence of the dev file on the premise that if the TPM failed that file would disappear. Is that a good test? Suggestions?
Peter
[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 5304 bytes --]
next reply other threads:[~2018-09-27 20:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-27 20:24 Scheie, Peter M [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-10-01 16:52 [tpm2] best way to verify tpm is alive Tadeusz Struk
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=3ca4069b2e3846fdba7e1d5d201b7e55@AZDC-MMB02.GD-MS.US \
--to=tpm2@lists.01.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).