Re: OTC VOTE: EVP init functions and the provider interface
On Tue, Mar 09, 2021 at 10:25:50AM +, Matt Caswell wrote: > topic: EVP init functions take an OSSL_PARAM array to set parameters and > this >should be reflected in the equivalent provider interface. +1 Kurt
Re: OTC VOTE: EVP init functions and the provider interface
This is related to the discussion in PR #14383. It has already been decided to add OSSL_PARAM arrays as an argument to the various EVP "init" functions. During the implementation of that there were differing views about whether this same change should be reflected in the core<->provider interface, i.e. so that the provider init functions would also take OSSL_PARAM arrays. The alternative was to have the libcrypto implementation of the init functions call the provider init and the provider set_params calls separately. Matt On 09/03/2021 17:07, Kurt Roeckx wrote: On Tue, Mar 09, 2021 at 10:25:50AM +, Matt Caswell wrote: topic: EVP init functions take an OSSL_PARAM array to set parameters and this should be reflected in the equivalent provider interface. I need more information than the vote text to be able to vote on this. Kurt
Re: OTC VOTE: EVP init functions and the provider interface
On Tue, Mar 09, 2021 at 10:25:50AM +, Matt Caswell wrote: > topic: EVP init functions take an OSSL_PARAM array to set parameters and > this >should be reflected in the equivalent provider interface. I need more information than the vote text to be able to vote on this. Kurt
OTC VOTE: EVP init functions and the provider interface
topic: EVP init functions take an OSSL_PARAM array to set parameters and this should be reflected in the equivalent provider interface. Proposed by Matt Caswell Public: yes opened: 2021-03-09 closed: 2021-03-09 accepted: yes (for: 5, against: 0, abstained: 2, not voted: 4) Matt [+1] Mark [ ] Pauli [+1] Viktor [ ] Tim[+1] Richard[ 0] Shane [+1] Tomas [+1] Kurt [ ] Matthias [ ] Nicola [+0]
