Live data from Hacker News

DNS over HTTPS

github.com

81–90 of 195 posts

Re: DNS over HTTPS

#81

Earlier quoted context omitted.

> After resolving the IP address over secure connection HTTPS still sends the host name unencrypted Correct me if I'm wrong, but I'm pretty sure the host name is generally only sent in an HTTP header, which should be encrypted over HTTPS. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Ho...

In TLS, the server will send its certificate — and thus the domain name — in the clear.

[deleted]

Re: DNS over HTTPS

#82
“...for privacy...” and “Google runs one...”

Strikes me as funny. Interesting concept apart from this detail though. Are there any servers that aren’t owned by advertisers and the like?

Re: DNS over HTTPS

#83
post #40

Earlier quoted context omitted.

Can anyone give examples of cases where “performant” would be better than “efficient”? To my mind, the difference is that “performant” delivers results quickly, whereas “efficient” uses little energy. A performant solution might be efficient, but not necessarily, and vice versa. Does anyone else share this understanding or am I living in a linguistic bubble? Not sure about Swedish (Daniel is Swedish), but in Finnish,…

efficiency = performance / resources Efficient has connotations of economy, of optimal use of resources but with a hint of parsimony - another way to get efficiency is to reduce the denominator. Performant emphasises the numerator much more.

*increase the denominator.

nitpick aside, agreed

Re: DNS over HTTPS

#85

Actual DNS servers and clients have supported TLS since the early years of this decade. What's gained by adding HTTP transport overhead?

What dns servers and clients support TLS?

Unbound does it natively, and BIND and the rest use DNSCrypt's shim

Re: DNS over HTTPS

#86
post #76

Actual DNS servers and clients have supported TLS since the early years of this decade. What's gained by adding HTTP transport overhead?

http is not overhead, http is the only transport that can go through middle boxes.

if the traffic is encrypted how can you tell whether it's http or plain dns?

Re: DNS over HTTPS

#87
post #61
post #54

Earlier quoted context omitted.

It is not actually translating anything since performant is not considered a real word in English, although I commonly see it used in the tech world.

> performant is not considered a real word in English, although I commonly see it used... This is close to being a contradiction in terms. The purpose of words is to communicate, and if a word is being successfully used to communicate -- which clearly it is -- what exactly does it mean to say that isn't "considered a real word"? Also, "Considered" by whom? The dictionary? Dictionaries are descriptivist -- they record…

> (As it happens, "performant" is at the stage where it is starting to pass those thresholds, and is now in the OED [2])

Strictly speaking, I don't believe your [2] is the OED. It's "Oxford Living Dictionaries", which I assume tries to be more current/dynamic, but might be regarded as less authoritative.

Interestingly, the word "performant" is in the OED itself, with the earliest citation being from 1809 -- but it is listed only as a noun, meaning "A person who performs a duty, ceremony, etc., a performer", not the adjectival usage under discussion here.

http://www.oed.com/view/Entry/262085?redirectedFrom=performa... (requires login)

Re: DNS over HTTPS

#88

Earlier quoted context omitted.

> Side note - I just learned that performant is not a recognized word ( https://english.stackexchange.com/questions/38945/what-is-wr... ) I don't personally use the word since there are many alternatives, but its use is now definitely widespread and consistently understood. There's really no argument against the fact that it has entered the English lexicon.

Can anyone give examples of cases where “performant” would be better than “efficient”? To my mind, the difference is that “performant” delivers results quickly, whereas “efficient” uses little energy. A performant solution might be efficient, but not necessarily, and vice versa. Does anyone else share this understanding or am I living in a linguistic bubble? Not sure about Swedish (Daniel is Swedish), but in Finnish,…

I think the word that was being grasped for is 'faster'.

It suffers in that doesn't sound very technical.

Re: DNS over HTTPS

#89

Earlier quoted context omitted.

I don't use it either, and I agree with the poster on that stackexchange link about it sounding like manager/marketing-speak, but when I see it, it makes me pause for a second to think about what really means (perhaps that's the point) --- I had this exchange with a coworker not long ago: CW: ...and this way it'll be more performant too. Me: Performant? As in faster? CW: Yes. Me (to self): Then why didn't you just sa…

Performant to me implies performing better against the relevant metrics. So faster, maybe, but perhaps smaller and more energy efficient too. If the context of the metrics is already understood then it seems quite a cromulent word.

What's cromulent mean? I looked it up at dictionary.com and couldn't find anything. Or are you making up more words to point out the irony? :)

Re: DNS over HTTPS

#90
post #39
post #27

I can see how DNS over HTTPS addresses security, but I do not see how it helps with privacy. After resolving the IP address over secure connection HTTPS still sends the host name unencrypted, so one can just eavesdrop on that. And if encrypted DNS becomes widespread, I suspect that various state-imposed firewalls like one Russia will just look for HTTPS connection header to block a particular site.

Are you talking about leaking names through TLS? As I understand it, this would fix leaking during DNS resolution, fixing any leaks from TLS is a separate issue. And yes, when that's fixed, you'll still be leaking destination IP. But if not one step at time, how is it going to get better? :)

One step, but in what direction?
Post reply on HN