News for hackers. Stuff that matters.
Re:Encrypted Client Hello – the last puzzle piece to privacy by Groxx on Friday September 29, 2023 @11:48PM (#37712616)
I think the remark is because: MITM would allow them to spoof the DNS response entirely, so they can replace it with whatever key they want. Doesn't matter what level of security the key claims at that point, it's attacker-controlled and they can just read whatever you send next.
Re:Encrypted Client Hello – the last puzzle piece to privacy by jacooper on Sunday October 01, 2023 @06:20AM (#37724505)
This wouldn't be possible with dnssec right?
Re:Encrypted Client Hello – the last puzzle piece to privacy by Anunayj on Monday October 02, 2023 @12:46AM (#37734092)
Yes, however it defeats one of the main point of ECH, that is encrypting the SNI. Since the domain is leaked in plaintext DNS.
Re:Encrypted Client Hello – the last puzzle piece to privacy by jacooper on Monday October 02, 2023 @09:04AM (#37737538)
Why? You can just use DNS-over-TLS/HTTPS + dnssec + ECH + TLSv1.3 and then you should have a unblockable website(outside of IP address bans).
Re:Encrypted Client Hello – the last puzzle piece to privacy by Anunayj on Wednesday October 04, 2023 @03:35PM (#37770443)
Ah yes, sorry I thought you meant can't we just use plaintext DNS + DNSSEC.
Re:Encrypted Client Hello – the last puzzle piece to privacy by mwwaters on Wednesday October 04, 2023 @01:34AM (#37761185)
I think the DNS key is only for the handshake to provide the certificate for the actual key. Without a certificate from a CA for second part, all the spoofed DNS key would get is what website they were trying to visit.