Yep, thanks. We got it, turns out the user wasn’t giving me quite the right info as to what they were seeing and was throwing me off of where to look. Ryan
From: [email protected] [mailto:[email protected]] On Behalf Of Christopher Bodnar Sent: Friday, February 12, 2016 10:35 AM To: [email protected] Subject: [NTSysADM] RE: a stupid certificate question You should see something like this to make the choice when generating the CSR: [cid:[email protected]] From: [email protected] [mailto:[email protected]] On Behalf Of Ryan Shugart Sent: Friday, February 12, 2016 12:08 PM To: [email protected] Subject: [NTSysADM] a stupid certificate question OK, I know this is obvious but I’m not seeing it and I’m not finding anything useful on Google which surprises me. If you are requesting a certificate through the certificates MMC snap-in, where do you select a key strength? We had a guy just request a new cert for an internal web server and he got a 1024-bit key, whereas the previous certificate had a 2048-bit key. Trying to figure out how that happened. Thanks. Ryan Ryan Shugart Windows System Administrator MiTek USA, MiTek Denver 303-723-4975 MiTek Holdings, Inc., 2011-2014, All Rights Reserved ________________________________ This communication (including any attachments) contains information which is confidential and may also be privileged. It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s), please note that any distribution, copying, or use of this communication or the information in it is strictly prohibited. If you have received this communication in error, please notify the sender immediately and then destroy any copies of it. ________________________________ ----------------------------------------- This message, and any attachments to it, may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are notified that any use, dissemination, distribution, copying, or communication of this message is strictly prohibited. If you have received this message in error, please notify the sender immediately by return e-mail and delete the message and any attachments. Thank you.
