@@ -1117,7 +1117,7 @@ Below are the procedure steps. Clicking on any of the link takes directly to the
With the sign_test.bat script you just signed the VeraCrypt executables. This is necessary, since Windows only accepts drivers, which are trusted by a signed Certificate Authority.
- Since you did not use the official VeraCrypt signing certificate to sign your code, but a public development version, you have to import and therefore trust the certifcates used.
+ Since you did not use the official VeraCrypt signing certificate to sign your code, but a public development version, you have to import and therefore trust the certificates used.
-
Open the folder "src/Signing"
@@ -1132,6 +1132,7 @@ Below are the procedure steps. Clicking on any of the link takes directly to the
- TestCertificates/idrix_SHA256TestRootCA.crt
- TestCertificates/idrix_TestRootCA.crt
+ Note: If prompted, the password for .pfx certificates is idrix.
@@ -1193,7 +1194,7 @@ Below are the procedure steps. Clicking on any of the link takes directly to the
Go to the top menu "Digital Signatures". Her you will find two signatures in the Signature list
Check both by double clicking on it. If the headline says "The certificate in the signature cannot be verified", the corresponding signing certificate was not imported correctly.
- Click on "View Certificate" and then on "Install Certificate..." to import the certificate to your certificate storage
+ Click on "View Certificate" and then on "Install Certificate..." to import the certificate to your certificate storage. For the Root certificates, you may need to choose "Place all certificates in the following store", and select the "Trusted Root Certification Authorities" store.
--
cgit v1.2.3