9front - general discussion about 9front
 help / color / mirror / Atom feed
From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] [Patch] ndb/dns: DNSKEY and OPT RR types
Date: Fri, 18 Dec 2020 19:18:24 +0100	[thread overview]
Message-ID: <3395DB36FC208BF9DEEEB50FB1C681CD@felloff.net> (raw)
In-Reply-To: <cc1085c8-1d3e-da4d-235e-ba2a78273eaa@mail.posixcafe.org>

> Are your concerns regarding the caching the fact that opt RR's coming from upstream would be cached?

I'm concerned because theres some logic that checks
if the answer section is empty (msg->ar == nil).

The current code *does* some filtering on the answers
to avoid cache poisoning or caching unknown record
types.

But i dont want to bet on it that it will filter
hacks like Topt records.

I'd rather keep the opt records separate. One thing
less to worry about. No accidents.

> I agree, I will fix that in a revised patch if this behavior is still desired.

Thanks.

> If this whole EDNS stuff is undesired I can rip that part of the patch out, 

No, this is good work. But i agree that it would be better
as separate patches.

> but still think the code should catch the Tdnskey RR's, 

Yes, absolutely.

> as having those get caught in the default case was causing some
> parsing issues(or perhaps there is a another nice way of handling
> that, I am not sure)
>
> Thanks,
> Moody

--
cinap

  reply	other threads:[~2020-12-18 18:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-17 23:51 Jacob Moody
2020-12-18 12:25 ` hiro
2020-12-18 15:21 ` cinap_lenrek
2020-12-18 16:05   ` Jacob Moody
2020-12-18 18:18     ` cinap_lenrek [this message]
2020-12-20  7:59       ` Jacob Moody
2020-12-20 22:03         ` cinap_lenrek
2020-12-18 15:30 ` cinap_lenrek

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3395DB36FC208BF9DEEEB50FB1C681CD@felloff.net \
    --to=cinap_lenrek@felloff.net \
    --cc=9front@9front.org \
    /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.
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 NNTP newsgroup(s).