Frank Morgner

I don't really see a problem in the low level function... Could you run a test with OpenSC's debug output enabled?

Do you have some "official" middleware?

how are you using your certificates to, for example, authenticate in a web browser, to open an VPN or to login to your computer?

with access to the source code, it's fairly easy to get the missing pieces for OpenSC. Unfortunately, we don't have a lot of information for writing new card drivers. please...

This is the initial configuration for compiling: ``` 2022-01-17T18:21:01.5072200Z Host: x86_64-apple-darwin19.6.0 2022-01-17T18:21:01.5072650Z Compiler: gcc 2022-01-17T18:21:01.5073070Z Preprocessor flags: 2022-01-17T18:21:01.5074110Z Compiler flags: -Wall -Wextra -Wno-unused-parameter -Werror -Wstrict-aliasing=2 -isysroot /Applications/Xcode_12.4.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.1.sdk -arch x86_64 -arch...

we don't use fat binaries anymore. we're just building 64 bits.

The installer of 98f6d77 [was 40 MB](https://github.com/OpenSC/OpenSC/actions/runs/1167034444), the installer of 703183e [was 133 MB](https://github.com/OpenSC/OpenSC/actions/runs/1181550216). As far as I can see, the only difference on macOS is the code signing... https://github.com/OpenSC/OpenSC/compare/98f6d77...703183e

A local build with code signing enabled also yields such a big installer, because only with this the CTK driver is built which contains an other copy of opensc linked...

``` bloaty ./cardos-tool /Library/OpenSC/bin FILE SIZE VM SIZE -------------- -------------- 62.3% 2.73Mi 65.2% 1.53Mi __TEXT,__text 6.7% 299Ki 5.8% 139Ki __TEXT,__const 5.5% 247Ki 5.3% 126Ki String Table 4.6% 204Ki 4.5% 107Ki...

One difference between cardos-tool and openpgp-tool is that the former is statically linked to OpenSSL while the latter does not. Both tools, are using libopensc, which is also statically linked...