FTDI Community
General Category => Discussion - Drivers => Topic started by: kukdh1 on April 30, 2020, 07:51:58 PM
-
Hi,
I recently installed FTDI VCP driver version 2.4.2 on my macbook. (macOS Catalina 10.15.4)
But the FTDIUSBSerialDriver.kext cannot be loaded with following error:
% sudo kextutil /Library/Extensions/FTDIUSBSerialDriver.kext
Password:
Untrusted kexts are not allowed
Kext with invalid signature (-2147409652) denied: /Library/StagedExtensions/Library/Extensions/E7F4D183-C6C1-4AB7-BCA4-125715B73BA5.kext
Bundle (/Library/Extensions/FTDIUSBSerialDriver.kext) failed to validate, deleting: /Library/StagedExtensions/Library/Extensions/E7F4D183-C6C1-4AB7-BCA4-125715B73BA5.kext
Unable to stage kext (/Library/Extensions/FTDIUSBSerialDriver.kext) to secure location.
With some search on google, I found following blog (written in Japanese).
https://qiita.com/keyakko/items/776bf543c831f22871de (https://qiita.com/keyakko/items/776bf543c831f22871de)
I checked my kext too, and it also shows code signing certificate has been revoked.
% codesign --verify /Library/Extensions/FTDIUSBSerialDriver.kext
/Library/Extensions/FTDIUSBSerialDriver.kext: CSSMERR_TP_CERT_REVOKED
In architecture: x86_64
Interestingly, VCP driver version 2.3 can be loaded successfully.
(But it prints 'resource busy' error when open the tty device, like https://apple.stackexchange.com/questions/377174/ (https://apple.stackexchange.com/questions/377174/))
Any helps with certificate error?
Thanks.
-
Hello,
Apple are moving from what are called Kernel Extentions (.kexts) to what are called Driver Extensions (.dexts) for the implementation of drivers starting in macOS Catalina (10.15). Currently .kexts are still supported in macOS Catalina, however after the beta release they issued an update which stopped our driver from loading. This update required our driver (FTDIUSBSerialDriver.kext) to be re-signed and notarized, we completed this process with an updated Apple Developer ID. Unfortunately when Apple issued our new Developer ID to re-sign and notarize the driver package they did so without the .kext support option enabled (as .kexts are being deprecated it is no longer automatically included). This is why there is a code signature issue with our driver, currently we are waiting on Apple issuing us with the correct Developer ID to be able to sign .kexts for macOS Catalina.
As such our current VCP driver available on the website has a signature issue and wont load. However if the device you are using implements a default FTDI VID/PID combination it should be picked up by the inbuilt AppleUSBFTDI.dext driver and present accordingly in the ‘/dev’ folder on your system in the following form:
/dev/cu.usbserial-xxxxxxxx
/dev/tty.usbserial-xxxxxxxx
Best Regards,
FTDI Community
-
While we wait for Apple, this macOS application has worked well for talking to my FTDI devices:
https://www.decisivetactics.com/products/serial/
-
Hello,
Thanks for the link! This is a very interesting piece of software and may be beneficial for other customers on the form whilst we are resolving the signature issue with our driver.
Best Regards,
FTDI Community
-
Is there any news about Apple's re-signing of the driver?
-
Hello,
Is there any news about Apple's re-signing of the driver?
Yes, actually we have just managed to re-sign and notarize our VCP driver package for macOS 10.15.
We still need to do a couple things before we can release this online, update release notes, etc.
Best Regards,
FTDI Community
-
Hello,
Please see the following post for a resigned version of the driver:
http://www.ftdicommunity.com/index.php?topic=505.0 (http://www.ftdicommunity.com/index.php?topic=505.0)
Best Regards,
FTDI Community