public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: sari.sercan@siemens.com
To: cip-dev@lists.cip-project.org
Subject: Re: [isar-cip-core][PATCH] encrypt_partition: evict stale systemd SRK handle before enrollment
Date: Fri, 17 Apr 2026 01:49:15 -0700	[thread overview]
Message-ID: <1451444.1776415755489458430@lists.cip-project.org> (raw)
In-Reply-To: <5166ed66-d402-4786-9b1e-bb8f7ecb13a1@siemens.com>

[-- Attachment #1: Type: text/plain, Size: 741 bytes --]

On Thu, Apr 16, 2026 at 07:03 PM, Jan Kiszka wrote:

> 
> On 16.04.26 16:56, Quirin Gylstorff wrote:
> 
>> 
>>> 
>>>> evict any stale handle before enrollment to avoid
>>>> "Failed to seal to TPM2: State not recoverable".
>>> 
>>> 
>> 
>> Could you also write when this error occurs.
> 
> 

This occurs when systemd-cryptenroll tries to create a new primary key
at the same time the same handle is occupied. with trixie shipping systemd >= v255,
this issue is easy reproduce in consecutive installations.

> 
> But then we would parse an error string and re-run the cryptenroll -
> does not sound very appealing this way.

By checking tpm2_getcap before evicting we can overcome this. I'll send a new version of it.

[-- Attachment #2: Type: text/html, Size: 907 bytes --]

  reply	other threads:[~2026-04-17  8:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-06 13:39 [isar-cip-core][PATCH] encrypt_partition: evict stale systemd SRK handle before enrollment Sari, Sercan
2026-04-16 14:30 ` Jan Kiszka
2026-04-16 14:56   ` Quirin Gylstorff
2026-04-16 16:03     ` Jan Kiszka
2026-04-17  8:49       ` sari.sercan [this message]
2026-04-17  7:49   ` sari.sercan

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=1451444.1776415755489458430@lists.cip-project.org \
    --to=sari.sercan@siemens.com \
    --cc=cip-dev@lists.cip-project.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