From: Tim K <tpm2 at bitzap.e4ward.com>
To: tpm2@lists.01.org
Subject: [tpm2] Re: How to initialize a used TPM2 module and thoughts on clevis
Date: Wed, 13 Jul 2022 15:59:13 +0000 [thread overview]
Message-ID: <20220713155913.2570.91658@ml01.vlan13.01.org> (raw)
In-Reply-To: 741ff3ee9707c1f3502d48e97496e1a47edfbb6d.camel@intel.com
[-- Attachment #1: Type: text/plain, Size: 910 bytes --]
My goal is to automate a cron job that requires credentials by keeping the credentials in a file that is encrypted using TPM2 via clevis. I am fully aware this does not add much protection if someone gets access to the OS, it is just so credentials do not sit in plain text in a file on disk, just protected by file permissions and it somewhat protects me from accidentally sync'ing the file to cloud or to some other backup (the file would at least be encrypted).
In order to do this, I don't think I can password protect the TPM2 hierarchies, otherwise there would be no way to automate it, I'd have to put the TPM2 passwords in the script for clevis to use (assuming clevis adds the option or that I just call the tpm2_* commands myself).
Any other suggestions how to make this better? My original idea was to use systemd-creds but it is not available in systemd v249 that Ubuntu 22.04 LTS ships with.
next reply other threads:[~2022-07-13 15:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 15:59 Tim K [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-08-19 16:17 [tpm2] Re: How to initialize a used TPM2 module and thoughts on clevis Roberts, William C
2022-07-13 14:53 Roberts, William C
2022-07-13 14:33 Roberts, William C
2022-07-12 22:25 Tim K
2022-07-12 21:32 Roberts, William C
2022-07-12 21:19 Roberts, William C
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=20220713155913.2570.91658@ml01.vlan13.01.org \
--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 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.