@Muhammad: do you mind checking this case please? > > Thanks. > > [Footnote] > > * On the public Internet, hopefully nobody is using that protocol > anymore, and instead using either https:// or ssh:// that gives > better integrity assurances. Indeed. I already used MPTCP with ssh:// thanks to 'mptcpize', but that looked more like a workaround. For the client side, if an option can be set to ask to use MPTCP, this info should be passed to what is being used for the HTTPS and SSH connections. @Muhammad: do you plan to look at that too? For HTTP(S), it looks like the libcurl is used. If yes, then `CURLOPT_OPENSOCKETFUNCTION` can be used, see: https://github.com/curl/curl/pull/13278/files For SSH, I'm a bit annoyed: we already asked OpenSSH maintainers to add MPTCP support by sending small patches, but they didn't want it because it is not officially supported by BSD... It is supported on Linux, macOS, Windows with WSL, etc. but that's not enough apparently :-/ (or maybe anyone here is able to convince them to support MPTCP by merging one of the two patches we already sent them? :-D ). For more details and workarounds: https://www.mptcp.dev/faq.html#how-to-enable-mptcp-support-with-openssh Hopefully we will find a way to support MPTCP here in git (and SSH) :) Cheers, Matt -- Sponsored by the NGI0 Core fund.
