<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>Hi folks,</div> <div> </div> <div>I'm freelancer and for my client I'm currently working on a board with securtity features running Debian OS and SystemD. Logging is done by JournalD and should run in "sealing" mode. For that, the Logger must be activated by a special journalctl command, which generates a key (FSS) that shall be stored in a "safe" location. Since there is no possiblity (use case) for the key to leave the board, this "safe" location has to be somewhere on the board. For safety reasons, this obviously cannot be a simple cell in RAM.</div> <div> </div> <div>Fortunately, the board includes a TPM (Trusted Platform Module) that could be used for this purpose. However, when verifying the logger's storage the TPM has to be "opened" to get the key. This means that a kind of password is used for this, which is somewhere unprotected in RAM. So with the TPM, I've shifted my problem from key to password.</div> <div> </div> <div>In my opinion, the only way to successfully use a TPM is to let the verification be done by the TPM instead by the logger. In this case, the key will not leave the TPM. </div> <div> </div> <div>Has there been anything developed in that direction yet?</div> <div> </div> <div>Or maybe there is another approach to solve my problem?</div> <div> </div> <div>Have a nice day,</div> <div>Andreas</div></div></body></html>