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

EVP_*Update: ensure that input NULL with length 0 isn't passed #8676

Closed
wants to merge 2 commits into from
Closed

EVP_*Update: ensure that input NULL with length 0 isn't passed #8676

wants to merge 2 commits into from

Commits on Apr 4, 2019

  1. EVP_*Update: ensure that input NULL with length 0 isn't passed 

    Even with custome ciphers, the combination in == NULL && inl == 0
should not be passed down to the backend cipher function.  The reason
is that these are the values passed by EVP_*Final, and some of the
backend cipher functions do check for these to see if a "final" call
is made.

Fixes openssl#8675
    @levitte
    levitte committed Apr 4, 2019
    Configuration menu
    Copy the full SHA
    c9d4e49 View commit details
    Browse the repository at this point in the history

Commits on Apr 5, 2019

  1. fixup! EVP_*Update: ensure that input NULL with length 0 isn't passed

    @levitte
    levitte committed Apr 5, 2019
    Configuration menu
    Copy the full SHA
    412b31b View commit details
    Browse the repository at this point in the history