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

Crypto pre 1.1-compat #229

Merged
merged 3 commits into from Feb 26, 2017
Merged

Crypto pre 1.1-compat #229

merged 3 commits into from Feb 26, 2017

Commits on Feb 26, 2017

  1. Always warn upon failure in crypto_keys_init() 

    It's rather unlikely to have a problem importing the server root, but if it
happens (*cough* OpenSSL 1.1), let's be explicit about it.
    @gperciva
    gperciva committed Feb 26, 2017
    Copy the full SHA
    6d03aa7 View commit details
    Browse the repository at this point in the history

  2. Add (const) to export_BN(BIGNUM *, ...) 

    This will avoid some warnings when we add OpenSSL 1.1 compatibility.
    @gperciva
    gperciva committed Feb 26, 2017
    Copy the full SHA
    91311d2 View commit details
    Browse the repository at this point in the history

  3. crypto_keys_subr.c: use BIGNUM as an intermediate step 

    Separating the interaction between
    uint8_t * buf
and
    RSA ** key
is a necessary step towards OpenSSL 1.1 compatibility.
    @gperciva
    gperciva committed Feb 26, 2017
    Copy the full SHA
    f76e1c2 View commit details
    Browse the repository at this point in the history