sftcd
sftcd
> I've not reviewed this in detail but I have some initial comments on the overall structure and approach to this solution. > Thanks! > Firstly we need to give...
> I would add that this is a substantial new feature so it would need to be discussed with OTC/OMC as to when/if this fits into our release plan. I'm...
> As an aside, if HPKE can be made to work within the bounds of our existing operations and their associated EVP APIs then it should be possible to write...
> > I think it makes sense to include HPKE a a feature for a crypto library anyway. > > Sure. I'm not suggesting we shouldn't look to include it...
Thanks! Will fix those nits. On this one: On 01/12/2021 18:22, FdaSilvaYY wrote: > strange: `return(__LINE__);` do not return `-1` That's just an old debugging trick I find makes it...
On 01/12/2021 22:12, Richard Levitte wrote: > @levitte commented on this pull request. > > > >> @@ -0,0 +1,377 @@ > +/* > + * Copyright 2019-2021 Stephen Farrell....
Hi Matt, > Firstly we need to give some thought as to how HPKE maps to the existing high level EVP APIs that we have. A while back in the...
> The problem with the SealInit/OpenInit APIs is that they are merely thin wrappers around other EVP APIs. There is no provider based equivalent of these > Not sure that's...
I'm playing about with different possible high level API designs and have a question: ``OSSL_PARAM`` is used for various APIs with a ``_set_params`` function. For HPKE one might initially think...
Ah - Ben got there before me, good:-) I agree with all he wrote.