Apologies for my mistake earlier: I sent this from an address which
isn't allowed to send to this list.
Forwarded message:
From: Niall O'Reilly
To: curl-library@cool.haxx.se
Subject: ESNI initiative
Date: Wed, 29 May 2019 15:03:21 +0100
Hello.
I'm not sure whether posting to this list is the
Hi.
On 31 May 2019, at 9:52, Niall O'Reilly wrote:
More will follow in due course.
So far, we have the network side, between **curl** client
and an ESNI-aware server, working. Instructions for trying
this out are here:
[https://github.com/niallor/curl/blob/master/ESNI-README.md](https://gith
PR on the way to allow full range [0..65535] for DNS QTYPE in doh_encode().
/Niall
---
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.haxx.se/mail/etiquette.html
Hi.
Some messages which I sent to this list earlier in the week
didn't arrive. Both Daniel Stenberg and I are puzzled.
I'm trying to identify differences at source between these
messages and one which arrived as expected yesterday. As I
find things that I can adjust, I'm doing this and re-sendin
Hi.
After too many attempts to follow up Daniel's (off-list)
reaction to my earlier mail, here's a quick summary of
how I think the questions raised can most simply be
resolved.
On 11 Sep 2019, at 16:33, niall.oreilly+li...@ucd.ie wrote:
> * Extend `struct dohdata` or use a different
> struc
On 12 Nov 2019, at 18:51, Daniel Stenberg wrote:
Ah! We should probably A) fix that and refuse such names with zero
labels and B) update the used host names in the test...
I think I’ve covered item A as a side effect while working on prefix
support.
https://github.com/niallor/curl/commit/
On 13 Nov 2019, at 9:36, Daniel Stenberg wrote:
It might be worth splitting out and fixing in a separate pull-request,
sure!
Hmm. I’m not sure what you mean here. If you mean a PR which covers
RFC1035
compliance but not prefix support, I would find myself doing almost the
same
work twice.
On 13 Nov 2019, at 9:36, Daniel Stenberg wrote:
I think it primarily needs a valid input name (no zero length labels)
that is longer than the given output buffer, as that test tries to
verify that the boundary checks for that are fine and causes no
overwrite.
There’s a notational ambiguity
On 13 Nov 2019, at 13:33, Daniel Stenberg wrote:
Why twice? If it is a generic fix to DoH in curl, that could be lifted
out from your other work and merged indepdendently. Once.
That’s pretty-well ready, including prefix support, which I’m not
minded to cut out,
only to have to add it back i
On 13 Nov 2019, at 13:41, Daniel Stenberg wrote:
Is there a reason the DoH code can't just use with exactly the host
name it gets passed, using a trailing dot or not?
That’s pretty-well the answer I was looking for.
I’m not aware of a compelling reason that it shouldn’t be tolerant,
just as
On 13 Nov 2019, at 9:36, Daniel Stenberg wrote:
It might be worth splitting out and fixing in a separate pull-request,
sure!
OK, done.
/Niall
---
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://cu
Hello.
Some data is published in the DNS at a child node of the node
which corresponds to the hostname, as documented in
[RFC8552](https://datatracker.ietf.org/doc/rfc8552/).
In particular, current (experimental) ESNI deployment uses
TXT records and child-prefix "_esni".
I've been thinking about
On 20 Nov 2019, at 14:10, Daniel Stenberg wrote:
SVCB is what the current ESNI draft wants, right? (btw there's now a
poll going for what to name those new records over at:
https://lists.w3.org/Archives/Public/ietf-http-wg/2019OctDec/0117.html
)
IIUC, SVCB will be published at a prefix nod
Hello.
A host’s IPv4 or IPv6 address is needed in order to establish a connection.
If DOH is enabled, the function *Curl_doh()* is used to retrieve these
from the DNS. *Curl_doh()* has two dedicated “probe slots” for holding DOH
query state independently for each of the DNS QTYPEs, A and .
In
I’m not sure whether this is worth opening an issue.
If the target hostname is an alias, the DNS returns a CNAME in the
answer to each of the queries which Curl_doh() launches. In the
standard libcurl build, there are two of these, with QTYPE of A
and respectively.
During decoding, these are
On 27 Nov 2019, at 10:03, Daniel Gustafsson via curl-library wrote:
> I'm not sure if we need to make it more explicit, but if we make funding
> students in some way different then maybe we should add that a proof of
> enrollment is required?
Maybe RIPE's RACI programme could be a model.
https://
On 19 Dec 2019, at 9:27, Daniel Stenberg via curl-library wrote:
> Thoughts?
All good, especially giving the seed some, but limited, persistence.
/Niall
---
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: ht
On 29 Jan 2020, at 7:51, Daniel Stenberg via curl-library wrote:
2. A simpler method would possibly be to use a single c-ares "channel"
for a whole multi handle, as then you would just make sure to keep the
multi handle around when doing multiple transfers and c-ares wouldn't
have to re-init.
On 12 Jun 2020, at 10:41, Daniel Stenberg via curl-library wrote:
"The project MUST clearly identify small tasks that can be performed
by new
or casual contributors"
... as this then seems to be *the only* remaining critera for curl
reaching gold level CII Best Practices, I'm tempted to do
On 13 Jun 2020, at 21:56, Daniel Stenberg via curl-library wrote:
> As of just a few moments ago we fulfill the gold level best practices!
Grattis!
---
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https:/
Feedback welcome:
https://github.com/niallor/curl/commit/873a5053c830fe68fa278e1b65cf4a7a0971ecce
Thanks in anticipation
Niall
---
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.haxx.se/mail/e
Helt sent, men grattis!
On 18 Sep 2020, at 21:41, Daniel Stenberg via curl-library wrote:
It's a meaningless number, but I just reached 15,000 commits in the
curl master branch today and I figured it could be fun to celebrate so
I blogged a little about it:
---
Hi.
Work I was involved in to add ESNI support to libcurl
was suspended quite a number of months ago as the
IETF TLS WG decided on, and since specified, a different
approach. After dealing with some other distractions,
I expect to pick this up again soonish, but most likely
not before the new ye
Hi.
Now that IETF work on ECH and service binding seems to be converging,
I’ve started looking at how to refactor the experimental ESNI code
from nearly a year ago.
I’ld like to start by to updating docs/ECH.md. Please let me know
whether https://github.com/niallor/curl/blob/ECH-reset/docs/ECH.md
Hello.
I would like to let people know of a proof-of-concept
implementation of ECH in curl and libcurl. This uses
OpenSSL as back-end and interoperates with Cloudflare’s
demonstration server.
For more information, please see
https://github.com/niallor/curl/blob/ECH-WIP/docs/ECH.md
Best regards.
FWIW, and with the caveat that I am not a **real** DNS expert.
On 10 May 2021, at 14:52, Daniel Stenberg via curl-library wrote:
I've created PR #7039 that makes "localhost" resolve to 127.0.0.1 and
::1 without using the resolver [1].
The point of this is to make sure localhost is the local h
26 matches
Mail list logo
