Skip to main content
AI Assist is now on Stack Overflow. Start a chat to get instant answers from across the network. Sign up to save and share your chats.

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • 4
    @jlp - No, OpenSSL is not a part of Windows, it is a standalone software package (openssl.org), available also for Windows (openssl.org/related/binaries.html) Commented Sep 6, 2011 at 15:32
  • 2
    If the first command fails, you can do this: open your .key and .spc in notepad, copy the whole content of both files and create a new one called newfile.key. Then run again the openssl x509 -text -in newfile.key command and it should work. Then you can convert the newfile.key to .pfx using openssl pkcs12 -export -out newfile.pfx -in newfile.key Commented Nov 13, 2013 at 1:32
  • 1
    @dacap: Thanks - yes, if you have the key and certificate in separate files you can combine them as you describe. You can also use the method @fig suggested below, using -inkey for the key file, and -in for the certificate (.spc) file... Commented Nov 20, 2013 at 3:53
  • ... Why Microsoft doesn't provide the function to convert .key to .pvk in pvk2pfx or signtool? Commented Nov 28, 2019 at 6:33