From fb38269c89e0fadf51e6912d5a9e017d02833b34 Mon Sep 17 00:00:00 2001 From: Mounir IDRASSI Date: Wed, 7 Dec 2016 00:27:28 +0100 Subject: Readme: correct instructions about code signing under Mac OSX --- src/Readme.txt | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'src/Readme.txt') diff --git a/src/Readme.txt b/src/Readme.txt index 5280ac30..053a6ad1 100644 --- a/src/Readme.txt +++ b/src/Readme.txt @@ -200,8 +200,9 @@ VeraCrypt sources (i.e. if "src" path is "/Users/joe/Projects/VeraCrypt/src" then wxWidgets should be at "/Users/joe/Projects/wxWidgets-3.0.2") The build process uses Code Signing certificates whose ID is specified in -src/Main/Main.make (lines 167 & 169). You'll have to modify these lines to put -the ID of your Code Signing certificates or comment them if you don't have one. +src/Main/Main.make (look for lines containing "Developer ID Application" and +"Developer ID Installer"). You'll have to modify these lines to put the ID of +your Code Signing certificates or comment them if you don't have one. Because of incompatibility issues with OSXFUSE, the SDK 10.9 generates a VeraCrypt binary that has issues communicating with the OSXFUSE kernel extension. -- cgit v1.2.3