TPM_RC_CONTEXT_GAP is an error the TPM is allowed to return when the counter that ensures the uniqueness of context saved sessions overflows. The solution, according to the manual, is to re-load and save the oldest session because that frees the old value causing the gap.
This leads to a problem: we have to have access to the session context to pull this trick, and that means we have to disallow TPM users from calling ContextSave on a session otherwise they could DoS us by inducing an unremediable TPM_RC_CONTEXT_GAP error (simply by keeping the saved session and never loading it). We could pull other tricks, like emulating ContextSave and ContextLoad for sessions, but I can't actually see why any legitimate application would want to save a session context at all. Unless anyone can see a way around this particular problem, I'll go ahead and implement it in the next iteration of the session exhaustion patch. James ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ tpmdd-devel mailing list tpmdd-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tpmdd-devel
