From: Jeff King <peff@peff.net>
To: Nicolas Morey-Chaisemartin <NMoreyChaisemartin@suse.de>
Cc: Nicolas Morey-Chaisemartin <nicolas@morey-chaisemartin.com>,
git@vger.kernel.org
Subject: Re: [RFC 0/3] imap-send curl tunnelling support
Date: Wed, 23 Aug 2017 17:43:49 -0400 [thread overview]
Message-ID: <20170823214349.k4ayl2urqepch7p4@sigill.intra.peff.net> (raw)
In-Reply-To: <0beb0a6c-acb3-ae24-5c52-95747f74c07f@suse.de>
On Mon, Aug 21, 2017 at 09:34:19AM +0200, Nicolas Morey-Chaisemartin wrote:
> >> It appears curl do not support the PREAUTH tag.
> > Too bad. IMHO preauth is the main reason to use a tunnel in the first
> > place.
>
> It shouldn't be too hard to add support for this in curl.
> If it's the main usecase, it'll simply means the curl tunnelling
> should be disabled by default for older curl (in this case, meaning
> every version until it gets supported) versions.
Yes, I agree. I was hoping when we started this discussion that we were
more ready to switch to curl-by-default. But sadly, that isn't close to
being the case. But hopefully we can at least end up with logic that
lets us use it in the easy cases (no tunneling) and falls back in the
harder ones.
-Peff
next prev parent reply other threads:[~2017-08-23 21:43 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-09 14:43 [RFC 0/3] imap-send curl tunnelling support Nicolas Morey-Chaisemartin
2017-08-09 14:46 ` [RFC 1/3] imap-send: move tunnel setup to its own function Nicolas Morey-Chaisemartin
2017-08-09 14:46 ` [RFC 2/3] imap-send: use a socketpair instead of pipe to communicate with the tunnel Nicolas Morey-Chaisemartin
2017-08-09 14:46 ` [RFC 3/3] imap_send: add support for curl over tunnel Nicolas Morey-Chaisemartin
2017-08-15 17:49 ` [RFC 0/3] imap-send curl tunnelling support Nicolas Morey-Chaisemartin
2017-08-15 18:18 ` Stefan Beller
2017-08-16 12:30 ` Johannes Schindelin
2017-08-21 7:27 ` Nicolas Morey-Chaisemartin
2017-08-22 17:10 ` Johannes Sixt
2017-08-22 18:22 ` Nicolas Morey-Chaisemartin
2017-08-23 22:35 ` Johannes Schindelin
2017-08-16 8:34 ` Jeff King
2017-08-21 7:34 ` Nicolas Morey-Chaisemartin
2017-08-23 21:43 ` Jeff King [this message]
2017-08-24 8:00 ` Nicolas Morey-Chaisemartin
2017-08-24 13:53 ` Jeff King
2017-08-24 14:02 ` Daniel Stenberg
2017-08-24 14:30 ` Jeff King
2017-08-24 21:22 ` Daniel Stenberg
2017-08-24 14:15 ` Nicolas Morey-Chaisemartin
2017-08-24 14:28 ` Jeff King
[not found] ` <7ee8331d-e154-7539-e000-4087406f39fa@suse.de>
2017-08-16 8:39 ` Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170823214349.k4ayl2urqepch7p4@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=NMoreyChaisemartin@suse.de \
--cc=git@vger.kernel.org \
--cc=nicolas@morey-chaisemartin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).