makecert

来源： https://stackoverflow.com/questions/22981766/makecert-is-not-recognized-as-an-internal-or-external-command-in-command-promp

来源： https://stackoverflow.com/questions/22981766/makecert-is-not-recognized-as-an-internal-or-external-command-in-command-promp

来源： https://stackoverflow.com/questions/22981766/makecert-is-not-recognized-as-an-internal-or-external-command-in-command-promp

问题 When I generate a certificate using MakeCert.exe, I want to change the key size from 1024 to 2048. Is this possible? Or do I need to setup a certificate authority (CA)? 回答1: Here the following syntax is used: makecert -pe -ss MY -$ individual -n "CN=your name here" -len 2048 -r Sorry I cannot test it, since I don't have Makecert. 回答2: A description of Makecert options can be found at MSDN, but I didn't see an explicit one for setting the key length. 来源： https://stackoverflow.com/questions

问题 I have recently been trying to make a SSL encrypted Server/Client in C#. I have followed this tutorial on MSDN, however, it required a certificate to be created for the server and client usage using makecert.exe so I found an example and it created the certificate fine: makecert -sr LocalMachine -ss My -n "CN=Test" -sky exchange -sk 123456 c:/Test.cer but now the problem is the server starts and waits for clients, when the client connects it uses the machine name which as far as I can gather

问题 I have recently been trying to make a SSL encrypted Server/Client in C#. I have followed this tutorial on MSDN, however, it required a certificate to be created for the server and client usage using makecert.exe so I found an example and it created the certificate fine: makecert -sr LocalMachine -ss My -n "CN=Test" -sky exchange -sk 123456 c:/Test.cer but now the problem is the server starts and waits for clients, when the client connects it uses the machine name which as far as I can gather

问题 I have recently been trying to make a SSL encrypted Server/Client in C#. I have followed this tutorial on MSDN, however, it required a certificate to be created for the server and client usage using makecert.exe so I found an example and it created the certificate fine: makecert -sr LocalMachine -ss My -n "CN=Test" -sky exchange -sk 123456 c:/Test.cer but now the problem is the server starts and waits for clients, when the client connects it uses the machine name which as far as I can gather

问题 I need to create a new cert and then locate it to obtain the serial number (to use it later to get the public and private keys). If I make a new certificate with makecert utility from Microsoft SDK's like this: makecert -r -pe -a sha1 -n "CN=ElektroSoft" -b 01/01/2013 -e 01/01/2050 -ss my -$ individual Then I suppose that cert will be stored in "my"... ..But when I try to list the "my" certificates I only get one entry, and is not my new certificate: C:\>CERTUTIL -store my my ================

问题 Is it possible to set Key Usage attributes using makecert, or any other tool I can use to generate my own test certificates? The reason I'm interested is that certificates used for BizTalk Server AS2 transport require a key usage of Digital Signature for signing and Data Encipherment or Key Encipherment for encryption/decryption, and I want to play around with this feature. I see how to set enhanced key usage attributes with makecert, but not key usage. 回答1: You can use the -eku option to

问题 If you decide to sign your code, you'll need: signcode.exe makecert.exe cert2spc.exe pvk2pfx.exe What's the best place to download these tools? Is there a way to do this without downloading large quantities of the Microsoft Windows SDK? 回答1: Start with the Windows SDK. That should have most of what you are looking for. Also, SignCode.exe has been deprecated after .NET 1.1. SignTool.exe is the replacement. Without downloading the SDK? In general, there are only a few SDK tools that are