Re: CA's Key on Smart Card Problem

From: S. Pidgorny (slavickp_at_yahoo.com)
Date: 01/23/05

  • Next message: S. Pidgorny : "Re: Connecting a client with L2TP"
    Date: Sun, 23 Jan 2005 21:38:09 +1100
    
    

    Steve,

    As far as I know Microsoft is using HSMs for storing the root CA keys. At a
    very high level, HSM is the same thing as the smart cards: private key is
    protected and never leaves the device, Windows interacts with it using a
    CSP.

    So some guideleines would be really appreciated.

    Denis: I would try to use another card/CSP - to see if I'll have the same
    problem. I think that "not implemented" is kinda self-explanatory and some
    advanced CSP may indeed be required.

    -- 
    Svyatoslav Pidgorny, MVP, MCSE
    -= F1 is the key =-
    "Steve Riley [MSFT]" <steriley@microsoft.com> wrote in message
    news:54751632419367852042832@news.microsoft.com...
    > This really isn't something we test. Specifically, the problem you're
    seeing
    > is because the CA runs as LocalSystem. But when you're getting the prompt
    > to enter the PIN, that's running in your user context.
    >
    > More importantly, though, remember that the CA needs to access its own
    private
    > key every time it issues a certificate, so you'd need to leave the
    smartcard
    > in the reader all the time, which pretty much negates the reason for using
    > a smartcard.
    >
    > Steve Riley
    > steriley@microsoft.com
    >
    >
    >
    > > Hi.
    > > To improve the security of an offline root CA I want to
    > > store the CA's private Key on a Smart Card. During the
    > > installation process of the certificate services I
    > > selected a Smart Card CSP (Gemplus) and activated the
    > > checkbox "Allow this CSP to interact with the desktop".
    > > When the setup process generates the cryptografic key I
    > > have to enter the PIN of the Smart Card and then I got an
    > > error message box "An error occurred when setting the
    > > security access on the private key "Name of the CA", or
    > > the CSP selected does not support setting security access
    > > on private keys. Please make sure the CSP is installed
    > > correctly or select another CSP. Not implemented
    > > 0x80004001 (-2147467263)". After this the installation of
    > > the certificate services fails. I've already tried tested
    > > this with different Smart Cards and different Computers,
    > > but always got the same error.
    > > Can anyone help me with the error, or has anyone already
    > > installed the CA's Key on a Smart Card, which Smart Card
    > > and CSP shoud I use?
    > > Thanks in advance,
    > >
    > > Denis
    > >
    >
    >
    

  • Next message: S. Pidgorny : "Re: Connecting a client with L2TP"

    Relevant Pages

    • CryptImportKey fails
      ... I'm developing my own Smart Card CSP. ... my CSP is loading adn importing my private key ... CryptImportKey function fails with NTE_BAD_VERSION error. ...
      (microsoft.public.platformsdk.security)
    • CAs Key on Smart Card Problem
      ... store the CA's private Key on a Smart Card. ... installation process of the certificate services I ... checkbox "Allow this CSP to interact with the desktop". ...
      (microsoft.public.windows.server.security)
    • Re: CAs Key on Smart Card Problem
      ... so it is no problem that the smart card ... integrated) GemPlus csp with the 8k GemPlus card. ... >- needing to access the CA's private key ...
      (microsoft.public.windows.server.security)
    • Re: Alternative store vs. MY store
      ... store both the client cert and its associate private key on my USB memory ... your codes (CSP, ... indirect call to your CSP when one of your cert is involved in an operation. ...
      (microsoft.public.platformsdk.security)
    • Re: windows programming cryptography(problem in implementing a Sma
      ... Normally your smart card should have on-board key pair generation, ... First,I should include it’s header file in CSP code as below: ... HCRYPTPROV and remember that it refers to your CSP and to the ...
      (microsoft.public.platformsdk.security)