8c94662e96
The PKCS#11 Usage Guide, at least up to v2.40, says that calling C_Initialize() in the child after fork is "considered to be good Cryptoki programming practice, since it can prevent the existence of dangling duplicate resources that were created at the time of the fork() call." (It neglects to mention that doing so in the child of a multi-threaded process is a clear violation of POSIX, mind you. Not to mention being utterly pointless if all you're going to do in the child is exec something else anyway.) Regardless of the sagacity of this recommendation, we need to cope when it happens. Historically, we've been quite bad at that. Let's add a test to pkcs11-tool in the hope it'll help... Fixes #464 |
||
---|---|---|
MacOSX | ||
doc | ||
etc | ||
m4 | ||
packaging/debian.templates | ||
solaris | ||
src | ||
win32 | ||
.gitignore | ||
.travis.yml | ||
CONTRIBUTING.md | ||
COPYING | ||
Makefile.am | ||
Makefile.mak | ||
NEWS | ||
README | ||
README.md | ||
bootstrap | ||
bootstrap.ci | ||
configure.ac | ||
version.m4 |
README.md
OpenSC documentation wiki is available online at https://github.com/OpenSC/OpenSC/wiki
Please take a look at the documentation before trying to use OpenSC.