Request for DNS over HTTPS API

[ExpressVPN]

We’d like to request that Chrome implement an extension API to be able to get and set the following DNS over HTTPS related settings:

• Enable/Disable DNS over HTTPS

• Use custom DNS provider

We support the DNS over HTTPS initiative, however, we believe it would be better for users if they had the choice to use a service like ours end-to-end rather than having some of their private data sent off to a party with whom they haven't agreed to use.

If there's somewhere more appropriate we should make this request please let us know.

Thanks for your consideration.

—ExpressVPN

[Andrey Meshkov]

Great idea!

[Decklin / Deco]

It should be noted that this already exists within Chrome (through chrome://flags) - that is supporting sending DNS requests over HTTPS as well as using the OS level async DNS resolver, meaning a user can manually declare a HTTPS/2 address to use in which Chrome will utilise.

This brings up the question - if extensions are able to modify this DNS setting, would they be considered a "third party server"? The answer being yes, they would - and also not withstanding the imminent security issues which would arise by allowing extensions to modify DNS/DNS protocol traffic through the browser.

A novel idea, yet laden with problems rendering it impossible to implement effectively.

--
You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/5b8456ad-d5a4-49b2-8f04-6054091b5f4c%40chromium.org.

[Simeon Vincent]

Hey ExpressVPN folks,

I think your best next-step is to open a feature request on crbug.com. From there, triage folks should route it to the right team for further consideration and discussion. Time permitting, I may also be able to track down the right stakeholders to get eyes on the request.

Simeon - @dotproto

Extensions Developer Advocate

On Friday, October 4, 2019 at 4:37:08 AM UTC-7, Decklin / Deco wrote:

It should be noted that this already exists within Chrome (through chrome://flags) - that is supporting sending DNS requests over HTTPS as well as using the OS level async DNS resolver, meaning a user can manually declare a HTTPS/2 address to use in which Chrome will utilise.

This brings up the question - if extensions are able to modify this DNS setting, would they be considered a "third party server"? The answer being yes, they would - and also not withstanding the imminent security issues which would arise by allowing extensions to modify DNS/DNS protocol traffic through the browser.

A novel idea, yet laden with problems rendering it impossible to implement effectively.

On Fri, 4 Oct 2019, 02:04 'ExpressVPN' via Chromium Extensions, <chromium-extensions@chromium.org> wrote:

We’d like to request that Chrome implement an extension API to be able to get and set the following DNS over HTTPS related settings:

• Enable/Disable DNS over HTTPS

• Use custom DNS provider

We support the DNS over HTTPS initiative, however, we believe it would be better for users if they had the choice to use a service like ours end-to-end rather than having some of their private data sent off to a party with whom they haven't agreed to use.

If there's somewhere more appropriate we should make this request please let us know.

Thanks for your consideration.

—ExpressVPN

--
You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extensions+unsub...@chromium.org.

[ExpressVPN]

Thanks Simeon - we've posted the request here: https://bugs.chromium.org/p/chromium/issues/detail?id=1010824

On Thursday, October 10, 2019 at 3:31:09 AM UTC+8, Simeon Vincent wrote:

Hey ExpressVPN folks,

I think your best next-step is to open a feature request on crbug.com. From there, triage folks should route it to the right team for further consideration and discussion. Time permitting, I may also be able to track down the right stakeholders to get eyes on the request.

Simeon - @dotproto

Extensions Developer Advocate

On Friday, October 4, 2019 at 4:37:08 AM UTC-7, Decklin / Deco wrote:

It should be noted that this already exists within Chrome (through chrome://flags) - that is supporting sending DNS requests over HTTPS as well as using the OS level async DNS resolver, meaning a user can manually declare a HTTPS/2 address to use in which Chrome will utilise.

This brings up the question - if extensions are able to modify this DNS setting, would they be considered a "third party server"? The answer being yes, they would - and also not withstanding the imminent security issues which would arise by allowing extensions to modify DNS/DNS protocol traffic through the browser.

A novel idea, yet laden with problems rendering it impossible to implement effectively.

[pop buz]

Thanks for everything you do for me and I will be there at least a week or two to get the rest 😊 were gonna need some help with the connection between the http and DNS servers.

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/5b8456ad-d5a4-49b2-8f04-6054091b5f4c%40chromium.org.

--

You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/a952a4b4-c76d-455e-8be3-eb33b501847f%40chromium.org.