Documentation:Certificate: Difference between revisions

Certificate

Latest revision as of 15:28, 10 February 2024

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

This page was edited 94 days ago on 02/10/2024. What links here

@@ Line 1: / Line 1: @@
-All certificates (codesign and ssl) can be managed with the application DigiCertUtil.exe.
+All certificates (Codesign and SSL) can be managed with the application DigiCertUtil.exe.
-When you buy a cert you often only get a cer file - and importing is no problem - but export it as pfx is not possible in std windows - use DigiCertUtil for this.
+When you buy a cert, you often only get a cert file.
-For developing you use localhost - to allow for chrome to bybpass 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|2024}}