Conversation
jarkko

Jarkko Sakkinen

working on RFC patch for TPM2 asymmetric keys (will use null seed encrypted session) for supporting x509: https://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git/commit/?h=tpm2_key

https://datatracker.ietf.org/doc/draft-woodhouse-cert-best-practice/
1
0
0
jarkko

Jarkko Sakkinen

Reply to @jarkko
weekend as a kind of freelancer (at least for some time) is the best time for own patches. on plus, you don't have to care anything but the solving problem itself... paid or unpaid i enjoy this ;-)
1
0
1
jarkko

Jarkko Sakkinen

Reply to @jarkko
Edited 6 months ago
OK, now I have together ASN.1 parsing and new key subtype "tpm2_key_subtype", which is foundations for TPM2 asymmetric keys.

Only compile-tested ;-) This is now bare minimum to trial in QEMU. Lot's of dance relocating necessary bits of trusted keys code to the TPM driver (only ASN.1 parser at this point).
1
0
0
jarkko

Jarkko Sakkinen

Reply to @jarkko
Also a bit unclear what is best bet for authentication but it is a non-concern for RFC.

One possible argument for just authentication value at most would be that LUKS2 already blesses with TPM2 policy and kernel communicates by using null seed derived key. Using policy adds robustness but is it worth of added complexity to have two layers of policy, I really don't know at this point.
1
0
0
jarkko

Jarkko Sakkinen

Reply to @jarkko
So apparently (after searching) there is previous work https://patchwork.kernel.org/project/keyrings/cover/20200518172704.29608-1-prestwoj@gmail.com/. So I guess I just use some of it (and make it a separate patch with appropriate credits).
1
0
0
jarkko

Jarkko Sakkinen

Reply to @jarkko
Edited 6 months ago
I emailed to James Prestwood if he wants to rebase just the ops part from his patch set. My patch does the reorg and defines parser and key type so that is exactly left so better to ask. I also was also wondering TPM2_RSA_Decrypt vs TPM2_Sign/TPM2_VerifySignature. The old patch set uses the former.

Depending on response I'll take that patch from him or refactor it myself.
0
0
0
About social.kernel.org

Terms of service

  1. Please do not use this service in violation of the Linux Kernel Code of Conduct. Doing so will result in your account suspension with the referral of the matter to the CoC committee.

  2. "Repeating"/"boosting" someone else's status on this platform will be treated as endorsement and will fall under rule #1.

  3. You are encouraged to use this platform to promote your work on the Linux Kernel, but there is no restriction on permitted topics (with the exception of anything covered by #1 above).

  4. There is no requirement to post in English, but it should be considered the primary language of communication on this platform.

Privacy notice

The admins of this service have access to all posted statuses. They aren't looking, but if it's something they shouldn't know about, then you should not post it on this platform.

Please see the Linux Foundation Privacy Policy, which applies to this platform as well.

Getting your own account

If you would like an account on this instance, please check that the following applies to you:

  • You are listed in MAINTAINERS or CREDITS

  • OR: You have a kernel.org account or email address

  • OR: You have a long and established history of involvement with the Linux Kernel

If the above is true and you agree with the Terms of Service and Privacy Notice listed above, please use these instructions to request an account: