Re: xdigest at ASF
Timofei Zhakov <[email protected]>
| Newsgroups | gmane.comp.apache.incubator.general |
|---|---|
| Message-ID | <CAPD1kXRhuh6Pe_j-AttHqQ1eUCF=Fkbsv_HJsJ+-eTufGZfJnw@mail.gmail.com> |
On Mon, Mar 23, 2026 at 1:22 PM Salz, Rich <[email protected]> wrote: > > I did a diff on a couple of source files. Can you describe what you did beyond renaming some functions and local variables, compared to the original sources? Oh, and adding your own copyright statement :) > Codewise - not so much. OpenSSL can do pretty much everything one would ask it to. Often, people need something rather simple. In the context of checksums, one would prefer not loading all the code that they wouldn't actually use. The low-level API is deprecated in OpenSSL since 3.0. xdigest prioritises simplicity and exposes it instead. There are several cases where the EVP interface is not suitable to use because it performs an indirect vtable call which makes the edge cases twice as slow [1]. This is not really that big of a deal with larger sizes, but is still a problem. If something looks similar, it's not exactly true. The same thing works the other way as well. Let's say AI generated code is not original although looking differently. OpenSSL has different goals which could not meet everyone's needs. This is also why deprecation does make sense even though it's not what *some* would love. [1] https://github.com/openssl/openssl/issues/19612 -- Timofei Zhakov