Hello wyday,
We need to have signed libTurboActivate.dylib - version 3.4.6 was signed correctly.
otool -L libTurboActivate.dyliblibTurboActivate.dylib: @rpath/libTurboActivate.dylib (compatibility version 1.0.0, current version 4.0.5) /usr/lib/libcurl.4.dylib (compatibility version 5.0.0, current version 5.0.0) /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 476.19.0) /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation (compatibility version 300.0.0, current version 677.26.0) /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration (compatibility version 1.0.0, current version 212.2.0) /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices (compatibility version 1.0.0, current version 32.0.0) /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit (compatibility version 1.0.0, current version 275.0.0) /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 7.4.0) /usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 111.1.4) /usr/lib/libobjc.A.dylib (compatibility version 1.0.0, current version 227.0.0)DevelopYosemite:TurboActivate-Mac-2 klokantech$ codesign -dvvv libTurboActivate.dyliblibTurboActivate.dylib: code object is not signed at allDevelopYosemite:TurboActivate-Mac-2 klokantech$ spctl -a -v libTurboActivate.dyliblibTurboActivate.dylib: rejectedsource=no usable signature
Would it be possible to sign it again and publish it now?
Hey Martin,
We do plan to release code-signed macOS libraries and executables. We're working with our EV Certificate provider to get the hardware-dongle working in Mac OS X (it works perfect in Windows, but it appears the drivers for Mac OS X are much buggier).
In the meantime sign them with your certificate.
Hey Martin,
The TurboFloatServer for macOS / Mac OS X is now signed with our code signing certificate.
