sftcd
sftcd
latest push has the `OSSL_ECHSTORE_init()` -> `OSSL_ECHSTORE_new()` change. And I'm probably doing something wrong with the fixup stuff judging by what's presented above - tell me if that should be...
I have a question, it's a bit forward-looking but we can maybe get an answer now. Previously, the internal storage for an ECH key pair, typically loaded in a server...
Nobody biting on the above? :-) That's ok, I can do it in the next PR, which is nearly ready - be nice for me if we can merge this...
ping! can we get this one done - I've the next PR (command line code) nearly ready and it'd be good to have a little bit of momentum:-)
I now have the next PR for the feature branch ready to push, once we get this merged. I don't believe there's much controversy about this one remaining so if...
By my reckoning, it's 10 days since I got a response on this PR.
Thanks! > b) seems ok to me for now. We can always tweak things in the future. On reflection, I think I'll leave it there for the moment if that's...
On 9/6/24 14:28, Tomáš Mráz wrote: > Still `OSSL_ECHSTORE_ENTRY_free` -> `ossl_echstore_entry_free` as > this is a non-public static function. Oops - yes I missed that. Will fix in a bit.
The above commit should fix those (hopefully nearly last:-) issues.
Thanks for all the review. Just to keep us on our toes, I've submitted the next one:-) https://github.com/openssl/openssl/pull/25420