Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Improve usefullness of remoting #18

Closed
wants to merge 4 commits into from
Closed

Improve usefullness of remoting #18

wants to merge 4 commits into from

Commits on Dec 8, 2016

  1. common: use recursive pthread mutex for library lock 

    This allows us to do nested locking within one thread avoiding a lockup
when remoting the p11-kit-proxy.so module.

The Windows NT mutex is aready recursive by default.
    @lkundrak
    lkundrak committed Dec 8, 2016
    Configuration menu
    Copy the full SHA
    90668f1 View commit details
    Browse the repository at this point in the history

  2. p11-kit: relax sanity checking when remoting 

    This allows us to remote the proxy module. No reason that wouldn't be
allowed.
    @lkundrak
    lkundrak committed Dec 8, 2016
    Configuration menu
    Copy the full SHA
    7cb2503 View commit details
    Browse the repository at this point in the history

  3. p11-kit: add a routine to allow setting up module remoting

    @lkundrak
    lkundrak committed Dec 8, 2016
    Configuration menu
    Copy the full SHA
    e10e473 View commit details
    Browse the repository at this point in the history

  4. p11-kit-remote-proxy: add a PKCS#11 module for remoting 

    This allows making a PKCS#11-enabled application that doesn't link to
p11-kit to use a remote module easily.

The remote is set up using P11_REMOTE environment variable, for a lack
of a better mechanism to pass data to the PKCS#11 module.
    @lkundrak
    lkundrak committed Dec 8, 2016
    Configuration menu
    Copy the full SHA
    0a01c7f View commit details
    Browse the repository at this point in the history