Google Chrome
Tsawon watanni yanzu Google ya bayyana aniyarsa ta cire masu toshe ad daga mashigar gidan yanar gizo ta Chrome., wannan tare da jagorar cewa masu toshewar zasu sami matsala a canje-canjen da aka gabatar a cikin Manifest V3.
Dukda cewa Google Har ila yau, ya yi jayayya cewa wasu masu ba da sabis kan layi suna da fasahar da aka gina ta na iya daidaita muhimman fasalolin talla na dijital daga ɓangare na uku.
Masu haɓaka Chrome sun yi ƙoƙarin ba da hujjar dakatar da tallafi don yanayin toshewa daga webRequest API, Yana ba ka damar canza abubuwan da aka karɓa a kan tashi kuma ana amfani da su a cikin ƙari don toshe tallace-tallace, kariya daga ɓarna, ɓatar da bayanai, leken asiri kan masu amfani, kulawar iyaye da sirrinsu.
Yanayin toshewar yanar gizoRequest API yana haifar da yawan amfani da albarkatu.
Lokacin amfani da wannan API, mai binciken yana fara aika duk bayanan da ke ƙunshe a cikin buƙatar hanyar sadarwar zuwa plugin ɗin, plugin ɗin ya yi shi kuma ya dawo da sigar da aka gyara don ci gaba da aiki a cikin mai bincike ko matsaloli tare da umarnin toshewa.
A wannan yanayin, babban jinkirin da aka samu ba a matakin aiwatar da zirga-zirga tare da toshe-ba, amma saboda sama-sama na daidaita aiwatar da fulogin.
Musamman, irin waɗannan magudi suna buƙatar ƙaddamarwa don haɓaka wani tsari na daban, da kuma amfani da IPC don hulɗa tare da wannan tsari da hanyoyin haɗa bayanai.
Ara mai cikakken iko yana sarrafa dukkan zirga-zirga a ƙananan matakin, wanda ke buɗe babbar dama don cin zarafi da keta haƙƙin sirri.
Google har yanzu yana goyon bayan cire API
Dangane da ƙididdigar Google, a cikin An gano kashi 42% na duk abubuwan da aka gano na cutarwa, an yi amfani da webRequest API.
Abin takaici facin baya ba da izinin kowane ɗayan ɓarnatattun abubuwa. Don haka don inganta kariya, an yanke shawarar ƙayyade abubuwan kari a matakin API.
Mahimmin ra'ayi shine don samar da plugins tare da iyakance damar zuwa duk zirga-zirga, idan ba kawai ga bayanan da suka wajaba don aiwatar da aikin da aka ɗauki ciki ba.
Musamman, don toshe abun ciki ba lallai bane a samar da plugin ɗin tare da cikakken damar yin amfani da duk bayanan mai amfani na sirri.
Shawarwarin da aka gabatar don maye gurbin declarativeNetRequest API yana kula da duk aikin babban tsarin aikin tace abun ciki kuma yana bukatar kwafin shigar da karin plugins. Bugu da ƙari, ƙari ba zai iya tsoma baki tare da zirga-zirga ba kuma bayanan sirri na mai amfani ba zai yiwu ba.
Google yayi la'akari da yawancin maganganun game da rashin ayyukan API, declarativeNetRequest kuma ya kara iyaka a kan yawan dokokin tacewa daga 30,000 da aka samar da asali ga kowane kari zuwa matsakaicin duniya na 150,000 sannan kuma ya kara ikon gyarawa da kara ka'idoji, cire da maye gurbin kanun HTTP (Referer, Cookie, Set-Cookie) kuma nemi sigogi.
Masu haɓaka ba su da cikakkiyar yarda
Gwaji ta masu haɓaka ƙari yana nuna cewa aikin ad-blocking add-ons ba shi da kyau idan aka kwatanta da asalin gaba ɗaya (lokacin gwaji, kwatanta ayyukan wasu add-ons, amma ba tare da yin la'akari da sama da ƙarin aikin da ke daidaitawa ba aiwatar da masu aiki a yanayin toshewar yanar gizo na APIRequest API).
Ba shi da amfani a daina tallafawa API, rayayye amfani a cikin plugins. Maimakon cire shi, masu haɓaka suna jayayya cewa za a iya ƙara wani ƙuduri daban-daban kuma za a iya sarrafa shi sosai don dacewar amfani da shi a cikin ƙari, wanda zai iya ceton marubutan manyan mashahuran plugins daga cikakken aikin sarrafa kayayyakinsu da hana ragin aiki.
Madadin da aka gabatar dashi na bayyanaNetRequest baya rufe duk bukatun masu bunkasa kayan masarufi don toshe tallace-tallace da kuma tabbatar da tsaro / sirri, saboda baya bada cikakken iko akan buƙatun cibiyar sadarwar, baya bada izinin amfani da matattarar matattarar bayanai kuma baya bada izinin amfani hadaddun dokoki waɗanda ke haɗuwa da juna dangane da yanayin.
Source: https://security.googleblog.com/