sftcd

On 29/09/2023 17:13, Daniel Stenberg wrote: > While you were working on this, we changed how these references should be formatted and they are now verified to follow this format...

This is out dated, see further down for latest. So the latest commit https://github.com/curl/curl/pull/11922/commits/fb2b2cd286ff7d80837659feea50a03e92378e20 re-does the command line args as follows: - ``--ech `` - the ``config`` value can be...

Given there's a preference for fewer options, the [latest push](https://github.com/curl/curl/pull/11922/commits/73358484a57ead5064cc5349681c33178c097595) reduces the command line to one option only as in: - ``--ech `` - the ``config`` value can be one...

> I hope it's not too late, but I made this patch for CMake earlier: > > Short of an ECH-enabled TLS library, it's only lightly tested. Oh thanks, I'll...

> I hope it's not too late, but I made this patch for CMake earlier: Thanks again @vszakats. Since yours was cleaner than mine, I've now gone more or less...

On 18/10/2023 16:47, 南宫雪珊 wrote: > What is the meaning of `--ech false`, why not delete `--ech`? In my local setup I have "ech=TRUE" in ``$HOME/.curlrc`` so this provides a...

> https://github.com/curl/curl/blob/9742dba5234ae8a717468856382a40991a18df74/docs/cmdline-opts/ech.d#L10 > To be honest, I'm not sure what "Multi: single" means, I probably just copied from some other ``.d`` file. > What if i want `hard` + base64...

Thanks for the comments btw - I take it from those that, at minimum, more text is needed in ``ech.d`` to clarify the above. I'll add something in a while.

> A bunch of comments of mine. Most of them are plain _opinions_ so do take them as proposals, not strict requirements. Working through those with a view to accepting...

A note for the curious: I've just rebased with the main branch and will be fixing things next few days so don't worry if the inevitable CI check fails occur...