[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wgKEbppgxafYchqQ6X_VFa0d_vdtVmfqGQC6kQ+Hg9cAw@mail.gmail.com>
Date: Wed, 4 May 2022 14:24:29 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Stafford Horne <shorne@...il.com>
Cc: "Jason A. Donenfeld" <Jason@...c4.com>,
Andy Shevchenko <andriy.shevchenko@...el.com>,
Mikulas Patocka <mpatocka@...hat.com>,
Andy Shevchenko <andy@...nel.org>,
device-mapper development <dm-devel@...hat.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Crypto Mailing List <linux-crypto@...r.kernel.org>,
Herbert Xu <herbert@...dor.apana.org.au>,
"David S. Miller" <davem@...emloft.net>,
Mike Snitzer <msnitzer@...hat.com>,
Mimi Zohar <zohar@...ux.ibm.com>,
Milan Broz <gmazyland@...il.com>
Subject: Re: [PATCH v2] hex2bin: make the function hex_to_bin constant-time
On Wed, May 4, 2022 at 1:26 PM Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
>
> Could be anywhere. Xfinity, Nest WiFi, or the cable router. They all
> are doing their own dns thing.
>
> Probably my cable box, since it's likely the oldest thing in the chain.
No, it seems to be my Nest WiFi router. I told it to use google DNS to
avoid Xfinity or the cable box, and it still shows the same behavior.
Not that I care much, since I consider those IDN names to be dangerous
anyway, but I think it would have been less sad if it had been some
old cable modem.
Linus
Powered by blists - more mailing lists