From: Jules Maselbas <jmaselbas@kalray.eu>
To: barebox@lists.infradead.org
Subject: Re: [PATCH] net: dns: Generate and verify transaction ID
Date: Fri, 6 May 2022 17:04:05 +0200 [thread overview]
Message-ID: <20220506150405.GF10082@tellis.lin.mbt.kalray.eu> (raw)
In-Reply-To: <20220505100805.5144-1-jmaselbas@kalray.eu>
Hi,
I would like some feedback on how to select a dns_req_id.
Although ths is likely not very critical to barebox, I think using both
dns_timer_start plus random32 is a bit overkill. Maybe simply using
random is sufficient.
On Thu, May 05, 2022 at 12:08:05PM +0200, Jules Maselbas wrote:
> The transaction ID wasn't verified on received DNS responses, plus the
> ID needs to be difficult to predict in order to avoid MitM (man in the
> middle) being able to easily forge responses.
>
> Signed-off-by: Jules Maselbas <jmaselbas@kalray.eu>
> ---
> net/dns.c | 10 +++++++++-
> 1 file changed, 9 insertions(+), 1 deletion(-)
>
> diff --git a/net/dns.c b/net/dns.c
> index 78588b96f..9ad316e33 100644
> --- a/net/dns.c
> +++ b/net/dns.c
> @@ -58,6 +58,7 @@ struct header {
>
> static struct net_connection *dns_con;
> static uint64_t dns_timer_start;
> +static uin32_t dns_req_id;
> static int dns_state;
> static IPaddr_t dns_ip;
>
> @@ -70,9 +71,12 @@ static int dns_send(const char *name)
> unsigned char *p, *s, *fullname, *dotptr;
> const unsigned char *domain;
>
> + /* generate a random transaction id */
> + dns_req_id = dns_timer_start + random32();
I am wondering if using only one of dns_timer_start or randome32 is
sufficient on its own. For the record musl uses clock_gettime without
random at all.
> /* Prepare DNS packet header */
> header = (struct header *)packet;
> - header->tid = 1;
> + header->tid = htons(dns_req_id);
> header->flags = htons(0x100); /* standard query */
> header->nqueries = htons(1); /* Just one query */
> header->nanswers = 0;
> @@ -127,6 +131,10 @@ static void dns_recv(struct header *header, unsigned len)
>
> pr_debug("%s\n", __func__);
>
> + /* Only accept responses with the expected request id */
> + if (ntohs(header->id) != dns_req_id)
> + return;
> +
> /* We sent 1 query. We want to see more that 1 answer. */
> if (ntohs(header->nqueries) != 1)
> return;
> --
> 2.17.1
>
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2022-05-06 15:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 10:08 Jules Maselbas
2022-05-06 14:58 ` [PATCH] fixup! " Jules Maselbas
2022-05-06 14:59 ` Jules Maselbas
2022-05-06 15:16 ` Jules Maselbas
2022-05-06 15:04 ` Jules Maselbas [this message]
2022-05-09 7:17 ` [PATCH] " Sascha Hauer
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=20220506150405.GF10082@tellis.lin.mbt.kalray.eu \
--to=jmaselbas@kalray.eu \
--cc=barebox@lists.infradead.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