I am not sure if this problem manifests only if you build OpenSCToken from source and the copy of its executable is present somewhere on your system.
Config
MacOS Mojave 10.14.6, Xcode-11.3.1. Current master of OpenSC and OpenSCToken, OpenSSL_1_1_1-stable (1.0.2 is deprecated - it's time to move off it ;).
Symptoms
Build and install (from the OpenSCToken.dmg) OpenSCTokenApp.app.
Start it, observe it registering the extension. So far so good.
Insert the token, observe (e.g., via ps -ef | fgrep OpenSCToken) that OpenSCToken started.
Remove the token, uninstall OpenSC via /usr/local/bin/opensc-uninstall. Double-check that the /Applications/OpenSCTokenApp.app has been removed - delete it if it wasn't.
Insert the token - observe the extension started again.
Remove the token, kill the running extension, insert the token - observe the extension started again.
Workaround
Determine what file the running extension was invoked from via
ps -ef | fgrep OpenSCToken
then
Remove that file via
pluginkit -r /full/path/to/that/file
Now the extension is gone.
Proposed Solution
I don't know - maybe write a real uninstaller that would locate and remove/unregister this extension?
I am not sure if this problem manifests only if you build
OpenSCToken
from source and the copy of its executable is present somewhere on your system.Config
MacOS Mojave 10.14.6, Xcode-11.3.1. Current master of OpenSC and OpenSCToken, OpenSSL_1_1_1-stable (1.0.2 is deprecated - it's time to move off it ;).
Symptoms
OpenSCToken.dmg
)OpenSCTokenApp.app
.ps -ef | fgrep OpenSCToken
) that OpenSCToken started./usr/local/bin/opensc-uninstall
. Double-check that the/Applications/OpenSCTokenApp.app
has been removed - delete it if it wasn't.Workaround
then
Now the extension is gone.
Proposed Solution
I don't know - maybe write a real uninstaller that would locate and remove/unregister this extension?