Re: Creating certificate request with 2 Signers

From: Vishal Agarwal[MSFT] (vishala_at_online.microsoft.com)
Date: 05/29/05

  • Next message: Vishal Agarwal[MSFT]: "Re: Problem signing openSSL certificate request..."
    Date: Sat, 28 May 2005 18:13:37 -0700
    
    

    The only way I know of to do this is by creating and signing a CMC request,
    then using certreq -sign to add an additional signature.

    You could also write code to call the CAPI2 Messaging APIs (CryptMsg*) to
    add a signature.

    CAPICOM may be able to add a signature to an existing PKCS7 request.

    To create the original request with one signer, you can script xenroll
    interfaces or use certreq -new.

    Thanks,

    Vishal Agarwal[MSFT]

    -- 
    This posting is provided "AS IS" with no warranties, and confers no rights
    <noolyg@yahoo.com> wrote in message 
    news:1117107510.166360.176290@o13g2000cwo.googlegroups.com...
    > Hello,
    >
    > Is there a way (using Enroll APIs for MS CA 2003) to enroll a
    > certificate on behalf of a user with 2 enrollment agents?
    >
    >
    > Thanks.
    > 
    

  • Next message: Vishal Agarwal[MSFT]: "Re: Problem signing openSSL certificate request..."

    Relevant Pages

    • Re: how can we restrict what certificate WSE will use?
      ... the valid x509 certificate which is used to identify him'. ... X509SecurityTokenManager to verify the request is from a trusted client. ... the problem is that he can not passed the authentication (suppose we ... > decrypte and signature validation process. ...
      (microsoft.public.dotnet.framework.webservices.enhancements)
    • Re: how can we restrict what certificate WSE will use?
      ... \par Microsoft Online Support ... \par you mentioned 'since his private key is not valid so, the signature of his ... \par in a request signed with his valid private key, and since his public key is ...
      (microsoft.public.dotnet.framework.webservices.enhancements)
    • Re: how can we restrict what certificate WSE will use?
      ... \par X509SecurityTokenManager to verify the request is from a trusted client. ... \par Subject: Re: how can we restrict what certificate WSE will use? ... \par there seems to be some disconnections where you say 'the hacker dosn't have ... \par> decrypte and signature validation process. ...
      (microsoft.public.dotnet.framework.webservices.enhancements)
    • Re: how can we restrict what certificate WSE will use?
      ... you mentioned 'since his private key is not valid so, the signature of his ... in a request signed with his valid private key, and since his public key is ... > As for the question on the X509 certificate verification in .net ...
      (microsoft.public.dotnet.framework.webservices.enhancements)
    • how can we restrict what certificate WSE will use?
      ... webservice, each client will send in properly encrypted and signed request, ... WSE will take care of decryption and verification of the signature, ... reaching my code where I verify it's a trusted client. ...
      (microsoft.public.dotnet.framework.webservices.enhancements)