Documentation:Certificate: Difference between revisions

Certificate

Latest revision as of 05:47, 20 January 2025

This page was created by Hans.karlsen@mdriven.net on 2017-01-17. Last edited by Edgar on 2025-01-20.

All certificates (Codesign and SSL) can be managed with the application DigiCertUtil.exe.

When you buy a cert, you often only get a cert file.

Importing is no problem, but exporting it as pfx is impossible in std windows. Use DigiCertUtil for this.

For developing, use localhost.

To allow Chrome to bypass the need for a valid certificate, enter this into the browser for https/SSL:

chrome://flags/#allow-insecure-localhost

@@ Line 1: / Line 1: @@
+<message>Write the content here to display this box</message>
 All certificates (Codesign and SSL) can be managed with the application DigiCertUtil.exe.
-When you buy a cert, you often only get a cert file; importing is no problem, but exporting it as pfx is impossible in std windows. Use DigiCertUtil for this.
+When you buy a cert, you often only get a cert file.
-For developing, use localhost - to allow Chrome to bypass the need for a valid certificate, enter this into the browser for https/SSL:
+Importing is no problem, but exporting it as pfx is impossible in std windows. Use DigiCertUtil for this.
-  <code>chrome://flags/#allow-insecure-localhost</code>
+For developing, use localhost.
+To allow Chrome to bypass the need for a valid certificate, enter this into the browser for https/SSL:
+  chrome://flags/#allow-insecure-localhost
   [[Category:Security]]
+{{Edited|July|12|2025}}