Live data from Hacker News

Chromium's Impact on Root DNS Traffic

blog.apnic.net

111–120 of 221 posts

Re: Chromium's Impact on Root DNS Traffic

#111
post #26

I don't get this feature. And I really hate that it's present in pretty much every browser these days. If I want to type an URL, I'll use the address bar. If I want to search, I'll use the search bar. Different bars with different keyboard shortcuts and different purposes. Why do so many browsers merge these two? Screens are insanely wide these days, so screen real estate can't be the reason. Are we trying to trick u…

On FF it’s Ctrl+k for searching (by prepending `? `) and Ctrl+l for addresses (if it can be parsed as an address). I almost never just click into the bar, so that works fine for me.

This works in Chrome too

Re: Chromium's Impact on Root DNS Traffic

#112

The worst thing is, this will not even detect a well written NXDOMAIN interceptor that only hijacks requests to valid top level domains. It's about time for DNSSEC to be available on all TLDs and for browsers to nag if it is broken.

> hijacks requests to valid top level domains

I believe the purpose of this feature is not about detecting hijack requests to valid top level domains. In other words, a well written NXDOMAIN interceptor would not cause a harm to their intended audience, so they didn't bother trying to detect it.

It's about detecting that a "eng-wiki A aa.bb.cc.dd" record it just received from the user's DNS server is actually intended to be eng-wiki served from corp network instead of a stupid ISP page.

Re: Chromium's Impact on Root DNS Traffic

#113

Earlier quoted context omitted.

I don't understand why browser vendors should be involved My browser should ask my OS to resolve DNS It's my OS's responsibility to do that - maybe sending a request to a remote server, maybe running it's own resolved, maybe using DoT, DoH, DNSSec or not What business should it be of browser vendors?

The OS resolves DNS names to IP addresses... Except an IP address isn't a security identifier of any kind, so there is no benefit to it not being spoofed. The relation to browser vendors is that DNSSEC allows DNS to verify/validate certificates for TLS connections, which can be used by web browsers (and other applications, but web browsers would be the main users).

Shouldn't it be up to my OS to do that validation though, not the browser? After all when I ssh to my.server.com I want the same guarentee as when I https to it.

Re: Chromium's Impact on Root DNS Traffic

#114
post #110
post #106

Earlier quoted context omitted.

This post contains a bunch of information about the question, but it doesn't seem to actually address the question. The question is: does Chromium send the first word I type to my ISP? The answer appears to be: yes.

> the first word No. The answer appears to be yes if you said "the only word", though.

[deleted]

Re: Chromium's Impact on Root DNS Traffic

#115
post #24

Earlier quoted context omitted.

And for those who don't understand why this is a bad thing, I will present my own use case. I run pi-hole at home and frequently work from there for another company. That company has provided me with a laptop that uses Cisco's DNS "Umbrella", which is some sort of security feature: https://docs.umbrella.com/deployment-umbrella/docs/point-you... Because my company laptop doesn't pay attention to the DNS servers recomm…

> THIS IS ALWAYS A BAD IDEA because once any account is compromised, ALL OTHER ACCOUNTS with locally stored keys ARE ALSO COMPROMISED. This is not universally true. If you generate separate private keys for each server-client pair, compromising one private key will limit the damage to just the one server.

That is just not true. It may be the case if the key itself is compromised, but consider that you may have many different accounts scattered on different servers. Once one of them is compromised, the attacker now has access to every other account because they are all chained together.

Re: Chromium's Impact on Root DNS Traffic

#116

Earlier quoted context omitted.

Ctrl+K for Windows users looking for a shortcut key.

That works on multiple platforms! I'm able to do that on Arch.

In the good old times, ctrl-l went to the location bar and ctrl-k went to the search bar. After they merged, ctrl-k just prepends the question mark. But... as an old shortcut, pretty much everything supports it.

Re: Chromium's Impact on Root DNS Traffic

#117
post #24

Earlier quoted context omitted.

> THIS IS ALWAYS A BAD IDEA because once any account is compromised, ALL OTHER ACCOUNTS with locally stored keys ARE ALSO COMPROMISED. This is not universally true. If you generate separate private keys for each server-client pair, compromising one private key will limit the damage to just the one server.

That is just not true. It may be the case if the key itself is compromised, but consider that you may have many different accounts scattered on different servers. Once one of them is compromised, the attacker now has access to every other account because they are all chained together.

Can you describe the attack scenario you're imagining in a bit more detail? Because that doesn't sound possible to me.

Re: Chromium's Impact on Root DNS Traffic

#118

Earlier quoted context omitted.

You can prefix your searches in the omnibox with “?” and they won’t be treated as possible short local network names

Ctrl+K for Windows users looking for a shortcut key.

Isn’t “?” and ctrl-k the same number of keystrokes?

Re: Chromium's Impact on Root DNS Traffic

#119
post #110
post #106

Earlier quoted context omitted.

This post contains a bunch of information about the question, but it doesn't seem to actually address the question. The question is: does Chromium send the first word I type to my ISP? The answer appears to be: yes.

> the first word No. The answer appears to be yes if you said "the only word", though.

...which the first word would be, as you typed it?
Post reply on HN