On 16/09/2020 15:23, Sage Gerard wrote: > I'm okay with using EVP_DigestSign, but both that and online materials > presume EVP_DigestSignUpdate's availability, and the source code does > not seem to have a directive to exclude the signature or implementation > at first glance. What can explain the symbol's absense? Its a macro: # define EVP_DigestSignUpdate(a,b,c) EVP_DigestUpdate(a,b,c) So, the symbol in libcrypto.so is called EVP_DigestUpdate. Note that this isn't the case in OpenSSL 3.0. It is a full symbol in its own right there. Matt