Hello, I needed to create an installer for OSX based on the latest CCID driver source (with patches, actually)
Get the "script" and a pre-built installer from here: https://github.com/martinpaljak/osx-ccid-installer After some searching I found a few other packaging efforts (not exhaustive list and in random order): - Gemalto for the Ezio reader: http://support.gemalto.com/fileadmin/user_upload/drivers/GemCCID4121WHQL/macosx/Gemalto_Ezio_driver.pkg - CryptoStick: http://mirror.dotplex.de/gpf/ccid-upgrade-1.4.13.pkg.zip - Realtek: (impossible to link, some crazy fpt-password-javascript-fu going on) http://www.realtek.com.tw/Downloads/downloadsView.aspx?Langid=1&PNid=15&PFid=25&Level=4&Conn=3&DownTypeID=3&GetDown=false#7 What do they do? - Gemalto: targets 10.6+, contains 32/64 bit code; installs an additional driver bundle; only contains Gemalto products in additional Info.plist; built with PackageMaker; no uninstaller - CryptoStick: claims to target 10.5+, actually contains only x86_64 code; contains all devices in version 1.4.13; replaces the stock bundle; built with PackageMaker; no uninstaller - Realtek: replaces the Info.plist of the stock driver with a version that lists 4 new different devices with different USB ID-s but same names, *based on version 1.3.8* (removes working readers from the stock driver which is 1.3.11)... No uninstaller either. What my "better package" does: - Targets OSX 10.8+ (as this is the smallest version that is available as a target on OSX 10.9. Updating to 10.9 which is a free upgrade should anyway be a smart move for anyone) - Includes 32 and 64 bit code (for 10.8) - Installs an additional driver bundle with support for all devices supported by the driver, while disabling the stock driver - Provides an uninstaller - Built with "modern" OSX packaging tools (could be signed, for example) My proposal is to use my skeleton to build an "official" CCID driver installer for OSX, for example by simply replacing the package identifiers to not include openkms (I had to figure out something, as not to replace the stock bundle) and maybe use a bundle identifier "upstream". Thoughts and ideas for improvement? -- Martin +372 515 6495 _______________________________________________ Muscle mailing list [email protected] http://lists.musclecard.com/mailman/listinfo/muscle_lists.musclecard.com
