Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | p11-kit: Use pthread_atfork() in a safe manner | Stef Walter | 2014-10-03 | 1 | -11/+9 |
| | | | | | | | | | | | | | Instead of trying to perform actions in pthread_atfork() which are not async-signal-safe, just increment a counter so we can later tell if the process has forked. Note this does not make it safe to mix threads and forking without immediately execing. This is a far broader problem that p11-kit, however we now do the right thing when fork+exec is used from a thread. https://bugs.freedesktop.org/show_bug.cgi?id=84567 | ||||
* | p11-kit: Fix various noise/issues highlighted by clang | Stef Walter | 2014-08-11 | 1 | -2/+2 |
| | |||||
* | rpc: Implement PKCS#11 messages/client/server code | Stef Walter | 2014-07-08 | 1 | -0/+2092 |
* This enables passing around bytes which represent PKCS#11 RPC calls. * Caller is responsible for connecting/disconnecting and so on. * Client side caller gets a mixin from p11_rpc_client_init() to call into, which generates callbacks with byte arrays to be transported. * Server side calls p11_rpc_server_handle() with a CK_FUNCTION_LIST_PTR on which relevant methods get called. * Doesn't yet implement the actual daemon or clients etc... https://bugs.freedesktop.org/show_bug.cgi?id=54105 |