diff --git a/doc/chm/VeraCrypt User Guide.chm b/doc/chm/VeraCrypt User Guide.chm
index 61fc46f5..9fef902a 100644
Binary files a/doc/chm/VeraCrypt User Guide.chm and b/doc/chm/VeraCrypt User Guide.chm differ
diff --git a/doc/html/Digital Signatures.html b/doc/html/Digital Signatures.html
index 17717b48..63a35cde 100644
--- a/doc/html/Digital Signatures.html
+++ b/doc/html/Digital Signatures.html
@@ -77,23 +77,30 @@ If you do not see the above sentence, the file is very likely corrupted. Note: O
How to Verify PGP Signatures
To verify a PGP signature, follow these steps:
-- Install any public-key encryption software that supports PGP signatures. For Windows, you can download
-Gpg4win. For more information, you can visit
-https://www.gnupg.org/.
- Create a private key (for information on how to do so, please see the documentation for the public-key encryption software).
-
- Download our PGP public key from IDRIX website (https://www.idrix.fr/VeraCrypt/VeraCrypt_PGP_public_key.asc) or from a trusted public key repository
- (ID=0x54DDD393), and import the downloaded key to your keyring (for information on how to do so, please see the documentation for the public-key encryption software). Please check that its fingerprint is
-993B7D7E8E413809828F0F29EB559C7C54DDD393.
- Sign the imported key with your private key to mark it as trusted (for information on how to do so, please see the documentation for the public-key encryption software).
+ - Install any public-key encryption software that supports PGP signatures. For Windows, you can download Gpg4win. For more information, you can visit https://www.gnupg.org/.
+- Create a private key (for information on how to do so, please see the documentation for the public-key encryption software).
+- Download our PGP public key from IDRIX website (https://www.idrix.fr/VeraCrypt/VeraCrypt_PGP_public_key.asc) or from a trusted public key repository
+ (ID=0x680D16DE), and import the downloaded key to your keyring (for information on how to do so, please see the documentation for the public-key encryption software). Please check that its fingerprint is
+5069A233D55A0EEB174A5FC3821ACD02680D16DE.
+
+
+- Sign the imported key with your private key to mark it as trusted (for information on how to do so, please see the documentation for the public-key encryption software).
Note: If you skip this step and attempt to verify any of our PGP signatures, you will receive an error message stating that the signing key is invalid.
- - Download the digital signature by downloading the PGP Signature of the file you want to verify (on the
-Downloads page).
-
- Verify the downloaded signature (for information on how to do so, please see the documentation for the public-key encryption software).
-
+
+Download the digital signature by downloading the PGP Signature of the file you want to verify (on the Downloads page).
+
+Verify the downloaded signature (for information on how to do so, please see the documentation for the public-key encryption software).
+
Under Linux, these steps can be achieved using the following commands:
-- Check that the fingerprint of the public key is 993B7D7E8E413809828F0F29EB559C7C54DDD393:
+
- Check that the fingerprint of the public key is 5069A233D55A0EEB174A5FC3821ACD02680D16DE:
gpg --with-fingerprint VeraCrypt_PGP_public_key.asc
- If the fingerprint is the expected one, import the public key: gpg --import VeraCrypt_PGP_public_key.asc
-
- Verify the signature of the Linux setup archive (here for version 1.0e):
-gpg --verify veracrypt-1.0e-setup.tar.bz2.sig veracrypt-1.0e-setup.tar.bz2
+
- Verify the signature of the Linux setup archive (here for version 1.23):
+gpg --verify veracrypt-1.23-setup.tar.bz2.sig veracrypt-1.23-setup.tar.bz2