New issue
Advanced search Search tips

Issue 655867 link

Starred by 1 user
Status: Duplicate
Merged: issue 601145
Owner: ----
Closed: Oct 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Feature



Sign in to add a comment

Chrome response to DNSCrypt in Yandex.Browser

Reported by jbionic2...@gmail.com, Oct 14 2016 
UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.59 Safari/537.36

Steps to reproduce the problem:
1. None
2. 
3. 

What is the expected behavior?

What went wrong?
A well-known Russian Google-like company called Yandex, which has developed its own browser  and now is striving to popularize it by adding extra security features, has just announced the release of a new version of its famous Yandex.Browser with DNSCrypt functionality:
https://habrahabr.ru/company/yandex/blog/280380/

I wonder whether Chrome is going to respond by implementing anything similar?

Did this work before? N/A 

Chrome version: 54.0.2840.59  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 23.0 r0

Comment 1 by mmoroz@chromium.org, Oct 14 2016

Components: Internals>Network>DNS
Labels: -Type-Bug-Security -Restrict-View-SecurityTeam Type-Feature
Mergedinto: 601145
Status: Duplicate (was: Unconfirmed)
Hello, thanks for your report.

1) This is not a security issue. Bug-Security template is intended to be used only for security bugs (https://www.chromium.org/Home/chromium-security). I'm removing security labels.

2) Looks like you are asking this question for a while (https://productforums.google.com/forum/#!msg/chrome/kFGDpsAFchY/EKoYs9f-EAAJ). If you are interested in tracking of DNS issues in Chromium, you can use the following search query for the bug tracker:

https://bugs.chromium.org/p/chromium/issues/list?can=2&q=component%3AInternals%3ENetwork%3EDNS+&colspec=ID+Pri+M+Stars+ReleaseBlock+Component+Status+Owner+Summary+OS+Modified&x=m&y=releaseblock&cells=ids

By the way, there is a similar feature request (bug 601145) and I'm duplicating this issue into there.
►

Sign in to add a comment