Ephemeral key containers

From: Jerome (9velcy002_at_sneakemail.com)
Date: 09/17/05

  • Next message: pklinkoff: "Pinvoke, address space and the .net security framework" 
    Date: 17 Sep 2005 13:32:51 -0700

    Using the .NET 1.1 crypto classes, is there any way of specifying that
    the crypto service providers should use ephemeral (in-memory-only) key
    containers? In other words, is there any way of instantiating
    RSACryptoServerProvider so that it calls CryptAcquireContext with
    CRYPT_VERIFYCONTEXT underneath the hood and doesn't touch a disk-based
    key store?

    Calling the Windows Crypto API through P/Invoke is not acceptable. I
    need to use the .NET classes if possible so that I have the hope of
    cross-platform compatibility and running without Full Trust.

  • Next message: pklinkoff: "Pinvoke, address space and the .net security framework"

    Relevant Pages

    • Re: Question about Encryption Algorithms
      ... i assume you mean in the context of the .NET Frameworks? ... there's two types of crypto classes in the Frameworks. ...
      (microsoft.public.security)
    • Re: Variation on prisoners dilemma
      ... identical containers, shuffle them, and exchange them one at a time, ... Your solution corresponds roughly to Phil's suggestion of Alice and ... To make it more closely match the "crypto" case, ... therefore Alice has no way of knowing that Bob isn't opening each ...
      (rec.puzzles)