Google Chrome
Bayan Mozilla, Google ya bayyana aniyarsa ta yin gwaji don gwaji Aiwatar da burauzar Chrome tare da «DNS akan HTTPS » (DoH, DNS akan HTTPS). Tare da fitowar Chrome 78, shirya don 22 ga Oktoba.
Wasu rukunan masu amfani ta tsohuwa za su iya shiga cikin gwajin Don ba da damar DoH, masu amfani ne kawai za su shiga cikin tsarin tsarin yanzu, wanda wasu masu samar da DNS waɗanda ke tallafawa DoH suka gane shi.
Mai ba da sabis na DNS ya haɗa da sabis na Google, Cloudflare, OpenDNS, Quad9, Cleanbrowsing da DNS.SB. Idan saitunan DNS na mai amfani sun tantance ɗayan sabobin DNS na sama, DoH a cikin Chrome za a kunna ta tsohuwa.
Ga waɗanda ke amfani da sabobin DNS wanda mai ba da sabis na Intanet na gida ya bayar, komai zai kasance ba canzawa ba kuma za a ci gaba da amfani da ƙudurin tsarin don tambayoyin DNS.
Wani bambanci mai mahimmanci daga aiwatarwar DoH a cikin Firefox, wanda a ciki za a sami asalin DoH na asali zai fara a ƙarshen Satumba, shine rashin haɗi zuwa sabis na DoH ɗaya.
Idan Firefox yayi amfani da sabar CloudFlare DNS ta tsohuwa, Chrome kawai zai sabunta hanyar aiki tare da DNS zuwa sabis daidai, ba tare da canza mai ba da DNS ba.
Idan ana so, mai amfani na iya kunna ko kashe DoH ta amfani da saitin "chrome: // flags / # dns-over-https". Menene ƙari hanyoyi uku na aiki suna tallafawa "Lafiya", "atomatik" da "kashe".
- A cikin "aminci", ana ƙaddamar da runduna ne kawai bisa ƙimar aminci (waɗanda aka karɓa a kan amintaccen haɗi) da buƙatu ta hanyar DoH, ba a amfani da komawa zuwa DNS na yau da kullun.
- A cikin yanayin "atomatik", idan DoH da amintaccen ɓoye ba su kasance ba, yana yiwuwa a karɓi bayanai daga ɓoyayyen maɓuɓɓugi da samun dama ta hanyar gargajiyar DNS.
- A cikin yanayin "kashe", ana bincika cache gaba ɗaya kuma, idan babu bayanai, ana aika buƙata ta hanyar tsarin tsarin DNS. An saita yanayin ta hanyar saitunan kDnsOverHttpsMode da samfurin taswirar sabar ta hanyar kDnsOverHttpsTemplates.
Gwajin don ba da damar DoH za a yi shi a kan duk dandamali masu talla a cikin Chrome, ban da Linux da iOS, saboda yanayin mara kyau mara kyau na ƙididdigar daidaitawar warwarewa da kuma iyakance damar isa ga tsarin tsarin DNS.
A yayin da bayan kunna DoH akwai gazawa don aika buƙatu zuwa uwar garken DoH (alal misali, saboda toshewarsa, gazawarsa ko gazawar haɗin cibiyar sadarwa), mai bincike zai dawo da saitunan tsarin DNS kai tsaye.
Dalilin gwajin shine don kammala aiwatar da DoH da bincika tasirin aikace-aikacen DoH akan aiki.
Ya kamata a lura cewa, a zahiri, an ƙara tallafin DoH zuwa mashigin lambar Chrome a cikin Fabrairu, amma don daidaitawa da kunna DoH, dole ne Chrome ya ƙaddamar tare da tuta ta musamman da zaɓuɓɓukan da ba bayyane ba.
Yana da muhimmanci a san hakan DoH na iya zama mai taimako wajen kawar da bayanan sirrin sunan mai gida nema ta hanyar sabobin DNS na masu samarwa, yaƙi da hare-haren MITM kuma maye gurbin zirga-zirgar DNS (misali, lokacin haɗawa zuwa Wi-Fi na jama'a) da adawa da matakin matakin DNS (DoH) ba za su iya maye gurbin VPN ba a cikin yanki na guje wa bulolin da aka aiwatar a matakin DPI) ko don tsara aiki idan ba shi yiwuwa kai tsaye zuwa Sabobin DNS (misali, lokacin aiki ta hanyar wakili).
Idan a cikin yanayi na yau da kullun, ana aika tambayoyin DNS kai tsaye zuwa sabobin DNS waɗanda aka ayyana a cikin tsarin tsarin, to a game da DoH, buƙatar ƙayyade adireshin IP ɗin mai masaukin yana ƙunshe cikin zirga-zirgar HTTPS kuma an aika zuwa uwar garken HTTP wanda warware hanyoyin aiwatar da buƙatun ta hanyar yanar gizo API.
Daidaitaccen tsarin DNSSEC yana amfani da ɓoyewa kawai don abokin ciniki da ingantaccen uwar garke.