On 1/20/2017 8:23 AM, Jarkko Sakkinen wrote: > > I'm talking about not trying to detect if something gets deleted. When > something gets created you would go through the global list of sessions > and check if it is used. If so, it must be that the session was deleted > at some point.
Are you saying that, when a process flushes (or continue = false) a session, this code won't actually flush the context? You'll wait until another startauthsession creates a handle, and then delete other occurrences of it? If so, I wonder about this: A process creates, uses, and flushes a session. It then tries to use the session again. It should fail, but will it with this design? There may also be a security reason that an application expects the context to be flushed when requested. E.g., it could have a satisfied policy. ------------------------------------------------------------------------------ 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 [email protected] https://lists.sourceforge.net/lists/listinfo/tpmdd-devel
