sftcd
sftcd
thanks! fixed that and also added code for ``SSL_CTX_ech_server_flush_keys()`` & pushed PS: late here, tomorrow (also here:-) before I do more on this, great to get all this help -...
I'm happy to do whatever I'm told:-) Meanwhile, I can post to https://github.com/openssl/project/issues/892 whenever I make a new PR for the feature branch. (Probably best to fully process this one...
So... back to the content of this PR: what's our modus-operandi for merging it into the feature branch? I can see two reasonable possibilities: 1) we treat the API description...
> I do not see any major issues with the proposal. There are some nits. Thanks! I've made the obvious changes, pushed those and marked the comments resolved (if you...
Sorry, there's a thing implicit in the above that might be worth calling out now for reviewers. (We can change minds later of course but it nearly came up in...
I made the obvious changes in the most recent commit, will give it a few hours before marking anything as resolved and then await feedback on the non-obvious stuff. I...
I made a branch for the padding stuff mentioned above, i.e. `SSL_CTX_set_block_padding_ex()`` et al. I'll turn that into a PR (aimed at master) tomorrow (or so) but in case someone...
Probably obvious, but the PR above is the padding one discussed here before:-)
commit handles today's comments from @FdaSilvaYY
@mattcaswell - I think you had two main problems with the current APIs, those being making changes to `SSL_CTX` values as ECH keys are updated and use of raw buffers...