RE: Behavior when multiple access to one key container

From: lelteto (lelteto_at_discussions.microsoft.com)
Date: 02/25/05 

Date: Fri, 25 Feb 2005 08:55:09 -0800

The CSP MUST allow multiple contexts for the same container (and signature or
key exchange key). Any context can change it - and it shuld be reflected in
all other contexts. (Obviously, the CSP would need to serialize access to
keys to avoid one context starting an operation using the existing key value
and another context overwriting the key vie import or new key gen).
Container DELETE: The usual way to handle this is to delay the delete action
until all contexts to the container are closed. This is very similar behavior
to files and other objects in the OS; there all open handles must be closed
before the delete / destroy operation actually takes place.

Laszlo Elteto
SafeNet, Inc.

"Jack" wrote:

> Hello!
>
> How should a custom CSP react, when an application retrieves multiple
> contexts to one single key container?
> It id possible that one context alters or even deletes the container, and
> the other tries to access it - this would produce an error.
>
> Thanks
>
>
>

Relevant Pages

  • RE: CSP calls for typical scenarios?
    ... Even if you don't free memory why you can't handle another logon? ... block on one - even if the contexts are for the same container). ... That's a bug in the app, not in your CSP. ... Laszlo Elteto ...
    (microsoft.public.platformsdk.security)
  • Re: Omnifocus - assign multiple contexts to actions?
    ... Ian McCall wrote: ... insistence on single contexts by simplifying them down to the barest ... vague context possible. ... This method has the side effect that I have to check multiple contexts ...
    (uk.comp.sys.mac)
  • Re: google "top coder" contest = stacked against C++ coders
    ... > can be used in multiple contexts (and even more so if used in many vastly ... > different contexts), not if it can be used in every context that you could ... So your definition of reuse is that code *might* work? ... definition is more strange, that the code should work always or just ...
    (alt.comp.lang.learn.c-cpp)
  • Re: google "top coder" contest = stacked against C++ coders
    ... > can be used in multiple contexts (and even more so if used in many vastly ... > different contexts), not if it can be used in every context that you could ... So your definition of reuse is that code *might* work? ... definition is more strange, that the code should work always or just ...
    (comp.lang.cpp)