+ Reply to Thread
Results 1 to 4 of 4
  1. Senior Member
    Join Date
    Dec 2007
    Location
    Bay Area, California
    Posts
    430

    Certifications
    A+, Network+, MCP, MCDST, MCTS; Vista
    #1

    Default Explanation of how keys issued.

    Can someone please explain to me how public and private keys are issue using an enterprise CA? I'm lost on the concept. Thanks!
    Reply With Quote Quote  

  2. SS -->
  3. New Member royal's Avatar
    Join Date
    Jul 2006
    Location
    Chicago, IL
    Posts
    3,373
    #2
    Signing = You use your private key to sign the data, and then you send your public key to the receiving party so they can use your public key for verification.
    Encryption = You use the receiving parties public key so they can decrypt it with their private key.

    For issuing, when you generate a request, you create a private key and a CSR. When a CA manually approves, it generates some information you put into a .CER in which you fullfill your certificate request. The .CER basically contains your public key information that you import and bind to your private key when you created your initial request.

    Does this help?
    Reply With Quote Quote  

  4. MIPS processor please Mishra's Avatar
    Join Date
    Feb 2007
    Location
    Ashburn, VA
    Posts
    2,468

    Certifications
    MCSA:2012, MCITP:EA/SA, MCSE 2003, MCTS: Vista, VCP4, AAS
    #3
    They are issued through digital certificates.

    Where are you lost on the issue? And what study material are you reading which is confusing?
    Reply With Quote Quote  

  5. Senior Member
    Join Date
    Dec 2007
    Location
    Bay Area, California
    Posts
    430

    Certifications
    A+, Network+, MCP, MCDST, MCTS; Vista
    #4
    Quote Originally Posted by royal
    Signing = You use your private key to sign the data, and then you send your public key to the receiving party so they can use your public key for verification.
    Encryption = You use the receiving parties public key so they can decrypt it with their private key.

    For issuing, when you generate a request, you create a private key and a CSR. When a CA manually approves, it generates some information you put into a .CER in which you fullfill your certificate request. The .CER basically contains your public key information that you import and bind to your private key when you created your initial request.

    Does this help?
    Yes it does, I was using CBT Nuggets but woops theres another part to it!
    Reply With Quote Quote  

+ Reply to Thread

Social Networking & Bookmarks