On 1/11/2017 2:56 PM, James Bottomley wrote: > I'm playing with adding session based handles to the RM now. What I > find is that there's no escape from interpreting TPM2_FlushContext > because we need to know if we can release a session resource and we > can't rely on the continuation parameter alone. Given this problem, it > looks like we have no choice but to intercept TPM2_FlushContext and > emulate its execution, so we're going to have to manufacture at least > some TPM return codes within the kernel. Once we start down this path, > it's probably fairly easy to add for the other RM returns.
If this helps: FlushContext can have any handle (except permanent handles) In addition: Session - continue attribute false Sequence - SequenceComplete, EventSequenceComplete Manufacturing error codes in the kernel is one possibility. Another is to just map the unknown handle to TPM_RH_NULL and let the TPM do the rest. ------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi _______________________________________________ tpmdd-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tpmdd-devel
