> > >I proposed the following as an alternative:> > >> > >* Print a message to the klog (which log level would be> > >appropriate?). > > Info?> > Maybe warn, definitely not err > > Since the driver does not fail usually warn would make sense but since> here even allowing to continue to use such TPM is questionable I would> use error here.

It does not really matter. People ignore the messages unless lookingfor something specific as you already noticed. Warn seems adequatebecause the cipher is weaker than expected but not known tobe compromised. People who care can look up the message. People whodon't care will ignore it even if it's crit.

> > People anyway ignore klog too easily so using warn would be a mistake> in my opinion. It's like saying that nothing serious is happening> here, move along.> > Do you think so?> > > >* Possibly sleep for few seconds. Is this a good idea? > > Helps how? > > Obviously to get it noticed that the system integrity is broken.

Overly intrusive. The message is not visible with splashscreens anyway.

Presumably other stuff can run in parallel these days spamming withunrelated messages.

> > > >While writing this email yet another alternative popped into my> > >mind: what if we allow only in-kernel use but disallow the use> > >of /dev/tpm0? You could still use trusted keys.> > > > > No, same terrible idea since you block the upgrade path.> > Upgrade tools work from userspace via the kernel driver. > > So /dev/tpm0 is necessary. > > Right! How stupid of me (my previous response to Jerry) :-) Of course> you can have special commands and talk to the TPM to do the upgrade> even if it is part of the platform and not connected to a standard> bus.

Unless the upgrade command is disabled to not disrupt the platform, ofcourse.