diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md index 3953f47d26f..05642d350b0 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md @@ -43,6 +43,14 @@ Here you can choose which proxy AdGuard should use to download filter updates or ## Use SockFilter driver -Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. +Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. If this option is disabled, AdGuard will switch to the older WFP driver instead. -If this option is disabled, AdGuard will switch to the older WFP driver instead. +SockFilter was first introduced in v8.0 RC. It is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md index 251e49cf286..1ab588bb16c 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Because of this, TDI-based traffic visibility becomes increasingly unstable. In AdGuard already treats the TDI driver as deprecated, and its complete removal is planned as the product evolves. +## Permanent solution + +From v8.0 RC, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows-8/settings/app-settings/network-settings/). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Temporary solution Certain Windows registry changes can force the browser to stop using AppContainer, causing its processes to run in a non-sandboxed mode again. Network Service stops using the WSK stack and falls back to a network path that the TDI driver can see. AdGuard then regains the ability to filter browser traffic. @@ -123,7 +131,3 @@ You should see the following policies active: If available, click _Reload policies_. Done! - -## Permanent solution - -We’re planning to add support for the SockFilter driver in the upcoming versions. It will fix the issue by solving conflicts in the WFP stack. [More information](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index 5945618ea9c..f8074e9cfa1 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -17,23 +17,35 @@ In this module you can select the checkbox _Use AdGuard as an HTTP proxy_ to use At last, there is a section with proxy settings. There you can specify which proxy server AdGuard should use to update filters, get new versions, and so on. -### SockFilter and other network drivers +### Enable traffic filtering -In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. +Traffic filtering is the core mechanism that allows AdGuard to inspect and control the network traffic generated by applications on your computer. When it is enabled, AdGuard intercepts outgoing and incoming connections and checks them against its filtering rules. If a request matches a blocking rule, AdGuard can block it, modify it, or allow it depending on the configuration. In AdGuard for Windows, this interception is implemented through network drivers. -**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. +If HTTPS filtering is enabled, AdGuard performs a controlled local TLS interception: it decrypts the traffic using its local certificate, applies filtering rules, and then re-encrypts the traffic before sending it to the browser. The driver simply provides the system-level access needed for AdGuard to intercept these connections. -The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +#### SockFilter **SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. -Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: +SockFilter was first implemented in version 7.22.4, and it is still considered unstable — you may encounter bugs. Once fully tested and implemented, SockFilter has the potential to offer several advantages over other drivers: -- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. - **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. -- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. -When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. +#### WFP + +**WFP** (Windows Filtering Platform) is a Microsoft networking framework built into Windows that allows software to filter and monitor network packets at different layers of the system networking stack. AdGuard uses WFP to safely hook into the network flow of applications and apply filtering rules before the traffic reaches the browser or the Internet. [More information](https://learn.microsoft.com/en-us/windows/win32/fwp/windows-filtering-platform-architecture-overview). + +While it is a powerful driver, it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) and lower Internet speed for some users. + +#### TDI + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. ### AdGuard VPN diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index ab90a964b9f..5699b31b033 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -44,12 +44,8 @@ Before you start manually writing your own rules read our detailed [syntax guide Many websites gather information about their visitors, such as their IP addresses, browser and operating system details, screen resolution, and the webpage from which the user came or was redirected. Some websites use cookies to mark and identify your browser, save your personal settings and preferences. This allows them to “recognize” you on your next visit. Tracking protection safeguards your personal information from these data- and statistics-gathering systems. -![Tracking protection levels \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection1.png) - You can adjust the _Tracking Protection_ settings as needed. For example, you can prevent websites from receiving the search request that you used to find them on the Internet, automatically delete third- and first-party cookies, and disable location sharing in your browser, to prevent tracking of your whereabouts. -![Tracking protection custom features \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection2.png) - To learn everything about _Tracking protection_ and its many options, [read this article](/general/stealth-mode). ### Browsing security diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md index 62370bf3eb1..bec08d0c665 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Because of this, TDI-based traffic visibility becomes increasingly unstable. In AdGuard already treats the TDI driver as deprecated, and its complete removal is planned as the product evolves. +## Permanent solution + +From v7.22.4, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows/features/network/#sockfilter-and-other-network-drivers). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Temporary solution Certain Windows registry changes can force the browser to stop using AppContainer, causing its processes to run in a non-sandboxed mode again. Network Service stops using the WSK stack and falls back to a network path that the TDI driver can see. AdGuard then regains the ability to filter browser traffic. @@ -136,7 +144,3 @@ You should see the following policies active: If available, click _Reload policies_. Done! - -## Permanent solution - -We’re planning to add support for the SockFilter driver in the upcoming versions. It will fix the issue by solving conflicts in the WFP stack. [More information](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/be/docusaurus-plugin-content-docs/current/general/github-repos.md b/i18n/be/docusaurus-plugin-content-docs/current/general/github-repos.md new file mode 100644 index 00000000000..dfb164c44bc --- /dev/null +++ b/i18n/be/docusaurus-plugin-content-docs/current/general/github-repos.md @@ -0,0 +1,238 @@ +--- +title: AdGuard’s GitHub repositories +sidebar_position: 9 +--- + +At AdGuard, our goal is to make the Internet safer, more comfortable, and more transparent. This commitment is reflected not only in our product features and strict privacy policies, but also in the fact that we keep our work as open as possible. That includes actively interacting with our community. + +This is why [all of our products have public repositories](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse) — online spaces where anybody can see what we are working on, report issues directly to AdGuard developers, and even contribute to our open-source projects. The repositories cover our ad-blocking apps, filters, browser extensions, DNS solutions, VPN tools, developer utilities, and more. There are different platforms that offer such functionality, but the most popular one by far is GitHub, and all AdGuard projects are stored there. + +This article lists the most important repositories by category, summarizes the purpose of each one, and gives a simple breakdown of what users can do there. + +:::tip + +Pro tip: Creating an issue on GitHub is the most effective way to bring the attention of AdGuard developers to a problem. Just make sure to check that a similar issue doesn’t already exist and describe the problem in a comprehensive but concise way. If it does exist, you can upvote it. + +::: + +## What is Github and its repositories + +Very simply put, you can think of GitHub as sort of Google Docs for code, where multiple people can work on the same project, track changes, and see who made which updates. It provides a central, cloud-based place to store your code so it’s accessible from anywhere. It also has teamwork tools for reviewing changes, fixing issues, and merging everyone’s work smoothly. + +GitHub is widely used for open-source projects, letting anyone view the code, suggest improvements, and contribute. + +A repository (often called “repo” for short) is the most basic element of GitHub. It’s a place where you can store your code, your files, and each file’s revision history. Repositories can have multiple collaborators and can be either public or private. + +## What can you do in AdGuard’s repositories + +You can find links to key repositories below in this article or visit the [general AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all) for a full list. In most repos, you can: + +- **View README file** on the main page: it gives you an introduction to the product and its repo + ![README file \*border](https://cdn.adtidy.org/content/blog/github-repos/see-readme.png) + +- **Check existing bug reports or feature requests**, comment and upvote + ![Check issues \*border](https://cdn.adtidy.org/content/blog/github-repos/check-issues.png) + +- **Create issues** to report bugs or request features + ![Create issues \*border](https://cdn.adtidy.org/content/blog/github-repos/create-issue.png) + +- **Check releases** for different versions and their changelogs (and install an older version if needed) + ![Check releases \*border](https://cdn.adtidy.org/content/blog/github-repos/check-releases.png) + +- **Install any older or beta version** if needed + ![Download builds \*border](https://cdn.adtidy.org/content/blog/github-repos/download-releases.png) + +:::note + +If you are new to GitHub, you’ll need to create a GitHub account in order to create new issues and comment on the existing ones. + +::: + +In open-source repos advanced users can also: + +- **Browse code** to understand product logic, what technologies are used and how they are implemented +- **Fork and contribute** via pull requests + +Whether you’re a casual user, technical expert, or a developer, AdGuard welcomes all community participation across its GitHub repos. + +## Legal documents + +### [LegalDocs](https://github.com/AdguardTeam/LegalDocs) + +As part of our commitment to transparency, we host all legal documents — such as End-User License Agreements, Privacy Policies, and Terms and Conditions — on GitHub. Our _LegalDocs_ repo lets anyone check the full history of changes to these documents. + +## AdGuard Ad Blocker products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdguardForAndroid](https://github.com/AdguardTeam/AdguardForAndroid) + +Repository of AdGuard for Android — an app that provides system-wide ad blocking. + +### [AdguardForiOS](https://github.com/AdguardTeam/AdguardForiOS) + +Repository of AdGuard for iOS — Safari content blocker with DNS and custom filters. Users can also check open-source code. + +### [AdguardForWindows](https://github.com/AdguardTeam/AdguardForWindows) + +Repository of AdGuard for Windows. Non-open-source; GitHub used as an open bug tracker. + +### [AdguardForMac](https://github.com/AdguardTeam/AdguardForMac) + +Repository of AdGuard for Mac — macOS standalone content blocker. Bug tracker only. + +### [AdguardBrowserExtension](https://github.com/AdguardTeam/AdguardBrowserExtension) + +Repository of AdGuard Browser Extension — extension that provides ad blocking with enhanced privacy for Chrome, Firefox, Opera, Edge. + +### [AdguardForSafari](https://github.com/AdguardTeam/AdGuardForSafari) + +Repository of AdGuard for Safari — Safari ad blocking extension for Mac. Users can also check open-sourced code. + +### [AdGuardCLI](https://github.com/AdguardTeam/AdGuardCLI) + +Repository of AdGuard for Linux — a command‑line interface for managing ad blocking. + +## AdGuard VPN products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdGuardVPNForiOS](https://github.com/AdguardTeam/AdGuardVPNForiOS) + +Repository of AdGuard VPN for iOS. Serves as an open bug tracker. + +### [AdGuardVPNForAndroid](https://github.com/AdguardTeam/AdGuardVPNForAndroid) + +Repository of AdGuard VPN for Android. Serves as an open bug tracker. + +### [AdGuardVPNForWindows](https://github.com/AdguardTeam/AdGuardVPNForWindows) + +Repository of AdGuard VPN for Windows. Serves as an open bug tracker. + +### [AdGuardVPNForMac](https://github.com/AdguardTeam/AdGuardVPNForMac) + +Repository of AdGuard VPN for Mac — app designed for macOS. + +### [AdGuardVPNExtension](https://github.com/AdguardTeam/AdGuardVPNExtension) + +Repository of AdGuard VPN Browser Extension. + +### [AdGuardVPNCLI](https://github.com/AdguardTeam/AdGuardVPNCLI) + +Repository of AdGuard VPN for Linux — a command‑line interface for managing VPN connection. The repo acts as a bug tracker. + +## DNS-based products + +### [AdGuardDNS](https://github.com/AdguardTeam/AdGuardDNS) + +Open-source repository that is also used for tracking bugs and issues related to AdGuard DNS service. Users can: + +- View and report DNS issues +- Suggest improvements + +### [AdGuardHome](https://github.com/AdguardTeam/AdGuardHome) + +Repository of AdGuard Home — free network-wide software for blocking ads and trackers via DNS. Users can: + +- Check and file bug reports or feature requests +- Review or contribute to code +- Download and install releases + +## Documentation and Knowledge bases + +Knowledge bases are aimed to help users better understand and use AdGuard. They describe each AdGuard product in detail: from feature overviews and problem-solving guides to advanced setting manuals and API documentations. In the repositories users can: + +- Suggest corrections or edits to knowledge base articles +- Propose new articles +- Test or run the local version + +### [KnowledgeBase](https://github.com/AdguardTeam/KnowledgeBase) + +Central documentation for AdGuard Ad Blocker and the technologies related to it. + +### [KnowledgeBaseDNS](https://github.com/AdguardTeam/KnowledgeBaseDNS) + +Detailed feature overview, troubleshooting guides and documentation for AdGuard DNS (both Public and Private), AdGuard Home, and everything related to them. + +### [KnowledgeBaseVPN](https://github.com/AdguardTeam/KnowledgeBaseVPN) + +Detailed feature overview and troubleshooting guides for AdGuard VPN. + +### [KnowledgeBaseMail](https://github.com/AdguardTeam/KnowledgeBaseMail) + +Detailed feature overview and troubleshooting guides of AdGuard Mail. + +## Core libraries + +### [CoreLibs](https://github.com/AdguardTeam/CoreLibs) + +AdGuard’s cross-platform core filtering engine. Used in Android, Windows, and Mac products. Users can: + +- Explore filtering logic and DNS handling +- Report bugs and suggest features via Issues + +### [DNSLibs](https://github.com/AdguardTeam/DNSLibs) + +A DNS library used by CoreLibs and AdGuardHome. Users can: + +- Review and contribute to low-level DNS implementation +- Suggest optimizations + +### [VPNLibs](https://github.com/AdguardTeam/VPNLibs) + +Shared codebase used in AdGuard VPN products across platforms for AdGuard VPN protocol implementation. Users can: + +- Contribute to VPN stack behavior +- Report or view performance issues and bugs + +## Core ad blocking and filtering technologies + +### [AdguardFilters](https://github.com/AdguardTeam/AdguardFilters) + +Contains AdGuard’s core filter lists. Users can: + +- View and download filter lists +- Create issues to report false positives or suggest new rules +- Monitor updates to filter logic + +### [AdGuardSDNSFilter](https://github.com/AdguardTeam/AdGuardSDNSFilter) + +Repository of AdGuard DNS filter — the main DNS-level blocking list used in AdGuard DNS and DNS filtering features. Users can: + +- Inspect the current rule set +- Propose changes or additions + +### [AGLint](https://github.com/AdguardTeam/AGLint) + +A linter for adblock filter list syntax. Users can: + +- Install AGLint to check their projects for rule issues +- Contribute to lint rules + +### [Scriptlets](https://github.com/AdguardTeam/Scriptlets) + +JavaScript helpers used in filtering rules. Users can: + +- Explore available scriptlets +- Submit pull requests for new scriptlets + +### [tsurlfilter](https://github.com/AdguardTeam/tsurlfilter) + +TypeScript content blocker library for browser extensions. Users can: + +- Explore how filtering logic is implemented +- Contribute fixes and features + +## There’s more + +Above, we listed 27 main public AdGuard repositories out of 96 total. If you want to go down the rabbit hole, you can [find the rest on the AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse). + +We’ll be waiting for your feedback there! Stay safe online and offline. diff --git a/i18n/be/docusaurus-plugin-content-docs/current/general/how-to-install.md b/i18n/be/docusaurus-plugin-content-docs/current/general/how-to-install.md index 106a29529a8..4ba78d7a094 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/general/how-to-install.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/general/how-to-install.md @@ -1,6 +1,6 @@ --- title: How to install AdGuard -sidebar_position: 9 +sidebar_position: 10 --- Depending on which AdGuard app or browser extension you want to install, follow one of these links to find the relevant article: diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md index 3953f47d26f..05642d350b0 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md @@ -43,6 +43,14 @@ Here you can choose which proxy AdGuard should use to download filter updates or ## Use SockFilter driver -Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. +Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. If this option is disabled, AdGuard will switch to the older WFP driver instead. -If this option is disabled, AdGuard will switch to the older WFP driver instead. +SockFilter was first introduced in v8.0 RC. It is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md index 251e49cf286..1ab588bb16c 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Because of this, TDI-based traffic visibility becomes increasingly unstable. In AdGuard already treats the TDI driver as deprecated, and its complete removal is planned as the product evolves. +## Permanent solution + +From v8.0 RC, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows-8/settings/app-settings/network-settings/). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Temporary solution Certain Windows registry changes can force the browser to stop using AppContainer, causing its processes to run in a non-sandboxed mode again. Network Service stops using the WSK stack and falls back to a network path that the TDI driver can see. AdGuard then regains the ability to filter browser traffic. @@ -123,7 +131,3 @@ You should see the following policies active: If available, click _Reload policies_. Done! - -## Permanent solution - -We’re planning to add support for the SockFilter driver in the upcoming versions. It will fix the issue by solving conflicts in the WFP stack. [More information](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index 5945618ea9c..f8074e9cfa1 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -17,23 +17,35 @@ In this module you can select the checkbox _Use AdGuard as an HTTP proxy_ to use At last, there is a section with proxy settings. There you can specify which proxy server AdGuard should use to update filters, get new versions, and so on. -### SockFilter and other network drivers +### Enable traffic filtering -In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. +Traffic filtering is the core mechanism that allows AdGuard to inspect and control the network traffic generated by applications on your computer. When it is enabled, AdGuard intercepts outgoing and incoming connections and checks them against its filtering rules. If a request matches a blocking rule, AdGuard can block it, modify it, or allow it depending on the configuration. In AdGuard for Windows, this interception is implemented through network drivers. -**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. +If HTTPS filtering is enabled, AdGuard performs a controlled local TLS interception: it decrypts the traffic using its local certificate, applies filtering rules, and then re-encrypts the traffic before sending it to the browser. The driver simply provides the system-level access needed for AdGuard to intercept these connections. -The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +#### SockFilter **SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. -Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: +SockFilter was first implemented in version 7.22.4, and it is still considered unstable — you may encounter bugs. Once fully tested and implemented, SockFilter has the potential to offer several advantages over other drivers: -- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. - **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. -- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. -When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. +#### WFP + +**WFP** (Windows Filtering Platform) is a Microsoft networking framework built into Windows that allows software to filter and monitor network packets at different layers of the system networking stack. AdGuard uses WFP to safely hook into the network flow of applications and apply filtering rules before the traffic reaches the browser or the Internet. [More information](https://learn.microsoft.com/en-us/windows/win32/fwp/windows-filtering-platform-architecture-overview). + +While it is a powerful driver, it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) and lower Internet speed for some users. + +#### TDI + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. ### AdGuard VPN diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index ab90a964b9f..5699b31b033 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -44,12 +44,8 @@ Before you start manually writing your own rules read our detailed [syntax guide Many websites gather information about their visitors, such as their IP addresses, browser and operating system details, screen resolution, and the webpage from which the user came or was redirected. Some websites use cookies to mark and identify your browser, save your personal settings and preferences. This allows them to “recognize” you on your next visit. Tracking protection safeguards your personal information from these data- and statistics-gathering systems. -![Tracking protection levels \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection1.png) - You can adjust the _Tracking Protection_ settings as needed. For example, you can prevent websites from receiving the search request that you used to find them on the Internet, automatically delete third- and first-party cookies, and disable location sharing in your browser, to prevent tracking of your whereabouts. -![Tracking protection custom features \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection2.png) - To learn everything about _Tracking protection_ and its many options, [read this article](/general/stealth-mode). ### Browsing security diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md index 62370bf3eb1..bec08d0c665 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Because of this, TDI-based traffic visibility becomes increasingly unstable. In AdGuard already treats the TDI driver as deprecated, and its complete removal is planned as the product evolves. +## Permanent solution + +From v7.22.4, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows/features/network/#sockfilter-and-other-network-drivers). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Temporary solution Certain Windows registry changes can force the browser to stop using AppContainer, causing its processes to run in a non-sandboxed mode again. Network Service stops using the WSK stack and falls back to a network path that the TDI driver can see. AdGuard then regains the ability to filter browser traffic. @@ -136,7 +144,3 @@ You should see the following policies active: If available, click _Reload policies_. Done! - -## Permanent solution - -We’re planning to add support for the SockFilter driver in the upcoming versions. It will fix the issue by solving conflicts in the WFP stack. [More information](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/general/github-repos.md b/i18n/bn/docusaurus-plugin-content-docs/current/general/github-repos.md new file mode 100644 index 00000000000..dfb164c44bc --- /dev/null +++ b/i18n/bn/docusaurus-plugin-content-docs/current/general/github-repos.md @@ -0,0 +1,238 @@ +--- +title: AdGuard’s GitHub repositories +sidebar_position: 9 +--- + +At AdGuard, our goal is to make the Internet safer, more comfortable, and more transparent. This commitment is reflected not only in our product features and strict privacy policies, but also in the fact that we keep our work as open as possible. That includes actively interacting with our community. + +This is why [all of our products have public repositories](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse) — online spaces where anybody can see what we are working on, report issues directly to AdGuard developers, and even contribute to our open-source projects. The repositories cover our ad-blocking apps, filters, browser extensions, DNS solutions, VPN tools, developer utilities, and more. There are different platforms that offer such functionality, but the most popular one by far is GitHub, and all AdGuard projects are stored there. + +This article lists the most important repositories by category, summarizes the purpose of each one, and gives a simple breakdown of what users can do there. + +:::tip + +Pro tip: Creating an issue on GitHub is the most effective way to bring the attention of AdGuard developers to a problem. Just make sure to check that a similar issue doesn’t already exist and describe the problem in a comprehensive but concise way. If it does exist, you can upvote it. + +::: + +## What is Github and its repositories + +Very simply put, you can think of GitHub as sort of Google Docs for code, where multiple people can work on the same project, track changes, and see who made which updates. It provides a central, cloud-based place to store your code so it’s accessible from anywhere. It also has teamwork tools for reviewing changes, fixing issues, and merging everyone’s work smoothly. + +GitHub is widely used for open-source projects, letting anyone view the code, suggest improvements, and contribute. + +A repository (often called “repo” for short) is the most basic element of GitHub. It’s a place where you can store your code, your files, and each file’s revision history. Repositories can have multiple collaborators and can be either public or private. + +## What can you do in AdGuard’s repositories + +You can find links to key repositories below in this article or visit the [general AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all) for a full list. In most repos, you can: + +- **View README file** on the main page: it gives you an introduction to the product and its repo + ![README file \*border](https://cdn.adtidy.org/content/blog/github-repos/see-readme.png) + +- **Check existing bug reports or feature requests**, comment and upvote + ![Check issues \*border](https://cdn.adtidy.org/content/blog/github-repos/check-issues.png) + +- **Create issues** to report bugs or request features + ![Create issues \*border](https://cdn.adtidy.org/content/blog/github-repos/create-issue.png) + +- **Check releases** for different versions and their changelogs (and install an older version if needed) + ![Check releases \*border](https://cdn.adtidy.org/content/blog/github-repos/check-releases.png) + +- **Install any older or beta version** if needed + ![Download builds \*border](https://cdn.adtidy.org/content/blog/github-repos/download-releases.png) + +:::note + +If you are new to GitHub, you’ll need to create a GitHub account in order to create new issues and comment on the existing ones. + +::: + +In open-source repos advanced users can also: + +- **Browse code** to understand product logic, what technologies are used and how they are implemented +- **Fork and contribute** via pull requests + +Whether you’re a casual user, technical expert, or a developer, AdGuard welcomes all community participation across its GitHub repos. + +## Legal documents + +### [LegalDocs](https://github.com/AdguardTeam/LegalDocs) + +As part of our commitment to transparency, we host all legal documents — such as End-User License Agreements, Privacy Policies, and Terms and Conditions — on GitHub. Our _LegalDocs_ repo lets anyone check the full history of changes to these documents. + +## AdGuard Ad Blocker products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdguardForAndroid](https://github.com/AdguardTeam/AdguardForAndroid) + +Repository of AdGuard for Android — an app that provides system-wide ad blocking. + +### [AdguardForiOS](https://github.com/AdguardTeam/AdguardForiOS) + +Repository of AdGuard for iOS — Safari content blocker with DNS and custom filters. Users can also check open-source code. + +### [AdguardForWindows](https://github.com/AdguardTeam/AdguardForWindows) + +Repository of AdGuard for Windows. Non-open-source; GitHub used as an open bug tracker. + +### [AdguardForMac](https://github.com/AdguardTeam/AdguardForMac) + +Repository of AdGuard for Mac — macOS standalone content blocker. Bug tracker only. + +### [AdguardBrowserExtension](https://github.com/AdguardTeam/AdguardBrowserExtension) + +Repository of AdGuard Browser Extension — extension that provides ad blocking with enhanced privacy for Chrome, Firefox, Opera, Edge. + +### [AdguardForSafari](https://github.com/AdguardTeam/AdGuardForSafari) + +Repository of AdGuard for Safari — Safari ad blocking extension for Mac. Users can also check open-sourced code. + +### [AdGuardCLI](https://github.com/AdguardTeam/AdGuardCLI) + +Repository of AdGuard for Linux — a command‑line interface for managing ad blocking. + +## AdGuard VPN products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdGuardVPNForiOS](https://github.com/AdguardTeam/AdGuardVPNForiOS) + +Repository of AdGuard VPN for iOS. Serves as an open bug tracker. + +### [AdGuardVPNForAndroid](https://github.com/AdguardTeam/AdGuardVPNForAndroid) + +Repository of AdGuard VPN for Android. Serves as an open bug tracker. + +### [AdGuardVPNForWindows](https://github.com/AdguardTeam/AdGuardVPNForWindows) + +Repository of AdGuard VPN for Windows. Serves as an open bug tracker. + +### [AdGuardVPNForMac](https://github.com/AdguardTeam/AdGuardVPNForMac) + +Repository of AdGuard VPN for Mac — app designed for macOS. + +### [AdGuardVPNExtension](https://github.com/AdguardTeam/AdGuardVPNExtension) + +Repository of AdGuard VPN Browser Extension. + +### [AdGuardVPNCLI](https://github.com/AdguardTeam/AdGuardVPNCLI) + +Repository of AdGuard VPN for Linux — a command‑line interface for managing VPN connection. The repo acts as a bug tracker. + +## DNS-based products + +### [AdGuardDNS](https://github.com/AdguardTeam/AdGuardDNS) + +Open-source repository that is also used for tracking bugs and issues related to AdGuard DNS service. Users can: + +- View and report DNS issues +- Suggest improvements + +### [AdGuardHome](https://github.com/AdguardTeam/AdGuardHome) + +Repository of AdGuard Home — free network-wide software for blocking ads and trackers via DNS. Users can: + +- Check and file bug reports or feature requests +- Review or contribute to code +- Download and install releases + +## Documentation and Knowledge bases + +Knowledge bases are aimed to help users better understand and use AdGuard. They describe each AdGuard product in detail: from feature overviews and problem-solving guides to advanced setting manuals and API documentations. In the repositories users can: + +- Suggest corrections or edits to knowledge base articles +- Propose new articles +- Test or run the local version + +### [KnowledgeBase](https://github.com/AdguardTeam/KnowledgeBase) + +Central documentation for AdGuard Ad Blocker and the technologies related to it. + +### [KnowledgeBaseDNS](https://github.com/AdguardTeam/KnowledgeBaseDNS) + +Detailed feature overview, troubleshooting guides and documentation for AdGuard DNS (both Public and Private), AdGuard Home, and everything related to them. + +### [KnowledgeBaseVPN](https://github.com/AdguardTeam/KnowledgeBaseVPN) + +Detailed feature overview and troubleshooting guides for AdGuard VPN. + +### [KnowledgeBaseMail](https://github.com/AdguardTeam/KnowledgeBaseMail) + +Detailed feature overview and troubleshooting guides of AdGuard Mail. + +## Core libraries + +### [CoreLibs](https://github.com/AdguardTeam/CoreLibs) + +AdGuard’s cross-platform core filtering engine. Used in Android, Windows, and Mac products. Users can: + +- Explore filtering logic and DNS handling +- Report bugs and suggest features via Issues + +### [DNSLibs](https://github.com/AdguardTeam/DNSLibs) + +A DNS library used by CoreLibs and AdGuardHome. Users can: + +- Review and contribute to low-level DNS implementation +- Suggest optimizations + +### [VPNLibs](https://github.com/AdguardTeam/VPNLibs) + +Shared codebase used in AdGuard VPN products across platforms for AdGuard VPN protocol implementation. Users can: + +- Contribute to VPN stack behavior +- Report or view performance issues and bugs + +## Core ad blocking and filtering technologies + +### [AdguardFilters](https://github.com/AdguardTeam/AdguardFilters) + +Contains AdGuard’s core filter lists. Users can: + +- View and download filter lists +- Create issues to report false positives or suggest new rules +- Monitor updates to filter logic + +### [AdGuardSDNSFilter](https://github.com/AdguardTeam/AdGuardSDNSFilter) + +Repository of AdGuard DNS filter — the main DNS-level blocking list used in AdGuard DNS and DNS filtering features. Users can: + +- Inspect the current rule set +- Propose changes or additions + +### [AGLint](https://github.com/AdguardTeam/AGLint) + +A linter for adblock filter list syntax. Users can: + +- Install AGLint to check their projects for rule issues +- Contribute to lint rules + +### [Scriptlets](https://github.com/AdguardTeam/Scriptlets) + +JavaScript helpers used in filtering rules. Users can: + +- Explore available scriptlets +- Submit pull requests for new scriptlets + +### [tsurlfilter](https://github.com/AdguardTeam/tsurlfilter) + +TypeScript content blocker library for browser extensions. Users can: + +- Explore how filtering logic is implemented +- Contribute fixes and features + +## There’s more + +Above, we listed 27 main public AdGuard repositories out of 96 total. If you want to go down the rabbit hole, you can [find the rest on the AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse). + +We’ll be waiting for your feedback there! Stay safe online and offline. diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/general/how-to-install.md b/i18n/bn/docusaurus-plugin-content-docs/current/general/how-to-install.md index 106a29529a8..4ba78d7a094 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/general/how-to-install.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/general/how-to-install.md @@ -1,6 +1,6 @@ --- title: How to install AdGuard -sidebar_position: 9 +sidebar_position: 10 --- Depending on which AdGuard app or browser extension you want to install, follow one of these links to find the relevant article: diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md index a7c205f7cd3..f59734c48fc 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md @@ -43,6 +43,14 @@ Zde můžete vybrat, jaký proxy server má AdGuard používat ke stahování ak ## Použít ovladač SockFilter -Tuto možnost zapněte, chcete-li používat ovladač SockFilter, který pomáhá blokovat reklamy a slídiče v aplikacích ve Windows 8 a novějších verzích. +Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. If this option is disabled, AdGuard will switch to the older WFP driver instead. -Pokud je tato možnost deaktivována, AdGuard místo toho přepne na starší ovladač WFP. +SockFilter was first introduced in v8.0 RC. It is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +Po dokončení testování a implementace má SockFilter potenciál přinést oproti jiným ovladačům několik výhod: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md index 4c3f123921d..e6d0381f9ea 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Z tohoto důvodu se viditelnost provozu založená na TDI stává stále nestabi AdGuard již považuje ovladač TDI za zastaralý a v rámci vývoje produktu se plánuje jeho úplné odstranění. +## Trvalé řešení + +From v8.0 RC, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows-8/settings/app-settings/network-settings/). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Dočasné řešení Určité změny v registru systému Windows mohou přimět prohlížeč, aby přestal používat AppContainer, což způsobí, že jeho procesy budou opět spuštěny v režimu bez sandboxu. Síťová služba přestane používat stack WSK a přejde na síťovou cestu, kterou může vidět ovladač TDI. AdGuard poté znovu získá schopnost filtrovat provoz prohlížeče. @@ -123,7 +131,3 @@ Měly by být aktivní následující zásady: Pokud jsou k dispozici, klikněte na _Znovu načíst zásadu_. Hotovo! - -## Trvalé řešení - -Plánujeme přidat podporu pro ovladač SockFilter v nadcházejících verzích. Problém vyřeší odstraněním konfliktů ve stacku WFP. [Další informace](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index fef3fc4951e..3352a7d5260 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -17,35 +17,47 @@ V tomto modulu můžete vybrat _Použít AdGuard jako HTTP proxy_, chcete-li pou Nakonec je zde část s nastavením proxy. Zde můžete určit, který proxy má AdGuard používat k aktualizaci filtrů, získávání nových verzí atd. -### SockFilter a další síťové ovladače +### Enable traffic filtering -V sekci _Síť_ můžete také povolit filtrování provozu a zvolit, který ovladač chcete použít: SockFilter, WFP nebo TDI. +Traffic filtering is the core mechanism that allows AdGuard to inspect and control the network traffic generated by applications on your computer. When it is enabled, AdGuard intercepts outgoing and incoming connections and checks them against its filtering rules. If a request matches a blocking rule, AdGuard can block it, modify it, or allow it depending on the configuration. In AdGuard for Windows, this interception is implemented through network drivers. -**WFP** (Windows Filtering Platform) je výkonný ovladač, u některých uživatelů však může představovat riziko pro stabilitu, například [občasné selhání systému (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792). +If HTTPS filtering is enabled, AdGuard performs a controlled local TLS interception: it decrypts the traffic using its local certificate, applies filtering rules, and then re-encrypts the traffic before sending it to the browser. The driver simply provides the system-level access needed for AdGuard to intercept these connections. -K dispozici je také ovladač **TDI**, ten je však zastaralý a v některých verzích prohlížeče Google Chrome může způsobovat [problémy s filtrováním](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [Existuje dočasné provizorní řešení](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), ale nejde o spolehlivé dlouhodobé řešení. +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. -**SockFilter** je _experimentální_, odlehčený síťový ovladač v režimu jádra, který pracuje na úrovni soketů (TCP/UDP). Místo toho, aby filtrování soketů kontrolovalo nebo upravovalo pakety při jejich průchodu celým síťovým zásobníkem systému Windows, zachycuje volání soketů (např. connect, send, receive, bind) na vyšší a stabilnější abstrakční úrovni. Díky tomu je ideální pro aplikace, které vyžadují monitorování nebo řízení síťové aktivity bez hloubkové analýzy paketů. +#### SockFilter -V současné době je SockFilter Right stále nestabilní a mohou se vyskytnout chyby. Po dokončení testování a implementace má SockFilter potenciál přinést oproti jiným ovladačům několik výhod: +**SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. -- **Pracuje na vyšší úrovni, na úrovni soketů**: SockFilter pracuje se soketovými operacemi namísto surových paketů, díky čemuž je méně složitý a stabilnější než nízkoúrovňové filtrování paketů v rámci WFP. -- **Žádné rušení ostatních síťových ovladačů**: Jelikož je umístěn nad filtry VPN, brány firewall a antivirového softwaru WFP, nedochází k problémům s pořadím filtrů ani ke konfliktům kompatibility, které jsou v zásobníku WFP běžné. -- **Výrazně snížené riziko BSOD souvisejících s NETIO**: SockFilter neběží uvnitř paketu NETIO, čímž se vyhýbá typickým situacím vedoucím k selhání, které jsou způsobeny nesprávným zpracováním vyrovnávacích pamětí, výsledků klasifikace nebo paměti paketů při voláních WFP. +SockFilter was first implemented in version 7.22.4, and it is still considered unstable — you may encounter bugs. Once fully tested and implemented, SockFilter has the potential to offer several advantages over other drivers: -Co se týče nevýhod, ovladač SockFilter vidí pouze operace na úrovni soketů a nezachytává provoz generovaný jinými ovladači jádra nebo komponentami, které obcházejí standardní rozhraní Winsock API. Z pohledu síťových mechanismů na nízké úrovni lze toto považovat za omezení, protože ovladač nemá přístup k surovým paketům ani nemůže kontrolovat provoz mimo sokety. Pro aplikaci blokující reklamy je však toto chování nejen přijatelné, ale přímo optimální. Veškerý relevantní provoz z prohlížečů a aplikací v uživatelském režimu prochází standardními sokety, a právě to potřebujeme mít pod kontrolou. Zároveň ignorování provozu na nízké úrovni ovladačů odstraňuje zbytečnou složitost, předchází problémům s kompatibilitou a zajišťuje stabilitu systému. +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. + +#### WFP + +**WFP** (Windows Filtering Platform) is a Microsoft networking framework built into Windows that allows software to filter and monitor network packets at different layers of the system networking stack. AdGuard uses WFP to safely hook into the network flow of applications and apply filtering rules before the traffic reaches the browser or the Internet. [More information](https://learn.microsoft.com/en-us/windows/win32/fwp/windows-filtering-platform-architecture-overview). + +While it is a powerful driver, it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) and lower Internet speed for some users. + +#### TDI + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. ### AdGuard VPN -Poslední část je věnována AdGuard VPN — ideálnímu nástroji, který poskytuje bezpečnost a anonymitu při každém procházení internetu. Můžete si ji stáhnout kliknutím na tlačítko _Stáhnout_ nebo přejít na webové stránky AdGuard VPN kliknutím na tlačítko _Domovská stránka_. +The last section is dedicated to AdGuard VPN — an ideal tool that provides security and anonymity each time you browse the Internet. You can download it by clicking the _Download_ button or go to the AdGuard VPN website by clicking the _Homepage_ button. -Jak funguje AdGuard VPN? Aniž bychom zacházeli do technických podrobností, můžeme říci, že VPN vytváří bezpečný šifrovaný tunel mezi počítačem nebo mobilním zařízením uživatele a vzdáleným serverem VPN. Tímto způsobem je zachována důvěrnost dat i anonymita uživatele, protože pozorovatel třetí strany vidí IP adresu serveru VPN, a nikoli skutečnou IP adresu uživatele. +How does AdGuard VPN work? Without going into technical details, we can say that VPN creates a secure encrypted tunnel between the user's computer or mobile device and a remote VPN server. In this way, data privacy is preserved, as well as the anonymity of the user, because a third-party observer sees the IP address of the VPN server and not the actual user's IP. -**Co dělá AdGuard VPN:** +**What AdGuard VPN does:** -- skrývá vaše skutečné místo pobytu a pomáhá vám zůstat v anonymitě -- změní vaši IP adresu a ochrání vaše data před sledováním -- šifruje váš provoz, aby byl nečitelný pro třetí strany -- umožňuje nastavit, kde se má VPN používat a kde ne (funkce výjimek) +- hides your real whereabouts and helps you stay anonymous +- changes your IP address to protect your data from tracking +- encrypts your traffic to make it unreadable to third parties +- lets you configure where to use VPN and where not to (exclusions feature) -Chcete-li získat více informací o AdGuard VPN, ponořte se do [Databáze znalostí AdGuard VPN](https://adguard-vpn.com/kb/). +To get more information about AdGuard VPN, dive into the [AdGuard VPN Knowledge Base](https://adguard-vpn.com/kb/). diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index 90b6442c62e..9d18a4575a2 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -44,12 +44,8 @@ Než začnete ručně psát vlastní pravidla, přečtěte si našeho podrobnéh Mnoho webových stránek shromažďuje informace o svých návštěvnících, například jejich IP adresy, informace o nainstalovaném prohlížeči a operačním systému, rozlišení obrazovky, a dokonce i o tom, na jakou stránku uživatel přišel nebo z jaké stránky byl přesměrován. Některé webové stránky používají soubory cookies k označení prohlížeče a uložení vašich osobních nastavení, uživatelských preferencí nebo k vašemu “rozpoznání“ při příští návštěvě. To jim umožní vás při příští návštěvě “rozpoznat“. Ochrana před sledováním chrání vaše osobní údaje před takovými systémy shromažďujícími data a statistiky. -![Tracking protection levels \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection1.png) - Nastavení _ochrany před sledováním_ můžete upravit podle potřeby. Můžete například zabránit webovým stránkám v přijímání vyhledávacích dotazů, které jste použili k jejich vyhledání na internetu, automaticky mazat soubory cookies třetích stran a vlastní a deaktivovat sdílení polohy ve svém prohlížeči, abyste zabránili sledování vaší polohy. -![Tracking protection custom features \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection2.png) - Chcete-li se dozvědět vše o _Ochraně před sledováním_ a mnoha možnostech, přečtěte si [tento článek](/general/stealth-mode). ### Bezpečné prohlížení diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md index a198fd5e7a5..43cc8bf072b 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Z tohoto důvodu se viditelnost provozu založená na TDI stává stále nestabi AdGuard již považuje ovladač TDI za zastaralý a v rámci vývoje produktu se plánuje jeho úplné odstranění. +## Trvalé řešení + +From v7.22.4, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows/features/network/#sockfilter-and-other-network-drivers). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Dočasné řešení Určité změny v registru systému Windows mohou přimět prohlížeč, aby přestal používat AppContainer, což způsobí, že jeho procesy budou opět spuštěny v režimu bez sandboxu. Síťová služba přestane používat stack WSK a přejde na síťovou cestu, kterou může vidět ovladač TDI. AdGuard poté znovu získá schopnost filtrovat provoz prohlížeče. @@ -136,7 +144,3 @@ Měly by být aktivní následující zásady: Pokud jsou k dispozici, klikněte na _Znovu načíst zásadu_. Hotovo! - -## Trvalé řešení - -Plánujeme přidat podporu pro ovladač SockFilter v nadcházejících verzích. Problém vyřeší odstraněním konfliktů ve stacku WFP. [Další informace](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/general/github-repos.md b/i18n/cs/docusaurus-plugin-content-docs/current/general/github-repos.md new file mode 100644 index 00000000000..dfb164c44bc --- /dev/null +++ b/i18n/cs/docusaurus-plugin-content-docs/current/general/github-repos.md @@ -0,0 +1,238 @@ +--- +title: AdGuard’s GitHub repositories +sidebar_position: 9 +--- + +At AdGuard, our goal is to make the Internet safer, more comfortable, and more transparent. This commitment is reflected not only in our product features and strict privacy policies, but also in the fact that we keep our work as open as possible. That includes actively interacting with our community. + +This is why [all of our products have public repositories](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse) — online spaces where anybody can see what we are working on, report issues directly to AdGuard developers, and even contribute to our open-source projects. The repositories cover our ad-blocking apps, filters, browser extensions, DNS solutions, VPN tools, developer utilities, and more. There are different platforms that offer such functionality, but the most popular one by far is GitHub, and all AdGuard projects are stored there. + +This article lists the most important repositories by category, summarizes the purpose of each one, and gives a simple breakdown of what users can do there. + +:::tip + +Pro tip: Creating an issue on GitHub is the most effective way to bring the attention of AdGuard developers to a problem. Just make sure to check that a similar issue doesn’t already exist and describe the problem in a comprehensive but concise way. If it does exist, you can upvote it. + +::: + +## What is Github and its repositories + +Very simply put, you can think of GitHub as sort of Google Docs for code, where multiple people can work on the same project, track changes, and see who made which updates. It provides a central, cloud-based place to store your code so it’s accessible from anywhere. It also has teamwork tools for reviewing changes, fixing issues, and merging everyone’s work smoothly. + +GitHub is widely used for open-source projects, letting anyone view the code, suggest improvements, and contribute. + +A repository (often called “repo” for short) is the most basic element of GitHub. It’s a place where you can store your code, your files, and each file’s revision history. Repositories can have multiple collaborators and can be either public or private. + +## What can you do in AdGuard’s repositories + +You can find links to key repositories below in this article or visit the [general AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all) for a full list. In most repos, you can: + +- **View README file** on the main page: it gives you an introduction to the product and its repo + ![README file \*border](https://cdn.adtidy.org/content/blog/github-repos/see-readme.png) + +- **Check existing bug reports or feature requests**, comment and upvote + ![Check issues \*border](https://cdn.adtidy.org/content/blog/github-repos/check-issues.png) + +- **Create issues** to report bugs or request features + ![Create issues \*border](https://cdn.adtidy.org/content/blog/github-repos/create-issue.png) + +- **Check releases** for different versions and their changelogs (and install an older version if needed) + ![Check releases \*border](https://cdn.adtidy.org/content/blog/github-repos/check-releases.png) + +- **Install any older or beta version** if needed + ![Download builds \*border](https://cdn.adtidy.org/content/blog/github-repos/download-releases.png) + +:::note + +If you are new to GitHub, you’ll need to create a GitHub account in order to create new issues and comment on the existing ones. + +::: + +In open-source repos advanced users can also: + +- **Browse code** to understand product logic, what technologies are used and how they are implemented +- **Fork and contribute** via pull requests + +Whether you’re a casual user, technical expert, or a developer, AdGuard welcomes all community participation across its GitHub repos. + +## Legal documents + +### [LegalDocs](https://github.com/AdguardTeam/LegalDocs) + +As part of our commitment to transparency, we host all legal documents — such as End-User License Agreements, Privacy Policies, and Terms and Conditions — on GitHub. Our _LegalDocs_ repo lets anyone check the full history of changes to these documents. + +## AdGuard Ad Blocker products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdguardForAndroid](https://github.com/AdguardTeam/AdguardForAndroid) + +Repository of AdGuard for Android — an app that provides system-wide ad blocking. + +### [AdguardForiOS](https://github.com/AdguardTeam/AdguardForiOS) + +Repository of AdGuard for iOS — Safari content blocker with DNS and custom filters. Users can also check open-source code. + +### [AdguardForWindows](https://github.com/AdguardTeam/AdguardForWindows) + +Repository of AdGuard for Windows. Non-open-source; GitHub used as an open bug tracker. + +### [AdguardForMac](https://github.com/AdguardTeam/AdguardForMac) + +Repository of AdGuard for Mac — macOS standalone content blocker. Bug tracker only. + +### [AdguardBrowserExtension](https://github.com/AdguardTeam/AdguardBrowserExtension) + +Repository of AdGuard Browser Extension — extension that provides ad blocking with enhanced privacy for Chrome, Firefox, Opera, Edge. + +### [AdguardForSafari](https://github.com/AdguardTeam/AdGuardForSafari) + +Repository of AdGuard for Safari — Safari ad blocking extension for Mac. Users can also check open-sourced code. + +### [AdGuardCLI](https://github.com/AdguardTeam/AdGuardCLI) + +Repository of AdGuard for Linux — a command‑line interface for managing ad blocking. + +## AdGuard VPN products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdGuardVPNForiOS](https://github.com/AdguardTeam/AdGuardVPNForiOS) + +Repository of AdGuard VPN for iOS. Serves as an open bug tracker. + +### [AdGuardVPNForAndroid](https://github.com/AdguardTeam/AdGuardVPNForAndroid) + +Repository of AdGuard VPN for Android. Serves as an open bug tracker. + +### [AdGuardVPNForWindows](https://github.com/AdguardTeam/AdGuardVPNForWindows) + +Repository of AdGuard VPN for Windows. Serves as an open bug tracker. + +### [AdGuardVPNForMac](https://github.com/AdguardTeam/AdGuardVPNForMac) + +Repository of AdGuard VPN for Mac — app designed for macOS. + +### [AdGuardVPNExtension](https://github.com/AdguardTeam/AdGuardVPNExtension) + +Repository of AdGuard VPN Browser Extension. + +### [AdGuardVPNCLI](https://github.com/AdguardTeam/AdGuardVPNCLI) + +Repository of AdGuard VPN for Linux — a command‑line interface for managing VPN connection. The repo acts as a bug tracker. + +## DNS-based products + +### [AdGuardDNS](https://github.com/AdguardTeam/AdGuardDNS) + +Open-source repository that is also used for tracking bugs and issues related to AdGuard DNS service. Users can: + +- View and report DNS issues +- Suggest improvements + +### [AdGuardHome](https://github.com/AdguardTeam/AdGuardHome) + +Repository of AdGuard Home — free network-wide software for blocking ads and trackers via DNS. Users can: + +- Check and file bug reports or feature requests +- Review or contribute to code +- Download and install releases + +## Documentation and Knowledge bases + +Knowledge bases are aimed to help users better understand and use AdGuard. They describe each AdGuard product in detail: from feature overviews and problem-solving guides to advanced setting manuals and API documentations. In the repositories users can: + +- Suggest corrections or edits to knowledge base articles +- Propose new articles +- Test or run the local version + +### [KnowledgeBase](https://github.com/AdguardTeam/KnowledgeBase) + +Central documentation for AdGuard Ad Blocker and the technologies related to it. + +### [KnowledgeBaseDNS](https://github.com/AdguardTeam/KnowledgeBaseDNS) + +Detailed feature overview, troubleshooting guides and documentation for AdGuard DNS (both Public and Private), AdGuard Home, and everything related to them. + +### [KnowledgeBaseVPN](https://github.com/AdguardTeam/KnowledgeBaseVPN) + +Detailed feature overview and troubleshooting guides for AdGuard VPN. + +### [KnowledgeBaseMail](https://github.com/AdguardTeam/KnowledgeBaseMail) + +Detailed feature overview and troubleshooting guides of AdGuard Mail. + +## Core libraries + +### [CoreLibs](https://github.com/AdguardTeam/CoreLibs) + +AdGuard’s cross-platform core filtering engine. Used in Android, Windows, and Mac products. Users can: + +- Explore filtering logic and DNS handling +- Report bugs and suggest features via Issues + +### [DNSLibs](https://github.com/AdguardTeam/DNSLibs) + +A DNS library used by CoreLibs and AdGuardHome. Users can: + +- Review and contribute to low-level DNS implementation +- Suggest optimizations + +### [VPNLibs](https://github.com/AdguardTeam/VPNLibs) + +Shared codebase used in AdGuard VPN products across platforms for AdGuard VPN protocol implementation. Users can: + +- Contribute to VPN stack behavior +- Report or view performance issues and bugs + +## Core ad blocking and filtering technologies + +### [AdguardFilters](https://github.com/AdguardTeam/AdguardFilters) + +Contains AdGuard’s core filter lists. Users can: + +- View and download filter lists +- Create issues to report false positives or suggest new rules +- Monitor updates to filter logic + +### [AdGuardSDNSFilter](https://github.com/AdguardTeam/AdGuardSDNSFilter) + +Repository of AdGuard DNS filter — the main DNS-level blocking list used in AdGuard DNS and DNS filtering features. Users can: + +- Inspect the current rule set +- Propose changes or additions + +### [AGLint](https://github.com/AdguardTeam/AGLint) + +A linter for adblock filter list syntax. Users can: + +- Install AGLint to check their projects for rule issues +- Contribute to lint rules + +### [Scriptlets](https://github.com/AdguardTeam/Scriptlets) + +JavaScript helpers used in filtering rules. Users can: + +- Explore available scriptlets +- Submit pull requests for new scriptlets + +### [tsurlfilter](https://github.com/AdguardTeam/tsurlfilter) + +TypeScript content blocker library for browser extensions. Users can: + +- Explore how filtering logic is implemented +- Contribute fixes and features + +## There’s more + +Above, we listed 27 main public AdGuard repositories out of 96 total. If you want to go down the rabbit hole, you can [find the rest on the AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse). + +We’ll be waiting for your feedback there! Stay safe online and offline. diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/general/how-to-install.md b/i18n/cs/docusaurus-plugin-content-docs/current/general/how-to-install.md index b1f8617e0bd..d2d3c51ec06 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/general/how-to-install.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/general/how-to-install.md @@ -1,6 +1,6 @@ --- title: Jak nainstalovat AdGuard -sidebar_position: 9 +sidebar_position: 10 --- Podle toho, kterou aplikaci AdGuard nebo rozšíření prohlížeče chcete nainstalovat, vyhledejte příslušný článek pomocí jednoho z těchto odkazů: diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md index 3953f47d26f..05642d350b0 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md @@ -43,6 +43,14 @@ Here you can choose which proxy AdGuard should use to download filter updates or ## Use SockFilter driver -Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. +Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. If this option is disabled, AdGuard will switch to the older WFP driver instead. -If this option is disabled, AdGuard will switch to the older WFP driver instead. +SockFilter was first introduced in v8.0 RC. It is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md index 251e49cf286..1ab588bb16c 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Because of this, TDI-based traffic visibility becomes increasingly unstable. In AdGuard already treats the TDI driver as deprecated, and its complete removal is planned as the product evolves. +## Permanent solution + +From v8.0 RC, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows-8/settings/app-settings/network-settings/). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Temporary solution Certain Windows registry changes can force the browser to stop using AppContainer, causing its processes to run in a non-sandboxed mode again. Network Service stops using the WSK stack and falls back to a network path that the TDI driver can see. AdGuard then regains the ability to filter browser traffic. @@ -123,7 +131,3 @@ You should see the following policies active: If available, click _Reload policies_. Done! - -## Permanent solution - -We’re planning to add support for the SockFilter driver in the upcoming versions. It will fix the issue by solving conflicts in the WFP stack. [More information](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index 5945618ea9c..f8074e9cfa1 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -17,23 +17,35 @@ In this module you can select the checkbox _Use AdGuard as an HTTP proxy_ to use At last, there is a section with proxy settings. There you can specify which proxy server AdGuard should use to update filters, get new versions, and so on. -### SockFilter and other network drivers +### Enable traffic filtering -In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. +Traffic filtering is the core mechanism that allows AdGuard to inspect and control the network traffic generated by applications on your computer. When it is enabled, AdGuard intercepts outgoing and incoming connections and checks them against its filtering rules. If a request matches a blocking rule, AdGuard can block it, modify it, or allow it depending on the configuration. In AdGuard for Windows, this interception is implemented through network drivers. -**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. +If HTTPS filtering is enabled, AdGuard performs a controlled local TLS interception: it decrypts the traffic using its local certificate, applies filtering rules, and then re-encrypts the traffic before sending it to the browser. The driver simply provides the system-level access needed for AdGuard to intercept these connections. -The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +#### SockFilter **SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. -Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: +SockFilter was first implemented in version 7.22.4, and it is still considered unstable — you may encounter bugs. Once fully tested and implemented, SockFilter has the potential to offer several advantages over other drivers: -- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. - **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. -- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. -When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. +#### WFP + +**WFP** (Windows Filtering Platform) is a Microsoft networking framework built into Windows that allows software to filter and monitor network packets at different layers of the system networking stack. AdGuard uses WFP to safely hook into the network flow of applications and apply filtering rules before the traffic reaches the browser or the Internet. [More information](https://learn.microsoft.com/en-us/windows/win32/fwp/windows-filtering-platform-architecture-overview). + +While it is a powerful driver, it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) and lower Internet speed for some users. + +#### TDI + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. ### AdGuard VPN diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index ab90a964b9f..5699b31b033 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -44,12 +44,8 @@ Before you start manually writing your own rules read our detailed [syntax guide Many websites gather information about their visitors, such as their IP addresses, browser and operating system details, screen resolution, and the webpage from which the user came or was redirected. Some websites use cookies to mark and identify your browser, save your personal settings and preferences. This allows them to “recognize” you on your next visit. Tracking protection safeguards your personal information from these data- and statistics-gathering systems. -![Tracking protection levels \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection1.png) - You can adjust the _Tracking Protection_ settings as needed. For example, you can prevent websites from receiving the search request that you used to find them on the Internet, automatically delete third- and first-party cookies, and disable location sharing in your browser, to prevent tracking of your whereabouts. -![Tracking protection custom features \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection2.png) - To learn everything about _Tracking protection_ and its many options, [read this article](/general/stealth-mode). ### Browsing security diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md index 62370bf3eb1..bec08d0c665 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Because of this, TDI-based traffic visibility becomes increasingly unstable. In AdGuard already treats the TDI driver as deprecated, and its complete removal is planned as the product evolves. +## Permanent solution + +From v7.22.4, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows/features/network/#sockfilter-and-other-network-drivers). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Temporary solution Certain Windows registry changes can force the browser to stop using AppContainer, causing its processes to run in a non-sandboxed mode again. Network Service stops using the WSK stack and falls back to a network path that the TDI driver can see. AdGuard then regains the ability to filter browser traffic. @@ -136,7 +144,3 @@ You should see the following policies active: If available, click _Reload policies_. Done! - -## Permanent solution - -We’re planning to add support for the SockFilter driver in the upcoming versions. It will fix the issue by solving conflicts in the WFP stack. [More information](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/da/docusaurus-plugin-content-docs/current/general/github-repos.md b/i18n/da/docusaurus-plugin-content-docs/current/general/github-repos.md new file mode 100644 index 00000000000..dfb164c44bc --- /dev/null +++ b/i18n/da/docusaurus-plugin-content-docs/current/general/github-repos.md @@ -0,0 +1,238 @@ +--- +title: AdGuard’s GitHub repositories +sidebar_position: 9 +--- + +At AdGuard, our goal is to make the Internet safer, more comfortable, and more transparent. This commitment is reflected not only in our product features and strict privacy policies, but also in the fact that we keep our work as open as possible. That includes actively interacting with our community. + +This is why [all of our products have public repositories](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse) — online spaces where anybody can see what we are working on, report issues directly to AdGuard developers, and even contribute to our open-source projects. The repositories cover our ad-blocking apps, filters, browser extensions, DNS solutions, VPN tools, developer utilities, and more. There are different platforms that offer such functionality, but the most popular one by far is GitHub, and all AdGuard projects are stored there. + +This article lists the most important repositories by category, summarizes the purpose of each one, and gives a simple breakdown of what users can do there. + +:::tip + +Pro tip: Creating an issue on GitHub is the most effective way to bring the attention of AdGuard developers to a problem. Just make sure to check that a similar issue doesn’t already exist and describe the problem in a comprehensive but concise way. If it does exist, you can upvote it. + +::: + +## What is Github and its repositories + +Very simply put, you can think of GitHub as sort of Google Docs for code, where multiple people can work on the same project, track changes, and see who made which updates. It provides a central, cloud-based place to store your code so it’s accessible from anywhere. It also has teamwork tools for reviewing changes, fixing issues, and merging everyone’s work smoothly. + +GitHub is widely used for open-source projects, letting anyone view the code, suggest improvements, and contribute. + +A repository (often called “repo” for short) is the most basic element of GitHub. It’s a place where you can store your code, your files, and each file’s revision history. Repositories can have multiple collaborators and can be either public or private. + +## What can you do in AdGuard’s repositories + +You can find links to key repositories below in this article or visit the [general AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all) for a full list. In most repos, you can: + +- **View README file** on the main page: it gives you an introduction to the product and its repo + ![README file \*border](https://cdn.adtidy.org/content/blog/github-repos/see-readme.png) + +- **Check existing bug reports or feature requests**, comment and upvote + ![Check issues \*border](https://cdn.adtidy.org/content/blog/github-repos/check-issues.png) + +- **Create issues** to report bugs or request features + ![Create issues \*border](https://cdn.adtidy.org/content/blog/github-repos/create-issue.png) + +- **Check releases** for different versions and their changelogs (and install an older version if needed) + ![Check releases \*border](https://cdn.adtidy.org/content/blog/github-repos/check-releases.png) + +- **Install any older or beta version** if needed + ![Download builds \*border](https://cdn.adtidy.org/content/blog/github-repos/download-releases.png) + +:::note + +If you are new to GitHub, you’ll need to create a GitHub account in order to create new issues and comment on the existing ones. + +::: + +In open-source repos advanced users can also: + +- **Browse code** to understand product logic, what technologies are used and how they are implemented +- **Fork and contribute** via pull requests + +Whether you’re a casual user, technical expert, or a developer, AdGuard welcomes all community participation across its GitHub repos. + +## Legal documents + +### [LegalDocs](https://github.com/AdguardTeam/LegalDocs) + +As part of our commitment to transparency, we host all legal documents — such as End-User License Agreements, Privacy Policies, and Terms and Conditions — on GitHub. Our _LegalDocs_ repo lets anyone check the full history of changes to these documents. + +## AdGuard Ad Blocker products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdguardForAndroid](https://github.com/AdguardTeam/AdguardForAndroid) + +Repository of AdGuard for Android — an app that provides system-wide ad blocking. + +### [AdguardForiOS](https://github.com/AdguardTeam/AdguardForiOS) + +Repository of AdGuard for iOS — Safari content blocker with DNS and custom filters. Users can also check open-source code. + +### [AdguardForWindows](https://github.com/AdguardTeam/AdguardForWindows) + +Repository of AdGuard for Windows. Non-open-source; GitHub used as an open bug tracker. + +### [AdguardForMac](https://github.com/AdguardTeam/AdguardForMac) + +Repository of AdGuard for Mac — macOS standalone content blocker. Bug tracker only. + +### [AdguardBrowserExtension](https://github.com/AdguardTeam/AdguardBrowserExtension) + +Repository of AdGuard Browser Extension — extension that provides ad blocking with enhanced privacy for Chrome, Firefox, Opera, Edge. + +### [AdguardForSafari](https://github.com/AdguardTeam/AdGuardForSafari) + +Repository of AdGuard for Safari — Safari ad blocking extension for Mac. Users can also check open-sourced code. + +### [AdGuardCLI](https://github.com/AdguardTeam/AdGuardCLI) + +Repository of AdGuard for Linux — a command‑line interface for managing ad blocking. + +## AdGuard VPN products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdGuardVPNForiOS](https://github.com/AdguardTeam/AdGuardVPNForiOS) + +Repository of AdGuard VPN for iOS. Serves as an open bug tracker. + +### [AdGuardVPNForAndroid](https://github.com/AdguardTeam/AdGuardVPNForAndroid) + +Repository of AdGuard VPN for Android. Serves as an open bug tracker. + +### [AdGuardVPNForWindows](https://github.com/AdguardTeam/AdGuardVPNForWindows) + +Repository of AdGuard VPN for Windows. Serves as an open bug tracker. + +### [AdGuardVPNForMac](https://github.com/AdguardTeam/AdGuardVPNForMac) + +Repository of AdGuard VPN for Mac — app designed for macOS. + +### [AdGuardVPNExtension](https://github.com/AdguardTeam/AdGuardVPNExtension) + +Repository of AdGuard VPN Browser Extension. + +### [AdGuardVPNCLI](https://github.com/AdguardTeam/AdGuardVPNCLI) + +Repository of AdGuard VPN for Linux — a command‑line interface for managing VPN connection. The repo acts as a bug tracker. + +## DNS-based products + +### [AdGuardDNS](https://github.com/AdguardTeam/AdGuardDNS) + +Open-source repository that is also used for tracking bugs and issues related to AdGuard DNS service. Users can: + +- View and report DNS issues +- Suggest improvements + +### [AdGuardHome](https://github.com/AdguardTeam/AdGuardHome) + +Repository of AdGuard Home — free network-wide software for blocking ads and trackers via DNS. Users can: + +- Check and file bug reports or feature requests +- Review or contribute to code +- Download and install releases + +## Documentation and Knowledge bases + +Knowledge bases are aimed to help users better understand and use AdGuard. They describe each AdGuard product in detail: from feature overviews and problem-solving guides to advanced setting manuals and API documentations. In the repositories users can: + +- Suggest corrections or edits to knowledge base articles +- Propose new articles +- Test or run the local version + +### [KnowledgeBase](https://github.com/AdguardTeam/KnowledgeBase) + +Central documentation for AdGuard Ad Blocker and the technologies related to it. + +### [KnowledgeBaseDNS](https://github.com/AdguardTeam/KnowledgeBaseDNS) + +Detailed feature overview, troubleshooting guides and documentation for AdGuard DNS (both Public and Private), AdGuard Home, and everything related to them. + +### [KnowledgeBaseVPN](https://github.com/AdguardTeam/KnowledgeBaseVPN) + +Detailed feature overview and troubleshooting guides for AdGuard VPN. + +### [KnowledgeBaseMail](https://github.com/AdguardTeam/KnowledgeBaseMail) + +Detailed feature overview and troubleshooting guides of AdGuard Mail. + +## Core libraries + +### [CoreLibs](https://github.com/AdguardTeam/CoreLibs) + +AdGuard’s cross-platform core filtering engine. Used in Android, Windows, and Mac products. Users can: + +- Explore filtering logic and DNS handling +- Report bugs and suggest features via Issues + +### [DNSLibs](https://github.com/AdguardTeam/DNSLibs) + +A DNS library used by CoreLibs and AdGuardHome. Users can: + +- Review and contribute to low-level DNS implementation +- Suggest optimizations + +### [VPNLibs](https://github.com/AdguardTeam/VPNLibs) + +Shared codebase used in AdGuard VPN products across platforms for AdGuard VPN protocol implementation. Users can: + +- Contribute to VPN stack behavior +- Report or view performance issues and bugs + +## Core ad blocking and filtering technologies + +### [AdguardFilters](https://github.com/AdguardTeam/AdguardFilters) + +Contains AdGuard’s core filter lists. Users can: + +- View and download filter lists +- Create issues to report false positives or suggest new rules +- Monitor updates to filter logic + +### [AdGuardSDNSFilter](https://github.com/AdguardTeam/AdGuardSDNSFilter) + +Repository of AdGuard DNS filter — the main DNS-level blocking list used in AdGuard DNS and DNS filtering features. Users can: + +- Inspect the current rule set +- Propose changes or additions + +### [AGLint](https://github.com/AdguardTeam/AGLint) + +A linter for adblock filter list syntax. Users can: + +- Install AGLint to check their projects for rule issues +- Contribute to lint rules + +### [Scriptlets](https://github.com/AdguardTeam/Scriptlets) + +JavaScript helpers used in filtering rules. Users can: + +- Explore available scriptlets +- Submit pull requests for new scriptlets + +### [tsurlfilter](https://github.com/AdguardTeam/tsurlfilter) + +TypeScript content blocker library for browser extensions. Users can: + +- Explore how filtering logic is implemented +- Contribute fixes and features + +## There’s more + +Above, we listed 27 main public AdGuard repositories out of 96 total. If you want to go down the rabbit hole, you can [find the rest on the AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse). + +We’ll be waiting for your feedback there! Stay safe online and offline. diff --git a/i18n/da/docusaurus-plugin-content-docs/current/general/how-to-install.md b/i18n/da/docusaurus-plugin-content-docs/current/general/how-to-install.md index 106a29529a8..4ba78d7a094 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/general/how-to-install.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/general/how-to-install.md @@ -1,6 +1,6 @@ --- title: How to install AdGuard -sidebar_position: 9 +sidebar_position: 10 --- Depending on which AdGuard app or browser extension you want to install, follow one of these links to find the relevant article: diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/adguard-browser-extension.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/adguard-browser-extension.md index 819e673435f..9c42731d3c9 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/adguard-browser-extension.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/adguard-browser-extension.md @@ -11,7 +11,7 @@ In diesem Artikel geht es um die AdGuard Browsereweiterung, die nur Ihren Browse - [Funktionen](/adguard-browser-extension/features) - Main features and settings available in AdGuard Browser Extension + Die wichtigsten Funktionen und Einstellungen der AdGuard Browsererweiterung - [Verfügbarkeit](/adguard-browser-extension/availability) @@ -23,7 +23,7 @@ In diesem Artikel geht es um die AdGuard Browsereweiterung, die nur Ihren Browse - [Kompatibilität mit der eigenständigen App](adguard-browser-extension/compatibility) - Compatibility of AdGuard Browser Extension with the AdGuard desktop apps + Kompatibilität der AdGuard Browsererweiterung mit den AdGuard-Desktop-Apps - [AdGuard Browsererweiterung für Chrome MV3](/adguard-browser-extension/mv3-version/) diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/features.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/features.md index c772527f1ae..40e7f776b2b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/features.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/features.md @@ -9,18 +9,18 @@ In diesem Artikel geht es um die AdGuard Browsereweiterung, die nur Ihren Browse ::: -- [Main menu](/adguard-browser-extension/features/main-menu.md) +- [Hauptmenü](/adguard-browser-extension/features/main-menu.md) - The main popup from which you can access settings, filtering log and statistics, and report problems + Das Pop-up, von dem aus Sie auf Einstellungen, das Filterungsprotokoll und Statistiken zugreifen und Probleme melden können -- [Filters](/adguard-browser-extension/features/filters.md) +- [Filter](/adguard-browser-extension/features/filters.md) Filter und Benutzerregeln zur Feinabstimmung der Werbeblockierung -- [Tracking protection (Stealth Mode)](/adguard-browser-extension/features/stealth-mode.md) +- [Tracking-Schutz (Privatsphäre)](/adguard-browser-extension/features/stealth-mode.md) - Settings to block cookies, UTM tags, and online analytics that collect user information + Einstellungen zum Blockieren von Cookies, UTM-Tags und Analyse-Tools, die Nutzerdaten sammeln -- [Other features and options](/adguard-browser-extension/features/other-features.md) +- [Weitere Funktionen und Optionen](/adguard-browser-extension/features/other-features.md) - General and additional settings, links to privacy documents and GitHub repository + Allgemeine und zusätzliche Einstellungen, Links zu Datenschutzdokumenten und zum GitHub-Repository diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md index d1e6bdd8101..15cabb3b1e3 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md @@ -1,13 +1,13 @@ --- -title: Ad blocking issues on search websites in Opera +title: Probleme mit der Werbeblockierung auf Suchmaschinen in Opera sidebar_position: 3 --- If AdGuard Browser Extension fails to block ads on search websites in Opera, either automatically or manually, it means that the extension does not have permission to access search page results. -To grant the required permission: +Um die erforderliche Berechtigung zu erteilen: -![Allow access to search page results](https://cdn.adtidy.org/content/kb/ad_blocker/browser_extension/allow-access.png) +![Zugriff auf Suchergebnisseiten zulassen](https://cdn.adtidy.org/content/kb/ad_blocker/browser_extension/allow-access.png) 1. Click the cube icon next to the address bar → _Manage extensions..._. 2. Find AdGuard AdBlocker in the list of installed extensions and tick the box next to _Allow access to search page results_. diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/solving-problems.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/solving-problems.md index fa905bcd89b..c4ab1716ebb 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/solving-problems.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/solving-problems.md @@ -3,7 +3,7 @@ title: Probleme lösen sidebar_position: 1 --- -Here are some guides you may need to solve problems with AdGuard Browser Extension. +Hier finden Sie einige Anleitungen, die Sie benötigen, um Probleme mit der AdGuard Browsererweiterung zu lösen. - [So exportieren Sie Protokolle von der Hintergrundseite](/adguard-browser-extension/solving-problems/logs.md) - [So erfolgt die Fehlersuche bei Regeln in AdGuard für Chrome MV3](/adguard-browser-extension/solving-problems/debug-rules.md) diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md index 1fa55da43bc..ecacdc86bf3 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md @@ -77,4 +77,4 @@ Hier sind die aktiven Funktionen der vorkonfigurierten Ebenen: k. _X-Client-Data-Header entfernen_. Diese Funktion verhindert, dass Google Chrome seine Versions- und Änderungsinformationen an Google-Domains (einschließlich DoubleClick und Google Analytics) sendet -You can tweak individual settings in _Tracking protection_ to create a custom configuration. Each setting has a description to help you understand its purpose. [Read more about various _Tracking protection_ settings](/general/stealth-mode) and use them cautiously, as some may interfere with the functionality of websites and browser extensions. +You can tweak individual settings in _Tracking protection_ to create a custom configuration. Each setting has a description to help you understand its purpose. [Lesen Sie mehr darüber, was die verschiedenen _Tracking-Schutz_-Einstellungen bewirken](/general/stealth-mode) und verwenden Sie sie mit Bedacht, da einige die Funktionalität von Websites und Browsererweiterungen beeinträchtigen können. diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md index b8a2c5a9e2f..23282c7641e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md @@ -31,7 +31,7 @@ Die _Protokollierungsebene_ legt fest, welche Daten über die Funktion der App p ![Erweitert \*mobile_border](https://cdn.adtidy.org/blog/new/vshfnadvanced.png) -Der Abschnitt _Low-Level-Einstellungen_ ist für erfahrene Benutzer:innen gedacht. [Read more about low-level settings](/adguard-for-android/features/low-level-settings/) +Der Abschnitt _Low-Level-Einstellungen_ ist für erfahrene Benutzer:innen gedacht. [Weitere Informationen über Low-Level-Einstellungen](/adguard-for-android/solving-problems/low-level-settings/) ![Low-Level-Einstellungen \*mobile_border](https://cdn.adtidy.org/blog/new/n9ztplow_level.png) @@ -83,7 +83,7 @@ Disable AMP is a userscript that disables [Accelerated mobile pages](https://en. #### HTTPS-Filterung -To block ads and trackers on most websites and in most apps, AdGuard needs to filter their HTTPS traffic. [Read more about HTTPS filtering](/general/https-filtering/what-is-https-filtering) +To block ads and trackers on most websites and in most apps, AdGuard needs to filter their HTTPS traffic. [Lesen Sie mehr über HTTPS-Filterung](/general/https-filtering/what-is-https-filtering) ##### Security certificates @@ -112,7 +112,7 @@ By default, we also do not filter websites with Extended Validation (EV) certifi #### Proxy -You can set up AdGuard to route all your device's traffic through your proxy server. [How to set up an outbound proxy](/adguard-for-android/solving-problems/outbound-proxy) +You can set up AdGuard to route all your device's traffic through your proxy server. [So richten Sie einen Outbound-Proxy ein](/adguard-for-android/solving-problems/outbound-proxy) In this section, you can also set up a third-party VPN to work with AdGuard, if your VPN provider allows it. @@ -126,7 +126,7 @@ This section allows you to select the traffic filtering method. :::note -The _Local VPN_ mode doesn't allow AdGuard to be used simultaneously with other VPNs. To use another VPN with AdGuard, you need to reconfigure it to work in proxy mode and set up an outbound proxy in AdGuard. For AdGuard VPN, this is done automatically with the help of the [_Integrated mode_](/adguard-for-android/features/integration-with-vpn). +The _Local VPN_ mode doesn't allow AdGuard to be used simultaneously with other VPNs. To use another VPN with AdGuard, you need to reconfigure it to work in proxy mode and set up an outbound proxy in AdGuard. Bei AdGuard VPN geschieht dies automatisch mit Hilfe des [_Integrierten Modus_](/adguard-for-android/features/integration-with-vpn). ::: @@ -161,12 +161,12 @@ Use this section if you have any questions or suggestions regarding AdGuard for If you notice a missed ad, please report it via _Report incorrect blocking_. -For unexpected app behavior, select _Report a bug_. If possible, describe your problem in detail and add app logs. [How to describe an issue](/guides/report-bugs/#how-to-describe-a-problem) +For unexpected app behavior, select _Report a bug_. If possible, describe your problem in detail and add app logs. [So beschreiben Sie ein Problem](/guides/report-bugs/#how-to-describe-a-problem) For your suggestions, use _Request a feature_. :::note -GitHub is an alternative way to report bugs and suggest new features. [Instructions and repository links](/guides/report-bugs/#adguard-for-android) +GitHub is an alternative way to report bugs and suggest new features. [Anleitungen und Repository-Links](/guides/report-bugs/#adguard-for-android) ::: diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-ios/features/features.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-ios/features/features.md index 5b4c576aa2b..88e00a6a378 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-ios/features/features.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-ios/features/features.md @@ -35,7 +35,7 @@ Dieser Artikel behandelt AdGuard für iOS, einem multifunktionalen Werbeblocker, - [Weitere Funktionen](/adguard-for-ios/features/other-features.md) - General settings: theme, settings and statistics reset, auto-update, inverting the allowlist, and advanced mode. + Allgemeine Einstellungen: Design, Zurücksetzen von Einstellungen und Statistiken, Auto-Updates, Invertieren der Zulassungsliste und erweiterter Modus. - [Kompatibilität mit AdGuard VPN](/adguard-for-ios/features/compatibility-with-adguard-vpn.md) diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/features/features.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/features/features.md index c3ff375e470..1e235e4eeeb 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/features/features.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/features/features.md @@ -27,7 +27,7 @@ Dieser Artikel behandelt AdGuard für Mac, einem multifunktionalen Werbeblocker, - [Privatsphäre](/adguard-for-mac/features/stealth.md) - Settings to block cookies, UTM tags, and online analytics that collect user information + Einstellungen zum Blockieren von Cookies, UTM-Tags und Analyse-Tools, die Nutzerdaten sammeln - [Sicherheit](/adguard-for-mac/features/security.md) diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/features/stealth.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/features/stealth.md index e61ca2b0992..961e880adc4 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/features/stealth.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/features/stealth.md @@ -13,4 +13,4 @@ Dieser Artikel behandelt AdGuard für Mac, einem multifunktionalen Werbeblocker, ![Stealth Mode](https://cdn.adtidy.org/content/kb/ad_blocker/mac/tracking_protection.png) -_Tracking protection_ (formerly Stealth Mode) safeguards your privacy by deleting cookies, UTM tags, online counters, and analytics systems. Es verhindert, dass Websites Ihre IP-Adresse, Geräte- und Browserparameter, Suchanfragen und persönliche Informationen sammeln. [Learn more about Tracking protection settings](/general/stealth-mode) +_Tracking protection_ (formerly Stealth Mode) safeguards your privacy by deleting cookies, UTM tags, online counters, and analytics systems. Es verhindert, dass Websites Ihre IP-Adresse, Geräte- und Browserparameter, Suchanfragen und persönliche Informationen sammeln. [Mehr über die Einstellungen zum Tracking-Schutz](/general/stealth-mode) diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md index d3215d76b9c..6073ac31a0e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md @@ -43,6 +43,14 @@ Hier können Sie festlegen, welchen Proxy AdGuard zum Herunterladen von Filter-U ## SockFilter-Treiber verwenden -Aktivieren Sie diese Option, um den SockFilter-Treiber zu verwenden, der dabei hilft, Werbung und Tracker in Apps unter Windows 8 und höher zu blockieren. +Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. If this option is disabled, AdGuard will switch to the older WFP driver instead. -Wenn diese Option deaktiviert ist, wechselt AdGuard stattdessen zum älteren WFP-Treiber. +SockFilter was first introduced in v8.0 RC. It is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +Nach vollständiger Erprobung und Implementierung bietet SockFilter gegenüber anderen Treibern mehrere entscheidende Vorteile: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md index 3f1a0399dae..b77f77756e1 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Deshalb wird die TDI-basierte Verkehrssichtbarkeit zunehmend instabil. In einige AdGuard behandelt den TDI-Treiber bereits als veraltet, und seine vollständige Entfernung ist im Zuge der Weiterentwicklung des Produkts geplant. +## Dauerhafte Lösung + +From v8.0 RC, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [Weitere Informationen](/adguard-for-windows-8/settings/app-settings/network-settings/). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Vorübergehende Lösung Bestimmte Änderungen in der Windows-Registry können den Browser dazu zwingen, die Verwendung von AppContainer zu stoppen, wodurch dessen Prozesse wieder im nicht sandboxed Modus ausgeführt werden. Der Netzwerkdienst verwendet nicht mehr den WSK-Stack, sondern greift auf einen Netzwerkpfad zurück, den der TDI-Treiber sehen kann. AdGuard ist dann wieder in der Lage, den Browserverkehr zu filtern. @@ -123,7 +131,3 @@ Folgende Richtlinien sollten aktiv sein: Falls verfügbar, klicken Sie auf _Richtlinien neu laden_. Fertig! - -## Dauerhafte Lösung - -Wir planen, in den kommenden Versionen Unterstützung für den SockFilter-Treiber hinzuzufügen. Dadurch werden Konflikte im WFP-Stack behoben und das Problem gelöst. [Weitere Informationen](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index 8ccccb19d65..ccc94a93799 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -17,35 +17,47 @@ In diesem Modul können Sie das Kontrollkästchen _AdGuard als HTTP-Proxy verwen Schließlich gibt es noch einen Abschnitt mit Proxy-Einstellungen. Dort können Sie angeben, welchen Proxyserver AdGuard verwenden soll, um Filter zu aktualisieren, neue Versionen zu erhalten usw. -### SockFilter und andere Netzwerktreiber +### Enable traffic filtering -In _Netzwerk_ können Sie auch die Datenverkehrsfilterung aktivieren und auswählen, welcher Treiber verwendet werden soll: SockFilter, WFP oder TDI. +Traffic filtering is the core mechanism that allows AdGuard to inspect and control the network traffic generated by applications on your computer. When it is enabled, AdGuard intercepts outgoing and incoming connections and checks them against its filtering rules. If a request matches a blocking rule, AdGuard can block it, modify it, or allow it depending on the configuration. In AdGuard for Windows, this interception is implemented through network drivers. -**WFP** (Windows Filtering Platform) ist ein leistungsstarker Treiber, kann jedoch für einige Benutzer Stabilitätsrisiken mit sich bringen, wie beispielsweise [gelegentliche Systemabstürze (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792). +If HTTPS filtering is enabled, AdGuard performs a controlled local TLS interception: it decrypts the traffic using its local certificate, applies filtering rules, and then re-encrypts the traffic before sending it to the browser. The driver simply provides the system-level access needed for AdGuard to intercept these connections. -Der **TDI**-Treiber ist ebenfalls verfügbar, jedoch veraltet und kann [in einigen Versionen von Google Chrome zu Filterproblemen führen](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. -Der **SockFilter** ist ein _experimenteller_, schlanker Kernel-Modus-Netzwerktreiber, der auf Socket-Ebene (TCP/UDP) arbeitet. Anstatt Pakete zu überprüfen oder zu modifizieren, während sie den gesamten Windows-Netzwerkstack durchlaufen, fängt ein Sock-Filter Socket-Aufrufe (z. B. connect, send, receive, bind) auf einer höheren, stabileren Abstraktionsebene ab. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. +#### SockFilter -Derzeit ist SockFilter Right noch instabil, und es können Probleme auftreten. Nach vollständiger Erprobung und Implementierung bietet SockFilter gegenüber anderen Treibern mehrere entscheidende Vorteile: +**SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. -- **Es wird auf einer höheren Ebene ausgeführt**: SockFilter arbeitet mit Socket-Operationen statt mit Rohpaketen, wodurch es weniger komplex und stabiler ist als die Low-Level-Paketfilterung von WFP. -- **Keine Beeinträchtigung anderer Netzwerktreiber**: Da es über den VPN-, Firewall- und Antivirus-WFP-Filtern angesiedelt ist, vermeidet es Probleme mit der Filterreihenfolge und Kompatibilitätskonflikte, die im WFP-Stack häufig auftreten. -- **Deutlich reduziertes Risiko von NETIO-bedingten BSODs**: SockFilter wird nicht innerhalb der NETIO-Paketpipeline ausgeführt, sodass die typischen Absturzszenarien vermieden werden, die durch WFP-Callouts verursacht werden, die Puffer, Klassifizierungsergebnisse oder Paketspeicher fehlerhaft verarbeiten. +SockFilter was first implemented in version 7.22.4, and it is still considered unstable — you may encounter bugs. Once fully tested and implemented, SockFilter has the potential to offer several advantages over other drivers: -Was die Nachteile betrifft, so sieht der SockFilter-Treiber nur Vorgänge auf Socket-Ebene und erfasst keinen Datenverkehr, der von anderen Kernel-Treibern oder Komponenten erzeugt wird, welche die Standard-Winsock-API umgehen. Aus Sicht der Low-Level-Vernetzung kann dies als Einschränkung angesehen werden, da der Treiber nicht auf Rohpakete zugreifen oder Nicht-Socket-Datenverkehr überprüfen kann. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. + +#### WFP + +**WFP** (Windows Filtering Platform) is a Microsoft networking framework built into Windows that allows software to filter and monitor network packets at different layers of the system networking stack. AdGuard uses WFP to safely hook into the network flow of applications and apply filtering rules before the traffic reaches the browser or the Internet. [More information](https://learn.microsoft.com/en-us/windows/win32/fwp/windows-filtering-platform-architecture-overview). + +While it is a powerful driver, it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) and lower Internet speed for some users. + +#### TDI + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. ### AdGuard VPN The last section is dedicated to AdGuard VPN — an ideal tool that provides security and anonymity each time you browse the Internet. You can download it by clicking the _Download_ button or go to the AdGuard VPN website by clicking the _Homepage_ button. -Wie funktioniert AdGuard VPN? Ohne auf technische Details einzugehen, kann gesagt werden, dass VPN einen sicheren verschlüsselten Tunnel zwischen einem Gerät und einem entfernten VPN-Server herstellt. Auf diese Weise bleibt der Datenschutz gewahrt und damit auch die Anonymität, denn ein fremder Beobachter sieht die IP-Adresse des VPN-Servers und nicht die tatsächliche IP-Adresse. +How does AdGuard VPN work? Without going into technical details, we can say that VPN creates a secure encrypted tunnel between the user's computer or mobile device and a remote VPN server. In this way, data privacy is preserved, as well as the anonymity of the user, because a third-party observer sees the IP address of the VPN server and not the actual user's IP. -**Was AdGuard VPN leistet:** +**What AdGuard VPN does:** -- verbirgt Ihren tatsächlichen Aufenthaltsort und hilft Ihnen, anonym zu bleiben -- ändert Ihre IP-Adresse, um Ihre Daten vor Verfolgung zu schützen -- verschlüsselt Ihren Datenverkehr, um ihn für Dritte unlesbar zu machen -- lässt Sie konfigurieren, wo VPN verwendet werden soll und wo nicht (Ausschlussfunktion) +- hides your real whereabouts and helps you stay anonymous +- changes your IP address to protect your data from tracking +- encrypts your traffic to make it unreadable to third parties +- lets you configure where to use VPN and where not to (exclusions feature) -Weitere Informationen über AdGuard VPN finden Sie in der [AdGuard VPN Wissensdatenbank](https://adguard-vpn.com/kb/). +To get more information about AdGuard VPN, dive into the [AdGuard VPN Knowledge Base](https://adguard-vpn.com/kb/). diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index 750e144c51e..eef866033ea 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -44,12 +44,8 @@ Bevor Sie mit dem manuellen Schreiben eigener Regeln beginnen, lesen Sie unsere Viele Websites sammeln Informationen über Personen, die sie besuchen, z. B. ihre IP-Adressen, Informationen über den Browser und das installierte Betriebssystem, die Bildschirmauflösung und sogar darüber, von welcher Seite die Benutzer:innen kamen oder weitergeleitet wurden. Einige Webseiten verwenden Cookies, um den Browser zu kennzeichnen und Ihre persönlichen Einstellungen und Vorlieben zu speichern oder Sie bei Ihrem nächsten Besuch wiederzuerkennen. Dadurch können sie Sie bei Ihrem nächsten Besuch „wiedererkennen“. Tracking-Schutz bewahrt Ihre persönlichen Informationen vor solchen Daten- und Statistiksammelsystemen. -![Tracking-Schutzstufen \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection1.png) - Sie können die Einstellungen für den _Tracking-Schutz_ nach Bedarf anpassen. Beispielsweise können Sie verhindern, dass Websites die Suchanfrage erfahren, mit der Sie sie im Internet gefunden haben, automatisch Cookies von Drittanbietern und Erstanbietern löschen und die Standortfreigabe in Ihrem Browser deaktivieren, um die Verfolgung Ihres Aufenthaltsorts zu unterbinden. -![Benutzerdefinierte Funktionen für den Tracking-Schutz \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection2.png) - Um alles über den _Tracking-Schutz_ und seine Optionen zu erfahren, [lesen Sie diesen Artikel](/general/stealth-mode). ### Internetsicherheit diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md index 778ad6e8794..7bd9b1e7cfb 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Deshalb wird die TDI-basierte Verkehrssichtbarkeit zunehmend instabil. In einige AdGuard behandelt den TDI-Treiber bereits als veraltet, und seine vollständige Entfernung ist im Zuge der Weiterentwicklung des Produkts geplant. +## Dauerhafte Lösung + +From v7.22.4, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [Weitere Informationen](/adguard-for-windows/features/network/#sockfilter-and-other-network-drivers). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Vorübergehende Lösung Bestimmte Änderungen in der Windows-Registry können den Browser dazu zwingen, die Verwendung von AppContainer zu stoppen, wodurch dessen Prozesse wieder im nicht sandboxed Modus ausgeführt werden. Der Netzwerkdienst verwendet nicht mehr den WSK-Stack, sondern greift auf einen Netzwerkpfad zurück, den der TDI-Treiber sehen kann. AdGuard ist dann wieder in der Lage, den Browserverkehr zu filtern. @@ -136,7 +144,3 @@ Folgende Richtlinien sollten aktiv sein: Falls verfügbar, klicken Sie auf _Richtlinien neu laden_. Fertig! - -## Dauerhafte Lösung - -Wir planen, in den kommenden Versionen Unterstützung für den SockFilter-Treiber hinzuzufügen. Dadurch werden Konflikte im WFP-Stack behoben und das Problem gelöst. [Weitere Informationen](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/de/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md b/i18n/de/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md index b30fc7bf41b..52cf27e05f0 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md @@ -205,7 +205,7 @@ This is a filter that blocks various widgets that are not essential for the func - Widgets for content recommendations — related articles, similar websites, various personalized recommendations - Chat widgets that are not integrated with the content and are not the main content of the page -- Marketing widgets: +- Marketing-Widgets: - Chats for communication with assistants or bots - Widgets with product recommendations that are shown to the user - Call-back forms @@ -213,7 +213,7 @@ This is a filter that blocks various widgets that are not essential for the func **Beschränkungen und Ausnahmen** -This filter doesn’t block: +Was wird nicht blockiert? - Widgets closely related to the content of the page, such as comments sections, live chat streams, with an exception of unmoderated chats on sites with unofficial streams, which are often filled with spam and similar content - Widgets for self-promotion and site-specific promotional activities diff --git a/i18n/de/docusaurus-plugin-content-docs/current/general/github-repos.md b/i18n/de/docusaurus-plugin-content-docs/current/general/github-repos.md new file mode 100644 index 00000000000..dfb164c44bc --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/general/github-repos.md @@ -0,0 +1,238 @@ +--- +title: AdGuard’s GitHub repositories +sidebar_position: 9 +--- + +At AdGuard, our goal is to make the Internet safer, more comfortable, and more transparent. This commitment is reflected not only in our product features and strict privacy policies, but also in the fact that we keep our work as open as possible. That includes actively interacting with our community. + +This is why [all of our products have public repositories](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse) — online spaces where anybody can see what we are working on, report issues directly to AdGuard developers, and even contribute to our open-source projects. The repositories cover our ad-blocking apps, filters, browser extensions, DNS solutions, VPN tools, developer utilities, and more. There are different platforms that offer such functionality, but the most popular one by far is GitHub, and all AdGuard projects are stored there. + +This article lists the most important repositories by category, summarizes the purpose of each one, and gives a simple breakdown of what users can do there. + +:::tip + +Pro tip: Creating an issue on GitHub is the most effective way to bring the attention of AdGuard developers to a problem. Just make sure to check that a similar issue doesn’t already exist and describe the problem in a comprehensive but concise way. If it does exist, you can upvote it. + +::: + +## What is Github and its repositories + +Very simply put, you can think of GitHub as sort of Google Docs for code, where multiple people can work on the same project, track changes, and see who made which updates. It provides a central, cloud-based place to store your code so it’s accessible from anywhere. It also has teamwork tools for reviewing changes, fixing issues, and merging everyone’s work smoothly. + +GitHub is widely used for open-source projects, letting anyone view the code, suggest improvements, and contribute. + +A repository (often called “repo” for short) is the most basic element of GitHub. It’s a place where you can store your code, your files, and each file’s revision history. Repositories can have multiple collaborators and can be either public or private. + +## What can you do in AdGuard’s repositories + +You can find links to key repositories below in this article or visit the [general AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all) for a full list. In most repos, you can: + +- **View README file** on the main page: it gives you an introduction to the product and its repo + ![README file \*border](https://cdn.adtidy.org/content/blog/github-repos/see-readme.png) + +- **Check existing bug reports or feature requests**, comment and upvote + ![Check issues \*border](https://cdn.adtidy.org/content/blog/github-repos/check-issues.png) + +- **Create issues** to report bugs or request features + ![Create issues \*border](https://cdn.adtidy.org/content/blog/github-repos/create-issue.png) + +- **Check releases** for different versions and their changelogs (and install an older version if needed) + ![Check releases \*border](https://cdn.adtidy.org/content/blog/github-repos/check-releases.png) + +- **Install any older or beta version** if needed + ![Download builds \*border](https://cdn.adtidy.org/content/blog/github-repos/download-releases.png) + +:::note + +If you are new to GitHub, you’ll need to create a GitHub account in order to create new issues and comment on the existing ones. + +::: + +In open-source repos advanced users can also: + +- **Browse code** to understand product logic, what technologies are used and how they are implemented +- **Fork and contribute** via pull requests + +Whether you’re a casual user, technical expert, or a developer, AdGuard welcomes all community participation across its GitHub repos. + +## Legal documents + +### [LegalDocs](https://github.com/AdguardTeam/LegalDocs) + +As part of our commitment to transparency, we host all legal documents — such as End-User License Agreements, Privacy Policies, and Terms and Conditions — on GitHub. Our _LegalDocs_ repo lets anyone check the full history of changes to these documents. + +## AdGuard Ad Blocker products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdguardForAndroid](https://github.com/AdguardTeam/AdguardForAndroid) + +Repository of AdGuard for Android — an app that provides system-wide ad blocking. + +### [AdguardForiOS](https://github.com/AdguardTeam/AdguardForiOS) + +Repository of AdGuard for iOS — Safari content blocker with DNS and custom filters. Users can also check open-source code. + +### [AdguardForWindows](https://github.com/AdguardTeam/AdguardForWindows) + +Repository of AdGuard for Windows. Non-open-source; GitHub used as an open bug tracker. + +### [AdguardForMac](https://github.com/AdguardTeam/AdguardForMac) + +Repository of AdGuard for Mac — macOS standalone content blocker. Bug tracker only. + +### [AdguardBrowserExtension](https://github.com/AdguardTeam/AdguardBrowserExtension) + +Repository of AdGuard Browser Extension — extension that provides ad blocking with enhanced privacy for Chrome, Firefox, Opera, Edge. + +### [AdguardForSafari](https://github.com/AdguardTeam/AdGuardForSafari) + +Repository of AdGuard for Safari — Safari ad blocking extension for Mac. Users can also check open-sourced code. + +### [AdGuardCLI](https://github.com/AdguardTeam/AdGuardCLI) + +Repository of AdGuard for Linux — a command‑line interface for managing ad blocking. + +## AdGuard VPN products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdGuardVPNForiOS](https://github.com/AdguardTeam/AdGuardVPNForiOS) + +Repository of AdGuard VPN for iOS. Serves as an open bug tracker. + +### [AdGuardVPNForAndroid](https://github.com/AdguardTeam/AdGuardVPNForAndroid) + +Repository of AdGuard VPN for Android. Serves as an open bug tracker. + +### [AdGuardVPNForWindows](https://github.com/AdguardTeam/AdGuardVPNForWindows) + +Repository of AdGuard VPN for Windows. Serves as an open bug tracker. + +### [AdGuardVPNForMac](https://github.com/AdguardTeam/AdGuardVPNForMac) + +Repository of AdGuard VPN for Mac — app designed for macOS. + +### [AdGuardVPNExtension](https://github.com/AdguardTeam/AdGuardVPNExtension) + +Repository of AdGuard VPN Browser Extension. + +### [AdGuardVPNCLI](https://github.com/AdguardTeam/AdGuardVPNCLI) + +Repository of AdGuard VPN for Linux — a command‑line interface for managing VPN connection. The repo acts as a bug tracker. + +## DNS-based products + +### [AdGuardDNS](https://github.com/AdguardTeam/AdGuardDNS) + +Open-source repository that is also used for tracking bugs and issues related to AdGuard DNS service. Users can: + +- View and report DNS issues +- Suggest improvements + +### [AdGuardHome](https://github.com/AdguardTeam/AdGuardHome) + +Repository of AdGuard Home — free network-wide software for blocking ads and trackers via DNS. Users can: + +- Check and file bug reports or feature requests +- Review or contribute to code +- Download and install releases + +## Documentation and Knowledge bases + +Knowledge bases are aimed to help users better understand and use AdGuard. They describe each AdGuard product in detail: from feature overviews and problem-solving guides to advanced setting manuals and API documentations. In the repositories users can: + +- Suggest corrections or edits to knowledge base articles +- Propose new articles +- Test or run the local version + +### [KnowledgeBase](https://github.com/AdguardTeam/KnowledgeBase) + +Central documentation for AdGuard Ad Blocker and the technologies related to it. + +### [KnowledgeBaseDNS](https://github.com/AdguardTeam/KnowledgeBaseDNS) + +Detailed feature overview, troubleshooting guides and documentation for AdGuard DNS (both Public and Private), AdGuard Home, and everything related to them. + +### [KnowledgeBaseVPN](https://github.com/AdguardTeam/KnowledgeBaseVPN) + +Detailed feature overview and troubleshooting guides for AdGuard VPN. + +### [KnowledgeBaseMail](https://github.com/AdguardTeam/KnowledgeBaseMail) + +Detailed feature overview and troubleshooting guides of AdGuard Mail. + +## Core libraries + +### [CoreLibs](https://github.com/AdguardTeam/CoreLibs) + +AdGuard’s cross-platform core filtering engine. Used in Android, Windows, and Mac products. Users can: + +- Explore filtering logic and DNS handling +- Report bugs and suggest features via Issues + +### [DNSLibs](https://github.com/AdguardTeam/DNSLibs) + +A DNS library used by CoreLibs and AdGuardHome. Users can: + +- Review and contribute to low-level DNS implementation +- Suggest optimizations + +### [VPNLibs](https://github.com/AdguardTeam/VPNLibs) + +Shared codebase used in AdGuard VPN products across platforms for AdGuard VPN protocol implementation. Users can: + +- Contribute to VPN stack behavior +- Report or view performance issues and bugs + +## Core ad blocking and filtering technologies + +### [AdguardFilters](https://github.com/AdguardTeam/AdguardFilters) + +Contains AdGuard’s core filter lists. Users can: + +- View and download filter lists +- Create issues to report false positives or suggest new rules +- Monitor updates to filter logic + +### [AdGuardSDNSFilter](https://github.com/AdguardTeam/AdGuardSDNSFilter) + +Repository of AdGuard DNS filter — the main DNS-level blocking list used in AdGuard DNS and DNS filtering features. Users can: + +- Inspect the current rule set +- Propose changes or additions + +### [AGLint](https://github.com/AdguardTeam/AGLint) + +A linter for adblock filter list syntax. Users can: + +- Install AGLint to check their projects for rule issues +- Contribute to lint rules + +### [Scriptlets](https://github.com/AdguardTeam/Scriptlets) + +JavaScript helpers used in filtering rules. Users can: + +- Explore available scriptlets +- Submit pull requests for new scriptlets + +### [tsurlfilter](https://github.com/AdguardTeam/tsurlfilter) + +TypeScript content blocker library for browser extensions. Users can: + +- Explore how filtering logic is implemented +- Contribute fixes and features + +## There’s more + +Above, we listed 27 main public AdGuard repositories out of 96 total. If you want to go down the rabbit hole, you can [find the rest on the AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse). + +We’ll be waiting for your feedback there! Stay safe online and offline. diff --git a/i18n/de/docusaurus-plugin-content-docs/current/general/how-to-install.md b/i18n/de/docusaurus-plugin-content-docs/current/general/how-to-install.md index b79b038324a..7049fb48ac4 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/general/how-to-install.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/general/how-to-install.md @@ -1,6 +1,6 @@ --- title: So installieren Sie AdGuard -sidebar_position: 9 +sidebar_position: 10 --- Je nachdem, welche AdGuard-App oder Browsererweiterung Sie installieren möchten, folgen Sie einem dieser Links, um den entsprechenden Artikel zu finden: diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md index 2db6ca8ffaf..31d54587f21 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md @@ -43,6 +43,14 @@ Here you can choose which proxy AdGuard should use to download filter updates or ## Use SockFilter driver -Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. +Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. If this option is disabled, AdGuard will switch to the older WFP driver instead. -If this option is disabled, AdGuard will switch to the older WFP driver instead. +SockFilter was first introduced in v8.0 RC. It is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md index da54018bac5..aa5e5bf5ac5 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Because of this, TDI-based traffic visibility becomes increasingly unstable. In AdGuard already treats the TDI driver as deprecated, and its complete removal is planned as the product evolves. +## Permanent solution + +From v8.0 RC, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows-8/settings/app-settings/network-settings/). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Temporary solution Certain Windows registry changes can force the browser to stop using AppContainer, causing its processes to run in a non-sandboxed mode again. Network Service stops using the WSK stack and falls back to a network path that the TDI driver can see. AdGuard then regains the ability to filter browser traffic. @@ -123,7 +131,3 @@ You should see the following policies active: If available, click _Reload policies_. ¡Listo! - -## Permanent solution - -We’re planning to add support for the SockFilter driver in the upcoming versions. It will fix the issue by solving conflicts in the WFP stack. [More information](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index 9a652fb1281..1dccb378291 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -17,23 +17,35 @@ En este módulo, puedes marcar la casilla de verificación _Usar AdGuard como pr Por fin, hay una sección con configuración de proxy. Allí puedes especificar qué servidor proxy AdGuard debe utilizar para actualizar los filtros, obtener nuevas versiones, etc. -### SockFilter and other network drivers +### Enable traffic filtering -In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. +Traffic filtering is the core mechanism that allows AdGuard to inspect and control the network traffic generated by applications on your computer. When it is enabled, AdGuard intercepts outgoing and incoming connections and checks them against its filtering rules. If a request matches a blocking rule, AdGuard can block it, modify it, or allow it depending on the configuration. In AdGuard for Windows, this interception is implemented through network drivers. -**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. +If HTTPS filtering is enabled, AdGuard performs a controlled local TLS interception: it decrypts the traffic using its local certificate, applies filtering rules, and then re-encrypts the traffic before sending it to the browser. The driver simply provides the system-level access needed for AdGuard to intercept these connections. -The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +#### SockFilter **SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. -Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: +SockFilter was first implemented in version 7.22.4, and it is still considered unstable — you may encounter bugs. Once fully tested and implemented, SockFilter has the potential to offer several advantages over other drivers: -- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. - **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. -- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. -When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. +#### WFP + +**WFP** (Windows Filtering Platform) is a Microsoft networking framework built into Windows that allows software to filter and monitor network packets at different layers of the system networking stack. AdGuard uses WFP to safely hook into the network flow of applications and apply filtering rules before the traffic reaches the browser or the Internet. [More information](https://learn.microsoft.com/en-us/windows/win32/fwp/windows-filtering-platform-architecture-overview). + +While it is a powerful driver, it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) and lower Internet speed for some users. + +#### TDI + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. ### AdGuard VPN diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index 7507dbd2c99..5aba3826738 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -44,12 +44,8 @@ Antes de empezar a escribir manualmente tus propias reglas, lee nuestra detallad Many websites gather information about their visitors, such as their IP addresses, browser and operating system details, screen resolution, and the webpage from which the user came or was redirected. Some websites use cookies to mark and identify your browser, save your personal settings and preferences. This allows them to “recognize” you on your next visit. Tracking protection safeguards your personal information from these data- and statistics-gathering systems. -![Tracking protection levels \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection1.png) - You can adjust the _Tracking Protection_ settings as needed. For example, you can prevent websites from receiving the search request that you used to find them on the Internet, automatically delete third- and first-party cookies, and disable location sharing in your browser, to prevent tracking of your whereabouts. -![Tracking protection custom features \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection2.png) - To learn everything about _Tracking protection_ and its many options, [read this article](/general/stealth-mode). ### Seguridad de navegación diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md index 12f1c37e2ea..191feae1d2e 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Because of this, TDI-based traffic visibility becomes increasingly unstable. In AdGuard already treats the TDI driver as deprecated, and its complete removal is planned as the product evolves. +## Permanent solution + +From v7.22.4, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows/features/network/#sockfilter-and-other-network-drivers). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Temporary solution Certain Windows registry changes can force the browser to stop using AppContainer, causing its processes to run in a non-sandboxed mode again. Network Service stops using the WSK stack and falls back to a network path that the TDI driver can see. AdGuard then regains the ability to filter browser traffic. @@ -136,7 +144,3 @@ You should see the following policies active: If available, click _Reload policies_. ¡Listo! - -## Permanent solution - -We’re planning to add support for the SockFilter driver in the upcoming versions. It will fix the issue by solving conflicts in the WFP stack. [More information](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/es/docusaurus-plugin-content-docs/current/general/github-repos.md b/i18n/es/docusaurus-plugin-content-docs/current/general/github-repos.md new file mode 100644 index 00000000000..dfb164c44bc --- /dev/null +++ b/i18n/es/docusaurus-plugin-content-docs/current/general/github-repos.md @@ -0,0 +1,238 @@ +--- +title: AdGuard’s GitHub repositories +sidebar_position: 9 +--- + +At AdGuard, our goal is to make the Internet safer, more comfortable, and more transparent. This commitment is reflected not only in our product features and strict privacy policies, but also in the fact that we keep our work as open as possible. That includes actively interacting with our community. + +This is why [all of our products have public repositories](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse) — online spaces where anybody can see what we are working on, report issues directly to AdGuard developers, and even contribute to our open-source projects. The repositories cover our ad-blocking apps, filters, browser extensions, DNS solutions, VPN tools, developer utilities, and more. There are different platforms that offer such functionality, but the most popular one by far is GitHub, and all AdGuard projects are stored there. + +This article lists the most important repositories by category, summarizes the purpose of each one, and gives a simple breakdown of what users can do there. + +:::tip + +Pro tip: Creating an issue on GitHub is the most effective way to bring the attention of AdGuard developers to a problem. Just make sure to check that a similar issue doesn’t already exist and describe the problem in a comprehensive but concise way. If it does exist, you can upvote it. + +::: + +## What is Github and its repositories + +Very simply put, you can think of GitHub as sort of Google Docs for code, where multiple people can work on the same project, track changes, and see who made which updates. It provides a central, cloud-based place to store your code so it’s accessible from anywhere. It also has teamwork tools for reviewing changes, fixing issues, and merging everyone’s work smoothly. + +GitHub is widely used for open-source projects, letting anyone view the code, suggest improvements, and contribute. + +A repository (often called “repo” for short) is the most basic element of GitHub. It’s a place where you can store your code, your files, and each file’s revision history. Repositories can have multiple collaborators and can be either public or private. + +## What can you do in AdGuard’s repositories + +You can find links to key repositories below in this article or visit the [general AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all) for a full list. In most repos, you can: + +- **View README file** on the main page: it gives you an introduction to the product and its repo + ![README file \*border](https://cdn.adtidy.org/content/blog/github-repos/see-readme.png) + +- **Check existing bug reports or feature requests**, comment and upvote + ![Check issues \*border](https://cdn.adtidy.org/content/blog/github-repos/check-issues.png) + +- **Create issues** to report bugs or request features + ![Create issues \*border](https://cdn.adtidy.org/content/blog/github-repos/create-issue.png) + +- **Check releases** for different versions and their changelogs (and install an older version if needed) + ![Check releases \*border](https://cdn.adtidy.org/content/blog/github-repos/check-releases.png) + +- **Install any older or beta version** if needed + ![Download builds \*border](https://cdn.adtidy.org/content/blog/github-repos/download-releases.png) + +:::note + +If you are new to GitHub, you’ll need to create a GitHub account in order to create new issues and comment on the existing ones. + +::: + +In open-source repos advanced users can also: + +- **Browse code** to understand product logic, what technologies are used and how they are implemented +- **Fork and contribute** via pull requests + +Whether you’re a casual user, technical expert, or a developer, AdGuard welcomes all community participation across its GitHub repos. + +## Legal documents + +### [LegalDocs](https://github.com/AdguardTeam/LegalDocs) + +As part of our commitment to transparency, we host all legal documents — such as End-User License Agreements, Privacy Policies, and Terms and Conditions — on GitHub. Our _LegalDocs_ repo lets anyone check the full history of changes to these documents. + +## AdGuard Ad Blocker products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdguardForAndroid](https://github.com/AdguardTeam/AdguardForAndroid) + +Repository of AdGuard for Android — an app that provides system-wide ad blocking. + +### [AdguardForiOS](https://github.com/AdguardTeam/AdguardForiOS) + +Repository of AdGuard for iOS — Safari content blocker with DNS and custom filters. Users can also check open-source code. + +### [AdguardForWindows](https://github.com/AdguardTeam/AdguardForWindows) + +Repository of AdGuard for Windows. Non-open-source; GitHub used as an open bug tracker. + +### [AdguardForMac](https://github.com/AdguardTeam/AdguardForMac) + +Repository of AdGuard for Mac — macOS standalone content blocker. Bug tracker only. + +### [AdguardBrowserExtension](https://github.com/AdguardTeam/AdguardBrowserExtension) + +Repository of AdGuard Browser Extension — extension that provides ad blocking with enhanced privacy for Chrome, Firefox, Opera, Edge. + +### [AdguardForSafari](https://github.com/AdguardTeam/AdGuardForSafari) + +Repository of AdGuard for Safari — Safari ad blocking extension for Mac. Users can also check open-sourced code. + +### [AdGuardCLI](https://github.com/AdguardTeam/AdGuardCLI) + +Repository of AdGuard for Linux — a command‑line interface for managing ad blocking. + +## AdGuard VPN products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdGuardVPNForiOS](https://github.com/AdguardTeam/AdGuardVPNForiOS) + +Repository of AdGuard VPN for iOS. Serves as an open bug tracker. + +### [AdGuardVPNForAndroid](https://github.com/AdguardTeam/AdGuardVPNForAndroid) + +Repository of AdGuard VPN for Android. Serves as an open bug tracker. + +### [AdGuardVPNForWindows](https://github.com/AdguardTeam/AdGuardVPNForWindows) + +Repository of AdGuard VPN for Windows. Serves as an open bug tracker. + +### [AdGuardVPNForMac](https://github.com/AdguardTeam/AdGuardVPNForMac) + +Repository of AdGuard VPN for Mac — app designed for macOS. + +### [AdGuardVPNExtension](https://github.com/AdguardTeam/AdGuardVPNExtension) + +Repository of AdGuard VPN Browser Extension. + +### [AdGuardVPNCLI](https://github.com/AdguardTeam/AdGuardVPNCLI) + +Repository of AdGuard VPN for Linux — a command‑line interface for managing VPN connection. The repo acts as a bug tracker. + +## DNS-based products + +### [AdGuardDNS](https://github.com/AdguardTeam/AdGuardDNS) + +Open-source repository that is also used for tracking bugs and issues related to AdGuard DNS service. Users can: + +- View and report DNS issues +- Suggest improvements + +### [AdGuardHome](https://github.com/AdguardTeam/AdGuardHome) + +Repository of AdGuard Home — free network-wide software for blocking ads and trackers via DNS. Users can: + +- Check and file bug reports or feature requests +- Review or contribute to code +- Download and install releases + +## Documentation and Knowledge bases + +Knowledge bases are aimed to help users better understand and use AdGuard. They describe each AdGuard product in detail: from feature overviews and problem-solving guides to advanced setting manuals and API documentations. In the repositories users can: + +- Suggest corrections or edits to knowledge base articles +- Propose new articles +- Test or run the local version + +### [KnowledgeBase](https://github.com/AdguardTeam/KnowledgeBase) + +Central documentation for AdGuard Ad Blocker and the technologies related to it. + +### [KnowledgeBaseDNS](https://github.com/AdguardTeam/KnowledgeBaseDNS) + +Detailed feature overview, troubleshooting guides and documentation for AdGuard DNS (both Public and Private), AdGuard Home, and everything related to them. + +### [KnowledgeBaseVPN](https://github.com/AdguardTeam/KnowledgeBaseVPN) + +Detailed feature overview and troubleshooting guides for AdGuard VPN. + +### [KnowledgeBaseMail](https://github.com/AdguardTeam/KnowledgeBaseMail) + +Detailed feature overview and troubleshooting guides of AdGuard Mail. + +## Core libraries + +### [CoreLibs](https://github.com/AdguardTeam/CoreLibs) + +AdGuard’s cross-platform core filtering engine. Used in Android, Windows, and Mac products. Users can: + +- Explore filtering logic and DNS handling +- Report bugs and suggest features via Issues + +### [DNSLibs](https://github.com/AdguardTeam/DNSLibs) + +A DNS library used by CoreLibs and AdGuardHome. Users can: + +- Review and contribute to low-level DNS implementation +- Suggest optimizations + +### [VPNLibs](https://github.com/AdguardTeam/VPNLibs) + +Shared codebase used in AdGuard VPN products across platforms for AdGuard VPN protocol implementation. Users can: + +- Contribute to VPN stack behavior +- Report or view performance issues and bugs + +## Core ad blocking and filtering technologies + +### [AdguardFilters](https://github.com/AdguardTeam/AdguardFilters) + +Contains AdGuard’s core filter lists. Users can: + +- View and download filter lists +- Create issues to report false positives or suggest new rules +- Monitor updates to filter logic + +### [AdGuardSDNSFilter](https://github.com/AdguardTeam/AdGuardSDNSFilter) + +Repository of AdGuard DNS filter — the main DNS-level blocking list used in AdGuard DNS and DNS filtering features. Users can: + +- Inspect the current rule set +- Propose changes or additions + +### [AGLint](https://github.com/AdguardTeam/AGLint) + +A linter for adblock filter list syntax. Users can: + +- Install AGLint to check their projects for rule issues +- Contribute to lint rules + +### [Scriptlets](https://github.com/AdguardTeam/Scriptlets) + +JavaScript helpers used in filtering rules. Users can: + +- Explore available scriptlets +- Submit pull requests for new scriptlets + +### [tsurlfilter](https://github.com/AdguardTeam/tsurlfilter) + +TypeScript content blocker library for browser extensions. Users can: + +- Explore how filtering logic is implemented +- Contribute fixes and features + +## There’s more + +Above, we listed 27 main public AdGuard repositories out of 96 total. If you want to go down the rabbit hole, you can [find the rest on the AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse). + +We’ll be waiting for your feedback there! Stay safe online and offline. diff --git a/i18n/es/docusaurus-plugin-content-docs/current/general/how-to-install.md b/i18n/es/docusaurus-plugin-content-docs/current/general/how-to-install.md index e21f85dc187..f30bf40ddf0 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/general/how-to-install.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/general/how-to-install.md @@ -1,6 +1,6 @@ --- title: Cómo instalar AdGuard -sidebar_position: 9 +sidebar_position: 10 --- Dependiendo de la aplicación AdGuard o de la extensión del navegador que desee instalar, siga uno de estos enlaces para encontrar el artículo correspondiente: diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md index 3953f47d26f..05642d350b0 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md @@ -43,6 +43,14 @@ Here you can choose which proxy AdGuard should use to download filter updates or ## Use SockFilter driver -Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. +Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. If this option is disabled, AdGuard will switch to the older WFP driver instead. -If this option is disabled, AdGuard will switch to the older WFP driver instead. +SockFilter was first introduced in v8.0 RC. It is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md index 251e49cf286..1ab588bb16c 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Because of this, TDI-based traffic visibility becomes increasingly unstable. In AdGuard already treats the TDI driver as deprecated, and its complete removal is planned as the product evolves. +## Permanent solution + +From v8.0 RC, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows-8/settings/app-settings/network-settings/). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Temporary solution Certain Windows registry changes can force the browser to stop using AppContainer, causing its processes to run in a non-sandboxed mode again. Network Service stops using the WSK stack and falls back to a network path that the TDI driver can see. AdGuard then regains the ability to filter browser traffic. @@ -123,7 +131,3 @@ You should see the following policies active: If available, click _Reload policies_. Done! - -## Permanent solution - -We’re planning to add support for the SockFilter driver in the upcoming versions. It will fix the issue by solving conflicts in the WFP stack. [More information](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index 5945618ea9c..f8074e9cfa1 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -17,23 +17,35 @@ In this module you can select the checkbox _Use AdGuard as an HTTP proxy_ to use At last, there is a section with proxy settings. There you can specify which proxy server AdGuard should use to update filters, get new versions, and so on. -### SockFilter and other network drivers +### Enable traffic filtering -In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. +Traffic filtering is the core mechanism that allows AdGuard to inspect and control the network traffic generated by applications on your computer. When it is enabled, AdGuard intercepts outgoing and incoming connections and checks them against its filtering rules. If a request matches a blocking rule, AdGuard can block it, modify it, or allow it depending on the configuration. In AdGuard for Windows, this interception is implemented through network drivers. -**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. +If HTTPS filtering is enabled, AdGuard performs a controlled local TLS interception: it decrypts the traffic using its local certificate, applies filtering rules, and then re-encrypts the traffic before sending it to the browser. The driver simply provides the system-level access needed for AdGuard to intercept these connections. -The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +#### SockFilter **SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. -Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: +SockFilter was first implemented in version 7.22.4, and it is still considered unstable — you may encounter bugs. Once fully tested and implemented, SockFilter has the potential to offer several advantages over other drivers: -- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. - **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. -- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. -When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. +#### WFP + +**WFP** (Windows Filtering Platform) is a Microsoft networking framework built into Windows that allows software to filter and monitor network packets at different layers of the system networking stack. AdGuard uses WFP to safely hook into the network flow of applications and apply filtering rules before the traffic reaches the browser or the Internet. [More information](https://learn.microsoft.com/en-us/windows/win32/fwp/windows-filtering-platform-architecture-overview). + +While it is a powerful driver, it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) and lower Internet speed for some users. + +#### TDI + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. ### AdGuard VPN diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index ab90a964b9f..5699b31b033 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -44,12 +44,8 @@ Before you start manually writing your own rules read our detailed [syntax guide Many websites gather information about their visitors, such as their IP addresses, browser and operating system details, screen resolution, and the webpage from which the user came or was redirected. Some websites use cookies to mark and identify your browser, save your personal settings and preferences. This allows them to “recognize” you on your next visit. Tracking protection safeguards your personal information from these data- and statistics-gathering systems. -![Tracking protection levels \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection1.png) - You can adjust the _Tracking Protection_ settings as needed. For example, you can prevent websites from receiving the search request that you used to find them on the Internet, automatically delete third- and first-party cookies, and disable location sharing in your browser, to prevent tracking of your whereabouts. -![Tracking protection custom features \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection2.png) - To learn everything about _Tracking protection_ and its many options, [read this article](/general/stealth-mode). ### Browsing security diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md index 62370bf3eb1..bec08d0c665 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Because of this, TDI-based traffic visibility becomes increasingly unstable. In AdGuard already treats the TDI driver as deprecated, and its complete removal is planned as the product evolves. +## Permanent solution + +From v7.22.4, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows/features/network/#sockfilter-and-other-network-drivers). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Temporary solution Certain Windows registry changes can force the browser to stop using AppContainer, causing its processes to run in a non-sandboxed mode again. Network Service stops using the WSK stack and falls back to a network path that the TDI driver can see. AdGuard then regains the ability to filter browser traffic. @@ -136,7 +144,3 @@ You should see the following policies active: If available, click _Reload policies_. Done! - -## Permanent solution - -We’re planning to add support for the SockFilter driver in the upcoming versions. It will fix the issue by solving conflicts in the WFP stack. [More information](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/general/github-repos.md b/i18n/fa/docusaurus-plugin-content-docs/current/general/github-repos.md new file mode 100644 index 00000000000..dfb164c44bc --- /dev/null +++ b/i18n/fa/docusaurus-plugin-content-docs/current/general/github-repos.md @@ -0,0 +1,238 @@ +--- +title: AdGuard’s GitHub repositories +sidebar_position: 9 +--- + +At AdGuard, our goal is to make the Internet safer, more comfortable, and more transparent. This commitment is reflected not only in our product features and strict privacy policies, but also in the fact that we keep our work as open as possible. That includes actively interacting with our community. + +This is why [all of our products have public repositories](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse) — online spaces where anybody can see what we are working on, report issues directly to AdGuard developers, and even contribute to our open-source projects. The repositories cover our ad-blocking apps, filters, browser extensions, DNS solutions, VPN tools, developer utilities, and more. There are different platforms that offer such functionality, but the most popular one by far is GitHub, and all AdGuard projects are stored there. + +This article lists the most important repositories by category, summarizes the purpose of each one, and gives a simple breakdown of what users can do there. + +:::tip + +Pro tip: Creating an issue on GitHub is the most effective way to bring the attention of AdGuard developers to a problem. Just make sure to check that a similar issue doesn’t already exist and describe the problem in a comprehensive but concise way. If it does exist, you can upvote it. + +::: + +## What is Github and its repositories + +Very simply put, you can think of GitHub as sort of Google Docs for code, where multiple people can work on the same project, track changes, and see who made which updates. It provides a central, cloud-based place to store your code so it’s accessible from anywhere. It also has teamwork tools for reviewing changes, fixing issues, and merging everyone’s work smoothly. + +GitHub is widely used for open-source projects, letting anyone view the code, suggest improvements, and contribute. + +A repository (often called “repo” for short) is the most basic element of GitHub. It’s a place where you can store your code, your files, and each file’s revision history. Repositories can have multiple collaborators and can be either public or private. + +## What can you do in AdGuard’s repositories + +You can find links to key repositories below in this article or visit the [general AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all) for a full list. In most repos, you can: + +- **View README file** on the main page: it gives you an introduction to the product and its repo + ![README file \*border](https://cdn.adtidy.org/content/blog/github-repos/see-readme.png) + +- **Check existing bug reports or feature requests**, comment and upvote + ![Check issues \*border](https://cdn.adtidy.org/content/blog/github-repos/check-issues.png) + +- **Create issues** to report bugs or request features + ![Create issues \*border](https://cdn.adtidy.org/content/blog/github-repos/create-issue.png) + +- **Check releases** for different versions and their changelogs (and install an older version if needed) + ![Check releases \*border](https://cdn.adtidy.org/content/blog/github-repos/check-releases.png) + +- **Install any older or beta version** if needed + ![Download builds \*border](https://cdn.adtidy.org/content/blog/github-repos/download-releases.png) + +:::note + +If you are new to GitHub, you’ll need to create a GitHub account in order to create new issues and comment on the existing ones. + +::: + +In open-source repos advanced users can also: + +- **Browse code** to understand product logic, what technologies are used and how they are implemented +- **Fork and contribute** via pull requests + +Whether you’re a casual user, technical expert, or a developer, AdGuard welcomes all community participation across its GitHub repos. + +## Legal documents + +### [LegalDocs](https://github.com/AdguardTeam/LegalDocs) + +As part of our commitment to transparency, we host all legal documents — such as End-User License Agreements, Privacy Policies, and Terms and Conditions — on GitHub. Our _LegalDocs_ repo lets anyone check the full history of changes to these documents. + +## AdGuard Ad Blocker products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdguardForAndroid](https://github.com/AdguardTeam/AdguardForAndroid) + +Repository of AdGuard for Android — an app that provides system-wide ad blocking. + +### [AdguardForiOS](https://github.com/AdguardTeam/AdguardForiOS) + +Repository of AdGuard for iOS — Safari content blocker with DNS and custom filters. Users can also check open-source code. + +### [AdguardForWindows](https://github.com/AdguardTeam/AdguardForWindows) + +Repository of AdGuard for Windows. Non-open-source; GitHub used as an open bug tracker. + +### [AdguardForMac](https://github.com/AdguardTeam/AdguardForMac) + +Repository of AdGuard for Mac — macOS standalone content blocker. Bug tracker only. + +### [AdguardBrowserExtension](https://github.com/AdguardTeam/AdguardBrowserExtension) + +Repository of AdGuard Browser Extension — extension that provides ad blocking with enhanced privacy for Chrome, Firefox, Opera, Edge. + +### [AdguardForSafari](https://github.com/AdguardTeam/AdGuardForSafari) + +Repository of AdGuard for Safari — Safari ad blocking extension for Mac. Users can also check open-sourced code. + +### [AdGuardCLI](https://github.com/AdguardTeam/AdGuardCLI) + +Repository of AdGuard for Linux — a command‑line interface for managing ad blocking. + +## AdGuard VPN products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdGuardVPNForiOS](https://github.com/AdguardTeam/AdGuardVPNForiOS) + +Repository of AdGuard VPN for iOS. Serves as an open bug tracker. + +### [AdGuardVPNForAndroid](https://github.com/AdguardTeam/AdGuardVPNForAndroid) + +Repository of AdGuard VPN for Android. Serves as an open bug tracker. + +### [AdGuardVPNForWindows](https://github.com/AdguardTeam/AdGuardVPNForWindows) + +Repository of AdGuard VPN for Windows. Serves as an open bug tracker. + +### [AdGuardVPNForMac](https://github.com/AdguardTeam/AdGuardVPNForMac) + +Repository of AdGuard VPN for Mac — app designed for macOS. + +### [AdGuardVPNExtension](https://github.com/AdguardTeam/AdGuardVPNExtension) + +Repository of AdGuard VPN Browser Extension. + +### [AdGuardVPNCLI](https://github.com/AdguardTeam/AdGuardVPNCLI) + +Repository of AdGuard VPN for Linux — a command‑line interface for managing VPN connection. The repo acts as a bug tracker. + +## DNS-based products + +### [AdGuardDNS](https://github.com/AdguardTeam/AdGuardDNS) + +Open-source repository that is also used for tracking bugs and issues related to AdGuard DNS service. Users can: + +- View and report DNS issues +- Suggest improvements + +### [AdGuardHome](https://github.com/AdguardTeam/AdGuardHome) + +Repository of AdGuard Home — free network-wide software for blocking ads and trackers via DNS. Users can: + +- Check and file bug reports or feature requests +- Review or contribute to code +- Download and install releases + +## Documentation and Knowledge bases + +Knowledge bases are aimed to help users better understand and use AdGuard. They describe each AdGuard product in detail: from feature overviews and problem-solving guides to advanced setting manuals and API documentations. In the repositories users can: + +- Suggest corrections or edits to knowledge base articles +- Propose new articles +- Test or run the local version + +### [KnowledgeBase](https://github.com/AdguardTeam/KnowledgeBase) + +Central documentation for AdGuard Ad Blocker and the technologies related to it. + +### [KnowledgeBaseDNS](https://github.com/AdguardTeam/KnowledgeBaseDNS) + +Detailed feature overview, troubleshooting guides and documentation for AdGuard DNS (both Public and Private), AdGuard Home, and everything related to them. + +### [KnowledgeBaseVPN](https://github.com/AdguardTeam/KnowledgeBaseVPN) + +Detailed feature overview and troubleshooting guides for AdGuard VPN. + +### [KnowledgeBaseMail](https://github.com/AdguardTeam/KnowledgeBaseMail) + +Detailed feature overview and troubleshooting guides of AdGuard Mail. + +## Core libraries + +### [CoreLibs](https://github.com/AdguardTeam/CoreLibs) + +AdGuard’s cross-platform core filtering engine. Used in Android, Windows, and Mac products. Users can: + +- Explore filtering logic and DNS handling +- Report bugs and suggest features via Issues + +### [DNSLibs](https://github.com/AdguardTeam/DNSLibs) + +A DNS library used by CoreLibs and AdGuardHome. Users can: + +- Review and contribute to low-level DNS implementation +- Suggest optimizations + +### [VPNLibs](https://github.com/AdguardTeam/VPNLibs) + +Shared codebase used in AdGuard VPN products across platforms for AdGuard VPN protocol implementation. Users can: + +- Contribute to VPN stack behavior +- Report or view performance issues and bugs + +## Core ad blocking and filtering technologies + +### [AdguardFilters](https://github.com/AdguardTeam/AdguardFilters) + +Contains AdGuard’s core filter lists. Users can: + +- View and download filter lists +- Create issues to report false positives or suggest new rules +- Monitor updates to filter logic + +### [AdGuardSDNSFilter](https://github.com/AdguardTeam/AdGuardSDNSFilter) + +Repository of AdGuard DNS filter — the main DNS-level blocking list used in AdGuard DNS and DNS filtering features. Users can: + +- Inspect the current rule set +- Propose changes or additions + +### [AGLint](https://github.com/AdguardTeam/AGLint) + +A linter for adblock filter list syntax. Users can: + +- Install AGLint to check their projects for rule issues +- Contribute to lint rules + +### [Scriptlets](https://github.com/AdguardTeam/Scriptlets) + +JavaScript helpers used in filtering rules. Users can: + +- Explore available scriptlets +- Submit pull requests for new scriptlets + +### [tsurlfilter](https://github.com/AdguardTeam/tsurlfilter) + +TypeScript content blocker library for browser extensions. Users can: + +- Explore how filtering logic is implemented +- Contribute fixes and features + +## There’s more + +Above, we listed 27 main public AdGuard repositories out of 96 total. If you want to go down the rabbit hole, you can [find the rest on the AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse). + +We’ll be waiting for your feedback there! Stay safe online and offline. diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/general/how-to-install.md b/i18n/fa/docusaurus-plugin-content-docs/current/general/how-to-install.md index 106a29529a8..4ba78d7a094 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/general/how-to-install.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/general/how-to-install.md @@ -1,6 +1,6 @@ --- title: How to install AdGuard -sidebar_position: 9 +sidebar_position: 10 --- Depending on which AdGuard app or browser extension you want to install, follow one of these links to find the relevant article: diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md index 3953f47d26f..05642d350b0 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md @@ -43,6 +43,14 @@ Here you can choose which proxy AdGuard should use to download filter updates or ## Use SockFilter driver -Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. +Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. If this option is disabled, AdGuard will switch to the older WFP driver instead. -If this option is disabled, AdGuard will switch to the older WFP driver instead. +SockFilter was first introduced in v8.0 RC. It is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md index 251e49cf286..1ab588bb16c 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Because of this, TDI-based traffic visibility becomes increasingly unstable. In AdGuard already treats the TDI driver as deprecated, and its complete removal is planned as the product evolves. +## Permanent solution + +From v8.0 RC, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows-8/settings/app-settings/network-settings/). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Temporary solution Certain Windows registry changes can force the browser to stop using AppContainer, causing its processes to run in a non-sandboxed mode again. Network Service stops using the WSK stack and falls back to a network path that the TDI driver can see. AdGuard then regains the ability to filter browser traffic. @@ -123,7 +131,3 @@ You should see the following policies active: If available, click _Reload policies_. Done! - -## Permanent solution - -We’re planning to add support for the SockFilter driver in the upcoming versions. It will fix the issue by solving conflicts in the WFP stack. [More information](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index 5945618ea9c..f8074e9cfa1 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -17,23 +17,35 @@ In this module you can select the checkbox _Use AdGuard as an HTTP proxy_ to use At last, there is a section with proxy settings. There you can specify which proxy server AdGuard should use to update filters, get new versions, and so on. -### SockFilter and other network drivers +### Enable traffic filtering -In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. +Traffic filtering is the core mechanism that allows AdGuard to inspect and control the network traffic generated by applications on your computer. When it is enabled, AdGuard intercepts outgoing and incoming connections and checks them against its filtering rules. If a request matches a blocking rule, AdGuard can block it, modify it, or allow it depending on the configuration. In AdGuard for Windows, this interception is implemented through network drivers. -**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. +If HTTPS filtering is enabled, AdGuard performs a controlled local TLS interception: it decrypts the traffic using its local certificate, applies filtering rules, and then re-encrypts the traffic before sending it to the browser. The driver simply provides the system-level access needed for AdGuard to intercept these connections. -The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +#### SockFilter **SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. -Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: +SockFilter was first implemented in version 7.22.4, and it is still considered unstable — you may encounter bugs. Once fully tested and implemented, SockFilter has the potential to offer several advantages over other drivers: -- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. - **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. -- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. -When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. +#### WFP + +**WFP** (Windows Filtering Platform) is a Microsoft networking framework built into Windows that allows software to filter and monitor network packets at different layers of the system networking stack. AdGuard uses WFP to safely hook into the network flow of applications and apply filtering rules before the traffic reaches the browser or the Internet. [More information](https://learn.microsoft.com/en-us/windows/win32/fwp/windows-filtering-platform-architecture-overview). + +While it is a powerful driver, it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) and lower Internet speed for some users. + +#### TDI + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. ### AdGuard VPN diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index ab90a964b9f..5699b31b033 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -44,12 +44,8 @@ Before you start manually writing your own rules read our detailed [syntax guide Many websites gather information about their visitors, such as their IP addresses, browser and operating system details, screen resolution, and the webpage from which the user came or was redirected. Some websites use cookies to mark and identify your browser, save your personal settings and preferences. This allows them to “recognize” you on your next visit. Tracking protection safeguards your personal information from these data- and statistics-gathering systems. -![Tracking protection levels \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection1.png) - You can adjust the _Tracking Protection_ settings as needed. For example, you can prevent websites from receiving the search request that you used to find them on the Internet, automatically delete third- and first-party cookies, and disable location sharing in your browser, to prevent tracking of your whereabouts. -![Tracking protection custom features \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection2.png) - To learn everything about _Tracking protection_ and its many options, [read this article](/general/stealth-mode). ### Browsing security diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md index 62370bf3eb1..bec08d0c665 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Because of this, TDI-based traffic visibility becomes increasingly unstable. In AdGuard already treats the TDI driver as deprecated, and its complete removal is planned as the product evolves. +## Permanent solution + +From v7.22.4, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows/features/network/#sockfilter-and-other-network-drivers). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Temporary solution Certain Windows registry changes can force the browser to stop using AppContainer, causing its processes to run in a non-sandboxed mode again. Network Service stops using the WSK stack and falls back to a network path that the TDI driver can see. AdGuard then regains the ability to filter browser traffic. @@ -136,7 +144,3 @@ You should see the following policies active: If available, click _Reload policies_. Done! - -## Permanent solution - -We’re planning to add support for the SockFilter driver in the upcoming versions. It will fix the issue by solving conflicts in the WFP stack. [More information](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/general/github-repos.md b/i18n/fi/docusaurus-plugin-content-docs/current/general/github-repos.md new file mode 100644 index 00000000000..dfb164c44bc --- /dev/null +++ b/i18n/fi/docusaurus-plugin-content-docs/current/general/github-repos.md @@ -0,0 +1,238 @@ +--- +title: AdGuard’s GitHub repositories +sidebar_position: 9 +--- + +At AdGuard, our goal is to make the Internet safer, more comfortable, and more transparent. This commitment is reflected not only in our product features and strict privacy policies, but also in the fact that we keep our work as open as possible. That includes actively interacting with our community. + +This is why [all of our products have public repositories](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse) — online spaces where anybody can see what we are working on, report issues directly to AdGuard developers, and even contribute to our open-source projects. The repositories cover our ad-blocking apps, filters, browser extensions, DNS solutions, VPN tools, developer utilities, and more. There are different platforms that offer such functionality, but the most popular one by far is GitHub, and all AdGuard projects are stored there. + +This article lists the most important repositories by category, summarizes the purpose of each one, and gives a simple breakdown of what users can do there. + +:::tip + +Pro tip: Creating an issue on GitHub is the most effective way to bring the attention of AdGuard developers to a problem. Just make sure to check that a similar issue doesn’t already exist and describe the problem in a comprehensive but concise way. If it does exist, you can upvote it. + +::: + +## What is Github and its repositories + +Very simply put, you can think of GitHub as sort of Google Docs for code, where multiple people can work on the same project, track changes, and see who made which updates. It provides a central, cloud-based place to store your code so it’s accessible from anywhere. It also has teamwork tools for reviewing changes, fixing issues, and merging everyone’s work smoothly. + +GitHub is widely used for open-source projects, letting anyone view the code, suggest improvements, and contribute. + +A repository (often called “repo” for short) is the most basic element of GitHub. It’s a place where you can store your code, your files, and each file’s revision history. Repositories can have multiple collaborators and can be either public or private. + +## What can you do in AdGuard’s repositories + +You can find links to key repositories below in this article or visit the [general AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all) for a full list. In most repos, you can: + +- **View README file** on the main page: it gives you an introduction to the product and its repo + ![README file \*border](https://cdn.adtidy.org/content/blog/github-repos/see-readme.png) + +- **Check existing bug reports or feature requests**, comment and upvote + ![Check issues \*border](https://cdn.adtidy.org/content/blog/github-repos/check-issues.png) + +- **Create issues** to report bugs or request features + ![Create issues \*border](https://cdn.adtidy.org/content/blog/github-repos/create-issue.png) + +- **Check releases** for different versions and their changelogs (and install an older version if needed) + ![Check releases \*border](https://cdn.adtidy.org/content/blog/github-repos/check-releases.png) + +- **Install any older or beta version** if needed + ![Download builds \*border](https://cdn.adtidy.org/content/blog/github-repos/download-releases.png) + +:::note + +If you are new to GitHub, you’ll need to create a GitHub account in order to create new issues and comment on the existing ones. + +::: + +In open-source repos advanced users can also: + +- **Browse code** to understand product logic, what technologies are used and how they are implemented +- **Fork and contribute** via pull requests + +Whether you’re a casual user, technical expert, or a developer, AdGuard welcomes all community participation across its GitHub repos. + +## Legal documents + +### [LegalDocs](https://github.com/AdguardTeam/LegalDocs) + +As part of our commitment to transparency, we host all legal documents — such as End-User License Agreements, Privacy Policies, and Terms and Conditions — on GitHub. Our _LegalDocs_ repo lets anyone check the full history of changes to these documents. + +## AdGuard Ad Blocker products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdguardForAndroid](https://github.com/AdguardTeam/AdguardForAndroid) + +Repository of AdGuard for Android — an app that provides system-wide ad blocking. + +### [AdguardForiOS](https://github.com/AdguardTeam/AdguardForiOS) + +Repository of AdGuard for iOS — Safari content blocker with DNS and custom filters. Users can also check open-source code. + +### [AdguardForWindows](https://github.com/AdguardTeam/AdguardForWindows) + +Repository of AdGuard for Windows. Non-open-source; GitHub used as an open bug tracker. + +### [AdguardForMac](https://github.com/AdguardTeam/AdguardForMac) + +Repository of AdGuard for Mac — macOS standalone content blocker. Bug tracker only. + +### [AdguardBrowserExtension](https://github.com/AdguardTeam/AdguardBrowserExtension) + +Repository of AdGuard Browser Extension — extension that provides ad blocking with enhanced privacy for Chrome, Firefox, Opera, Edge. + +### [AdguardForSafari](https://github.com/AdguardTeam/AdGuardForSafari) + +Repository of AdGuard for Safari — Safari ad blocking extension for Mac. Users can also check open-sourced code. + +### [AdGuardCLI](https://github.com/AdguardTeam/AdGuardCLI) + +Repository of AdGuard for Linux — a command‑line interface for managing ad blocking. + +## AdGuard VPN products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdGuardVPNForiOS](https://github.com/AdguardTeam/AdGuardVPNForiOS) + +Repository of AdGuard VPN for iOS. Serves as an open bug tracker. + +### [AdGuardVPNForAndroid](https://github.com/AdguardTeam/AdGuardVPNForAndroid) + +Repository of AdGuard VPN for Android. Serves as an open bug tracker. + +### [AdGuardVPNForWindows](https://github.com/AdguardTeam/AdGuardVPNForWindows) + +Repository of AdGuard VPN for Windows. Serves as an open bug tracker. + +### [AdGuardVPNForMac](https://github.com/AdguardTeam/AdGuardVPNForMac) + +Repository of AdGuard VPN for Mac — app designed for macOS. + +### [AdGuardVPNExtension](https://github.com/AdguardTeam/AdGuardVPNExtension) + +Repository of AdGuard VPN Browser Extension. + +### [AdGuardVPNCLI](https://github.com/AdguardTeam/AdGuardVPNCLI) + +Repository of AdGuard VPN for Linux — a command‑line interface for managing VPN connection. The repo acts as a bug tracker. + +## DNS-based products + +### [AdGuardDNS](https://github.com/AdguardTeam/AdGuardDNS) + +Open-source repository that is also used for tracking bugs and issues related to AdGuard DNS service. Users can: + +- View and report DNS issues +- Suggest improvements + +### [AdGuardHome](https://github.com/AdguardTeam/AdGuardHome) + +Repository of AdGuard Home — free network-wide software for blocking ads and trackers via DNS. Users can: + +- Check and file bug reports or feature requests +- Review or contribute to code +- Download and install releases + +## Documentation and Knowledge bases + +Knowledge bases are aimed to help users better understand and use AdGuard. They describe each AdGuard product in detail: from feature overviews and problem-solving guides to advanced setting manuals and API documentations. In the repositories users can: + +- Suggest corrections or edits to knowledge base articles +- Propose new articles +- Test or run the local version + +### [KnowledgeBase](https://github.com/AdguardTeam/KnowledgeBase) + +Central documentation for AdGuard Ad Blocker and the technologies related to it. + +### [KnowledgeBaseDNS](https://github.com/AdguardTeam/KnowledgeBaseDNS) + +Detailed feature overview, troubleshooting guides and documentation for AdGuard DNS (both Public and Private), AdGuard Home, and everything related to them. + +### [KnowledgeBaseVPN](https://github.com/AdguardTeam/KnowledgeBaseVPN) + +Detailed feature overview and troubleshooting guides for AdGuard VPN. + +### [KnowledgeBaseMail](https://github.com/AdguardTeam/KnowledgeBaseMail) + +Detailed feature overview and troubleshooting guides of AdGuard Mail. + +## Core libraries + +### [CoreLibs](https://github.com/AdguardTeam/CoreLibs) + +AdGuard’s cross-platform core filtering engine. Used in Android, Windows, and Mac products. Users can: + +- Explore filtering logic and DNS handling +- Report bugs and suggest features via Issues + +### [DNSLibs](https://github.com/AdguardTeam/DNSLibs) + +A DNS library used by CoreLibs and AdGuardHome. Users can: + +- Review and contribute to low-level DNS implementation +- Suggest optimizations + +### [VPNLibs](https://github.com/AdguardTeam/VPNLibs) + +Shared codebase used in AdGuard VPN products across platforms for AdGuard VPN protocol implementation. Users can: + +- Contribute to VPN stack behavior +- Report or view performance issues and bugs + +## Core ad blocking and filtering technologies + +### [AdguardFilters](https://github.com/AdguardTeam/AdguardFilters) + +Contains AdGuard’s core filter lists. Users can: + +- View and download filter lists +- Create issues to report false positives or suggest new rules +- Monitor updates to filter logic + +### [AdGuardSDNSFilter](https://github.com/AdguardTeam/AdGuardSDNSFilter) + +Repository of AdGuard DNS filter — the main DNS-level blocking list used in AdGuard DNS and DNS filtering features. Users can: + +- Inspect the current rule set +- Propose changes or additions + +### [AGLint](https://github.com/AdguardTeam/AGLint) + +A linter for adblock filter list syntax. Users can: + +- Install AGLint to check their projects for rule issues +- Contribute to lint rules + +### [Scriptlets](https://github.com/AdguardTeam/Scriptlets) + +JavaScript helpers used in filtering rules. Users can: + +- Explore available scriptlets +- Submit pull requests for new scriptlets + +### [tsurlfilter](https://github.com/AdguardTeam/tsurlfilter) + +TypeScript content blocker library for browser extensions. Users can: + +- Explore how filtering logic is implemented +- Contribute fixes and features + +## There’s more + +Above, we listed 27 main public AdGuard repositories out of 96 total. If you want to go down the rabbit hole, you can [find the rest on the AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse). + +We’ll be waiting for your feedback there! Stay safe online and offline. diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/general/how-to-install.md b/i18n/fi/docusaurus-plugin-content-docs/current/general/how-to-install.md index 106a29529a8..4ba78d7a094 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/general/how-to-install.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/general/how-to-install.md @@ -1,6 +1,6 @@ --- title: How to install AdGuard -sidebar_position: 9 +sidebar_position: 10 --- Depending on which AdGuard app or browser extension you want to install, follow one of these links to find the relevant article: diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md index c2e1c164ed7..bcd31f2462c 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md @@ -43,6 +43,14 @@ Ici, vous pouvez choisir quel proxy AdGuard doit utiliser pour télécharger les ## Utiliser le pilote SockFilter -Activez cette option pour utiliser le pilote SockFilter, qui aide à bloquer les publicités et les traqueurs dans les apps sur Windows 8 et versions ultérieures. +Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. If this option is disabled, AdGuard will switch to the older WFP driver instead. -Si cette option est désactivée, AdGuard passera au pilote WFP plus ancien. +SockFilter was first introduced in v8.0 RC. It is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md index 7552be1dbd5..ab9712a3e4c 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ De ce fait, la visibilité du trafic basée sur le TDI devient de plus en plus i AdGuard considère déjà le pilote TDI comme obsolète, et sa suppression complète est prévue à mesure que le produit évolue. +## Solution permanente + +From v8.0 RC, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows-8/settings/app-settings/network-settings/). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Solution temporaire Certaines modifications du registre Windows peuvent forcer le navigateur à cesser d'utiliser AppContainer, ce qui aura pour conséquence que ses processus s'exécutent à nouveau en mode non isolé. Le service réseau cesse d'utiliser la pile WSK et se rabat sur un chemin réseau que le pilote TDI peut voir. AdGuard retrouve alors la capacité de filtrer le trafic du navigateur. @@ -123,7 +131,3 @@ Vous devriez voir les politiques actives suivantes : Si disponible, cliquez sur _Recharger les politiques_. C'est fait ! - -## Solution permanente - -Nous prévoyons d'ajouter la prise en charge du pilote SockFilter dans les prochaines versions. Cela résoudra le problème en éliminant les conflits dans la pile WFP. [Plus d'informations](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index 1c048943a42..a4bde3af9fc 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -17,23 +17,35 @@ Dans ce module, vous pouvez cocher la case _Utiliser AdGuard comme proxy HTTP_ p Enfin, il y a une section avec les paramètres de proxy. Vous pouvez y spécifier quel serveur proxy AdGuard doit utiliser pour mettre à jour les filtres, obtenir de nouvelles versions, et ainsi de suite. -### SockFilter and other network drivers +### Enable traffic filtering -In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. +Traffic filtering is the core mechanism that allows AdGuard to inspect and control the network traffic generated by applications on your computer. When it is enabled, AdGuard intercepts outgoing and incoming connections and checks them against its filtering rules. If a request matches a blocking rule, AdGuard can block it, modify it, or allow it depending on the configuration. In AdGuard for Windows, this interception is implemented through network drivers. -**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. +If HTTPS filtering is enabled, AdGuard performs a controlled local TLS interception: it decrypts the traffic using its local certificate, applies filtering rules, and then re-encrypts the traffic before sending it to the browser. The driver simply provides the system-level access needed for AdGuard to intercept these connections. -The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +#### SockFilter **SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. -Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: +SockFilter was first implemented in version 7.22.4, and it is still considered unstable — you may encounter bugs. Once fully tested and implemented, SockFilter has the potential to offer several advantages over other drivers: -- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. - **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. -- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. -When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. +#### WFP + +**WFP** (Windows Filtering Platform) is a Microsoft networking framework built into Windows that allows software to filter and monitor network packets at different layers of the system networking stack. AdGuard uses WFP to safely hook into the network flow of applications and apply filtering rules before the traffic reaches the browser or the Internet. [More information](https://learn.microsoft.com/en-us/windows/win32/fwp/windows-filtering-platform-architecture-overview). + +While it is a powerful driver, it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) and lower Internet speed for some users. + +#### TDI + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. ### AdGuard VPN diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index 64bb6b0aeae..a26a655bb3c 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -44,12 +44,8 @@ Avant de commencer à écrire vos propres règles manuellement, lisez notre [gui Many websites gather information about their visitors, such as their IP addresses, browser and operating system details, screen resolution, and the webpage from which the user came or was redirected. Some websites use cookies to mark and identify your browser, save your personal settings and preferences. This allows them to “recognize” you on your next visit. Tracking protection safeguards your personal information from these data- and statistics-gathering systems. -![Tracking protection levels \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection1.png) - You can adjust the _Tracking Protection_ settings as needed. For example, you can prevent websites from receiving the search request that you used to find them on the Internet, automatically delete third- and first-party cookies, and disable location sharing in your browser, to prevent tracking of your whereabouts. -![Tracking protection custom features \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection2.png) - To learn everything about _Tracking protection_ and its many options, [read this article](/general/stealth-mode). ### Navigation sécurisée diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md index c4800373c6c..07ffb3d9673 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Because of this, TDI-based traffic visibility becomes increasingly unstable. In AdGuard already treats the TDI driver as deprecated, and its complete removal is planned as the product evolves. +## Permanent solution + +From v7.22.4, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows/features/network/#sockfilter-and-other-network-drivers). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Temporary solution Certain Windows registry changes can force the browser to stop using AppContainer, causing its processes to run in a non-sandboxed mode again. Network Service stops using the WSK stack and falls back to a network path that the TDI driver can see. AdGuard then regains the ability to filter browser traffic. @@ -136,7 +144,3 @@ You should see the following policies active: If available, click _Reload policies_. C'est fait ! - -## Permanent solution - -We’re planning to add support for the SockFilter driver in the upcoming versions. It will fix the issue by solving conflicts in the WFP stack. [More information](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/general/github-repos.md b/i18n/fr/docusaurus-plugin-content-docs/current/general/github-repos.md new file mode 100644 index 00000000000..dfb164c44bc --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/current/general/github-repos.md @@ -0,0 +1,238 @@ +--- +title: AdGuard’s GitHub repositories +sidebar_position: 9 +--- + +At AdGuard, our goal is to make the Internet safer, more comfortable, and more transparent. This commitment is reflected not only in our product features and strict privacy policies, but also in the fact that we keep our work as open as possible. That includes actively interacting with our community. + +This is why [all of our products have public repositories](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse) — online spaces where anybody can see what we are working on, report issues directly to AdGuard developers, and even contribute to our open-source projects. The repositories cover our ad-blocking apps, filters, browser extensions, DNS solutions, VPN tools, developer utilities, and more. There are different platforms that offer such functionality, but the most popular one by far is GitHub, and all AdGuard projects are stored there. + +This article lists the most important repositories by category, summarizes the purpose of each one, and gives a simple breakdown of what users can do there. + +:::tip + +Pro tip: Creating an issue on GitHub is the most effective way to bring the attention of AdGuard developers to a problem. Just make sure to check that a similar issue doesn’t already exist and describe the problem in a comprehensive but concise way. If it does exist, you can upvote it. + +::: + +## What is Github and its repositories + +Very simply put, you can think of GitHub as sort of Google Docs for code, where multiple people can work on the same project, track changes, and see who made which updates. It provides a central, cloud-based place to store your code so it’s accessible from anywhere. It also has teamwork tools for reviewing changes, fixing issues, and merging everyone’s work smoothly. + +GitHub is widely used for open-source projects, letting anyone view the code, suggest improvements, and contribute. + +A repository (often called “repo” for short) is the most basic element of GitHub. It’s a place where you can store your code, your files, and each file’s revision history. Repositories can have multiple collaborators and can be either public or private. + +## What can you do in AdGuard’s repositories + +You can find links to key repositories below in this article or visit the [general AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all) for a full list. In most repos, you can: + +- **View README file** on the main page: it gives you an introduction to the product and its repo + ![README file \*border](https://cdn.adtidy.org/content/blog/github-repos/see-readme.png) + +- **Check existing bug reports or feature requests**, comment and upvote + ![Check issues \*border](https://cdn.adtidy.org/content/blog/github-repos/check-issues.png) + +- **Create issues** to report bugs or request features + ![Create issues \*border](https://cdn.adtidy.org/content/blog/github-repos/create-issue.png) + +- **Check releases** for different versions and their changelogs (and install an older version if needed) + ![Check releases \*border](https://cdn.adtidy.org/content/blog/github-repos/check-releases.png) + +- **Install any older or beta version** if needed + ![Download builds \*border](https://cdn.adtidy.org/content/blog/github-repos/download-releases.png) + +:::note + +If you are new to GitHub, you’ll need to create a GitHub account in order to create new issues and comment on the existing ones. + +::: + +In open-source repos advanced users can also: + +- **Browse code** to understand product logic, what technologies are used and how they are implemented +- **Fork and contribute** via pull requests + +Whether you’re a casual user, technical expert, or a developer, AdGuard welcomes all community participation across its GitHub repos. + +## Legal documents + +### [LegalDocs](https://github.com/AdguardTeam/LegalDocs) + +As part of our commitment to transparency, we host all legal documents — such as End-User License Agreements, Privacy Policies, and Terms and Conditions — on GitHub. Our _LegalDocs_ repo lets anyone check the full history of changes to these documents. + +## AdGuard Ad Blocker products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdguardForAndroid](https://github.com/AdguardTeam/AdguardForAndroid) + +Repository of AdGuard for Android — an app that provides system-wide ad blocking. + +### [AdguardForiOS](https://github.com/AdguardTeam/AdguardForiOS) + +Repository of AdGuard for iOS — Safari content blocker with DNS and custom filters. Users can also check open-source code. + +### [AdguardForWindows](https://github.com/AdguardTeam/AdguardForWindows) + +Repository of AdGuard for Windows. Non-open-source; GitHub used as an open bug tracker. + +### [AdguardForMac](https://github.com/AdguardTeam/AdguardForMac) + +Repository of AdGuard for Mac — macOS standalone content blocker. Bug tracker only. + +### [AdguardBrowserExtension](https://github.com/AdguardTeam/AdguardBrowserExtension) + +Repository of AdGuard Browser Extension — extension that provides ad blocking with enhanced privacy for Chrome, Firefox, Opera, Edge. + +### [AdguardForSafari](https://github.com/AdguardTeam/AdGuardForSafari) + +Repository of AdGuard for Safari — Safari ad blocking extension for Mac. Users can also check open-sourced code. + +### [AdGuardCLI](https://github.com/AdguardTeam/AdGuardCLI) + +Repository of AdGuard for Linux — a command‑line interface for managing ad blocking. + +## AdGuard VPN products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdGuardVPNForiOS](https://github.com/AdguardTeam/AdGuardVPNForiOS) + +Repository of AdGuard VPN for iOS. Serves as an open bug tracker. + +### [AdGuardVPNForAndroid](https://github.com/AdguardTeam/AdGuardVPNForAndroid) + +Repository of AdGuard VPN for Android. Serves as an open bug tracker. + +### [AdGuardVPNForWindows](https://github.com/AdguardTeam/AdGuardVPNForWindows) + +Repository of AdGuard VPN for Windows. Serves as an open bug tracker. + +### [AdGuardVPNForMac](https://github.com/AdguardTeam/AdGuardVPNForMac) + +Repository of AdGuard VPN for Mac — app designed for macOS. + +### [AdGuardVPNExtension](https://github.com/AdguardTeam/AdGuardVPNExtension) + +Repository of AdGuard VPN Browser Extension. + +### [AdGuardVPNCLI](https://github.com/AdguardTeam/AdGuardVPNCLI) + +Repository of AdGuard VPN for Linux — a command‑line interface for managing VPN connection. The repo acts as a bug tracker. + +## DNS-based products + +### [AdGuardDNS](https://github.com/AdguardTeam/AdGuardDNS) + +Open-source repository that is also used for tracking bugs and issues related to AdGuard DNS service. Users can: + +- View and report DNS issues +- Suggest improvements + +### [AdGuardHome](https://github.com/AdguardTeam/AdGuardHome) + +Repository of AdGuard Home — free network-wide software for blocking ads and trackers via DNS. Users can: + +- Check and file bug reports or feature requests +- Review or contribute to code +- Download and install releases + +## Documentation and Knowledge bases + +Knowledge bases are aimed to help users better understand and use AdGuard. They describe each AdGuard product in detail: from feature overviews and problem-solving guides to advanced setting manuals and API documentations. In the repositories users can: + +- Suggest corrections or edits to knowledge base articles +- Propose new articles +- Test or run the local version + +### [KnowledgeBase](https://github.com/AdguardTeam/KnowledgeBase) + +Central documentation for AdGuard Ad Blocker and the technologies related to it. + +### [KnowledgeBaseDNS](https://github.com/AdguardTeam/KnowledgeBaseDNS) + +Detailed feature overview, troubleshooting guides and documentation for AdGuard DNS (both Public and Private), AdGuard Home, and everything related to them. + +### [KnowledgeBaseVPN](https://github.com/AdguardTeam/KnowledgeBaseVPN) + +Detailed feature overview and troubleshooting guides for AdGuard VPN. + +### [KnowledgeBaseMail](https://github.com/AdguardTeam/KnowledgeBaseMail) + +Detailed feature overview and troubleshooting guides of AdGuard Mail. + +## Core libraries + +### [CoreLibs](https://github.com/AdguardTeam/CoreLibs) + +AdGuard’s cross-platform core filtering engine. Used in Android, Windows, and Mac products. Users can: + +- Explore filtering logic and DNS handling +- Report bugs and suggest features via Issues + +### [DNSLibs](https://github.com/AdguardTeam/DNSLibs) + +A DNS library used by CoreLibs and AdGuardHome. Users can: + +- Review and contribute to low-level DNS implementation +- Suggest optimizations + +### [VPNLibs](https://github.com/AdguardTeam/VPNLibs) + +Shared codebase used in AdGuard VPN products across platforms for AdGuard VPN protocol implementation. Users can: + +- Contribute to VPN stack behavior +- Report or view performance issues and bugs + +## Core ad blocking and filtering technologies + +### [AdguardFilters](https://github.com/AdguardTeam/AdguardFilters) + +Contains AdGuard’s core filter lists. Users can: + +- View and download filter lists +- Create issues to report false positives or suggest new rules +- Monitor updates to filter logic + +### [AdGuardSDNSFilter](https://github.com/AdguardTeam/AdGuardSDNSFilter) + +Repository of AdGuard DNS filter — the main DNS-level blocking list used in AdGuard DNS and DNS filtering features. Users can: + +- Inspect the current rule set +- Propose changes or additions + +### [AGLint](https://github.com/AdguardTeam/AGLint) + +A linter for adblock filter list syntax. Users can: + +- Install AGLint to check their projects for rule issues +- Contribute to lint rules + +### [Scriptlets](https://github.com/AdguardTeam/Scriptlets) + +JavaScript helpers used in filtering rules. Users can: + +- Explore available scriptlets +- Submit pull requests for new scriptlets + +### [tsurlfilter](https://github.com/AdguardTeam/tsurlfilter) + +TypeScript content blocker library for browser extensions. Users can: + +- Explore how filtering logic is implemented +- Contribute fixes and features + +## There’s more + +Above, we listed 27 main public AdGuard repositories out of 96 total. If you want to go down the rabbit hole, you can [find the rest on the AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse). + +We’ll be waiting for your feedback there! Stay safe online and offline. diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/general/how-to-install.md b/i18n/fr/docusaurus-plugin-content-docs/current/general/how-to-install.md index 6a3eca6e7e5..67d55ec4ca5 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/general/how-to-install.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/general/how-to-install.md @@ -1,6 +1,6 @@ --- title: Comment installer AdGuard -sidebar_position: 9 +sidebar_position: 10 --- Selon l'application AdGuard ou l'extension de navigateur que vous souhaitez installer, suivez l'un de ces liens pour trouver l'article correspondant : diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md index 3953f47d26f..05642d350b0 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md @@ -43,6 +43,14 @@ Here you can choose which proxy AdGuard should use to download filter updates or ## Use SockFilter driver -Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. +Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. If this option is disabled, AdGuard will switch to the older WFP driver instead. -If this option is disabled, AdGuard will switch to the older WFP driver instead. +SockFilter was first introduced in v8.0 RC. It is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md index 251e49cf286..1ab588bb16c 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Because of this, TDI-based traffic visibility becomes increasingly unstable. In AdGuard already treats the TDI driver as deprecated, and its complete removal is planned as the product evolves. +## Permanent solution + +From v8.0 RC, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows-8/settings/app-settings/network-settings/). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Temporary solution Certain Windows registry changes can force the browser to stop using AppContainer, causing its processes to run in a non-sandboxed mode again. Network Service stops using the WSK stack and falls back to a network path that the TDI driver can see. AdGuard then regains the ability to filter browser traffic. @@ -123,7 +131,3 @@ You should see the following policies active: If available, click _Reload policies_. Done! - -## Permanent solution - -We’re planning to add support for the SockFilter driver in the upcoming versions. It will fix the issue by solving conflicts in the WFP stack. [More information](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index 5945618ea9c..f8074e9cfa1 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -17,23 +17,35 @@ In this module you can select the checkbox _Use AdGuard as an HTTP proxy_ to use At last, there is a section with proxy settings. There you can specify which proxy server AdGuard should use to update filters, get new versions, and so on. -### SockFilter and other network drivers +### Enable traffic filtering -In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. +Traffic filtering is the core mechanism that allows AdGuard to inspect and control the network traffic generated by applications on your computer. When it is enabled, AdGuard intercepts outgoing and incoming connections and checks them against its filtering rules. If a request matches a blocking rule, AdGuard can block it, modify it, or allow it depending on the configuration. In AdGuard for Windows, this interception is implemented through network drivers. -**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. +If HTTPS filtering is enabled, AdGuard performs a controlled local TLS interception: it decrypts the traffic using its local certificate, applies filtering rules, and then re-encrypts the traffic before sending it to the browser. The driver simply provides the system-level access needed for AdGuard to intercept these connections. -The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +#### SockFilter **SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. -Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: +SockFilter was first implemented in version 7.22.4, and it is still considered unstable — you may encounter bugs. Once fully tested and implemented, SockFilter has the potential to offer several advantages over other drivers: -- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. - **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. -- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. -When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. +#### WFP + +**WFP** (Windows Filtering Platform) is a Microsoft networking framework built into Windows that allows software to filter and monitor network packets at different layers of the system networking stack. AdGuard uses WFP to safely hook into the network flow of applications and apply filtering rules before the traffic reaches the browser or the Internet. [More information](https://learn.microsoft.com/en-us/windows/win32/fwp/windows-filtering-platform-architecture-overview). + +While it is a powerful driver, it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) and lower Internet speed for some users. + +#### TDI + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. ### AdGuard VPN diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index ab90a964b9f..5699b31b033 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -44,12 +44,8 @@ Before you start manually writing your own rules read our detailed [syntax guide Many websites gather information about their visitors, such as their IP addresses, browser and operating system details, screen resolution, and the webpage from which the user came or was redirected. Some websites use cookies to mark and identify your browser, save your personal settings and preferences. This allows them to “recognize” you on your next visit. Tracking protection safeguards your personal information from these data- and statistics-gathering systems. -![Tracking protection levels \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection1.png) - You can adjust the _Tracking Protection_ settings as needed. For example, you can prevent websites from receiving the search request that you used to find them on the Internet, automatically delete third- and first-party cookies, and disable location sharing in your browser, to prevent tracking of your whereabouts. -![Tracking protection custom features \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection2.png) - To learn everything about _Tracking protection_ and its many options, [read this article](/general/stealth-mode). ### Browsing security diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md index 62370bf3eb1..bec08d0c665 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Because of this, TDI-based traffic visibility becomes increasingly unstable. In AdGuard already treats the TDI driver as deprecated, and its complete removal is planned as the product evolves. +## Permanent solution + +From v7.22.4, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows/features/network/#sockfilter-and-other-network-drivers). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Temporary solution Certain Windows registry changes can force the browser to stop using AppContainer, causing its processes to run in a non-sandboxed mode again. Network Service stops using the WSK stack and falls back to a network path that the TDI driver can see. AdGuard then regains the ability to filter browser traffic. @@ -136,7 +144,3 @@ You should see the following policies active: If available, click _Reload policies_. Done! - -## Permanent solution - -We’re planning to add support for the SockFilter driver in the upcoming versions. It will fix the issue by solving conflicts in the WFP stack. [More information](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/general/github-repos.md b/i18n/hr/docusaurus-plugin-content-docs/current/general/github-repos.md new file mode 100644 index 00000000000..dfb164c44bc --- /dev/null +++ b/i18n/hr/docusaurus-plugin-content-docs/current/general/github-repos.md @@ -0,0 +1,238 @@ +--- +title: AdGuard’s GitHub repositories +sidebar_position: 9 +--- + +At AdGuard, our goal is to make the Internet safer, more comfortable, and more transparent. This commitment is reflected not only in our product features and strict privacy policies, but also in the fact that we keep our work as open as possible. That includes actively interacting with our community. + +This is why [all of our products have public repositories](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse) — online spaces where anybody can see what we are working on, report issues directly to AdGuard developers, and even contribute to our open-source projects. The repositories cover our ad-blocking apps, filters, browser extensions, DNS solutions, VPN tools, developer utilities, and more. There are different platforms that offer such functionality, but the most popular one by far is GitHub, and all AdGuard projects are stored there. + +This article lists the most important repositories by category, summarizes the purpose of each one, and gives a simple breakdown of what users can do there. + +:::tip + +Pro tip: Creating an issue on GitHub is the most effective way to bring the attention of AdGuard developers to a problem. Just make sure to check that a similar issue doesn’t already exist and describe the problem in a comprehensive but concise way. If it does exist, you can upvote it. + +::: + +## What is Github and its repositories + +Very simply put, you can think of GitHub as sort of Google Docs for code, where multiple people can work on the same project, track changes, and see who made which updates. It provides a central, cloud-based place to store your code so it’s accessible from anywhere. It also has teamwork tools for reviewing changes, fixing issues, and merging everyone’s work smoothly. + +GitHub is widely used for open-source projects, letting anyone view the code, suggest improvements, and contribute. + +A repository (often called “repo” for short) is the most basic element of GitHub. It’s a place where you can store your code, your files, and each file’s revision history. Repositories can have multiple collaborators and can be either public or private. + +## What can you do in AdGuard’s repositories + +You can find links to key repositories below in this article or visit the [general AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all) for a full list. In most repos, you can: + +- **View README file** on the main page: it gives you an introduction to the product and its repo + ![README file \*border](https://cdn.adtidy.org/content/blog/github-repos/see-readme.png) + +- **Check existing bug reports or feature requests**, comment and upvote + ![Check issues \*border](https://cdn.adtidy.org/content/blog/github-repos/check-issues.png) + +- **Create issues** to report bugs or request features + ![Create issues \*border](https://cdn.adtidy.org/content/blog/github-repos/create-issue.png) + +- **Check releases** for different versions and their changelogs (and install an older version if needed) + ![Check releases \*border](https://cdn.adtidy.org/content/blog/github-repos/check-releases.png) + +- **Install any older or beta version** if needed + ![Download builds \*border](https://cdn.adtidy.org/content/blog/github-repos/download-releases.png) + +:::note + +If you are new to GitHub, you’ll need to create a GitHub account in order to create new issues and comment on the existing ones. + +::: + +In open-source repos advanced users can also: + +- **Browse code** to understand product logic, what technologies are used and how they are implemented +- **Fork and contribute** via pull requests + +Whether you’re a casual user, technical expert, or a developer, AdGuard welcomes all community participation across its GitHub repos. + +## Legal documents + +### [LegalDocs](https://github.com/AdguardTeam/LegalDocs) + +As part of our commitment to transparency, we host all legal documents — such as End-User License Agreements, Privacy Policies, and Terms and Conditions — on GitHub. Our _LegalDocs_ repo lets anyone check the full history of changes to these documents. + +## AdGuard Ad Blocker products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdguardForAndroid](https://github.com/AdguardTeam/AdguardForAndroid) + +Repository of AdGuard for Android — an app that provides system-wide ad blocking. + +### [AdguardForiOS](https://github.com/AdguardTeam/AdguardForiOS) + +Repository of AdGuard for iOS — Safari content blocker with DNS and custom filters. Users can also check open-source code. + +### [AdguardForWindows](https://github.com/AdguardTeam/AdguardForWindows) + +Repository of AdGuard for Windows. Non-open-source; GitHub used as an open bug tracker. + +### [AdguardForMac](https://github.com/AdguardTeam/AdguardForMac) + +Repository of AdGuard for Mac — macOS standalone content blocker. Bug tracker only. + +### [AdguardBrowserExtension](https://github.com/AdguardTeam/AdguardBrowserExtension) + +Repository of AdGuard Browser Extension — extension that provides ad blocking with enhanced privacy for Chrome, Firefox, Opera, Edge. + +### [AdguardForSafari](https://github.com/AdguardTeam/AdGuardForSafari) + +Repository of AdGuard for Safari — Safari ad blocking extension for Mac. Users can also check open-sourced code. + +### [AdGuardCLI](https://github.com/AdguardTeam/AdGuardCLI) + +Repository of AdGuard for Linux — a command‑line interface for managing ad blocking. + +## AdGuard VPN products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdGuardVPNForiOS](https://github.com/AdguardTeam/AdGuardVPNForiOS) + +Repository of AdGuard VPN for iOS. Serves as an open bug tracker. + +### [AdGuardVPNForAndroid](https://github.com/AdguardTeam/AdGuardVPNForAndroid) + +Repository of AdGuard VPN for Android. Serves as an open bug tracker. + +### [AdGuardVPNForWindows](https://github.com/AdguardTeam/AdGuardVPNForWindows) + +Repository of AdGuard VPN for Windows. Serves as an open bug tracker. + +### [AdGuardVPNForMac](https://github.com/AdguardTeam/AdGuardVPNForMac) + +Repository of AdGuard VPN for Mac — app designed for macOS. + +### [AdGuardVPNExtension](https://github.com/AdguardTeam/AdGuardVPNExtension) + +Repository of AdGuard VPN Browser Extension. + +### [AdGuardVPNCLI](https://github.com/AdguardTeam/AdGuardVPNCLI) + +Repository of AdGuard VPN for Linux — a command‑line interface for managing VPN connection. The repo acts as a bug tracker. + +## DNS-based products + +### [AdGuardDNS](https://github.com/AdguardTeam/AdGuardDNS) + +Open-source repository that is also used for tracking bugs and issues related to AdGuard DNS service. Users can: + +- View and report DNS issues +- Suggest improvements + +### [AdGuardHome](https://github.com/AdguardTeam/AdGuardHome) + +Repository of AdGuard Home — free network-wide software for blocking ads and trackers via DNS. Users can: + +- Check and file bug reports or feature requests +- Review or contribute to code +- Download and install releases + +## Documentation and Knowledge bases + +Knowledge bases are aimed to help users better understand and use AdGuard. They describe each AdGuard product in detail: from feature overviews and problem-solving guides to advanced setting manuals and API documentations. In the repositories users can: + +- Suggest corrections or edits to knowledge base articles +- Propose new articles +- Test or run the local version + +### [KnowledgeBase](https://github.com/AdguardTeam/KnowledgeBase) + +Central documentation for AdGuard Ad Blocker and the technologies related to it. + +### [KnowledgeBaseDNS](https://github.com/AdguardTeam/KnowledgeBaseDNS) + +Detailed feature overview, troubleshooting guides and documentation for AdGuard DNS (both Public and Private), AdGuard Home, and everything related to them. + +### [KnowledgeBaseVPN](https://github.com/AdguardTeam/KnowledgeBaseVPN) + +Detailed feature overview and troubleshooting guides for AdGuard VPN. + +### [KnowledgeBaseMail](https://github.com/AdguardTeam/KnowledgeBaseMail) + +Detailed feature overview and troubleshooting guides of AdGuard Mail. + +## Core libraries + +### [CoreLibs](https://github.com/AdguardTeam/CoreLibs) + +AdGuard’s cross-platform core filtering engine. Used in Android, Windows, and Mac products. Users can: + +- Explore filtering logic and DNS handling +- Report bugs and suggest features via Issues + +### [DNSLibs](https://github.com/AdguardTeam/DNSLibs) + +A DNS library used by CoreLibs and AdGuardHome. Users can: + +- Review and contribute to low-level DNS implementation +- Suggest optimizations + +### [VPNLibs](https://github.com/AdguardTeam/VPNLibs) + +Shared codebase used in AdGuard VPN products across platforms for AdGuard VPN protocol implementation. Users can: + +- Contribute to VPN stack behavior +- Report or view performance issues and bugs + +## Core ad blocking and filtering technologies + +### [AdguardFilters](https://github.com/AdguardTeam/AdguardFilters) + +Contains AdGuard’s core filter lists. Users can: + +- View and download filter lists +- Create issues to report false positives or suggest new rules +- Monitor updates to filter logic + +### [AdGuardSDNSFilter](https://github.com/AdguardTeam/AdGuardSDNSFilter) + +Repository of AdGuard DNS filter — the main DNS-level blocking list used in AdGuard DNS and DNS filtering features. Users can: + +- Inspect the current rule set +- Propose changes or additions + +### [AGLint](https://github.com/AdguardTeam/AGLint) + +A linter for adblock filter list syntax. Users can: + +- Install AGLint to check their projects for rule issues +- Contribute to lint rules + +### [Scriptlets](https://github.com/AdguardTeam/Scriptlets) + +JavaScript helpers used in filtering rules. Users can: + +- Explore available scriptlets +- Submit pull requests for new scriptlets + +### [tsurlfilter](https://github.com/AdguardTeam/tsurlfilter) + +TypeScript content blocker library for browser extensions. Users can: + +- Explore how filtering logic is implemented +- Contribute fixes and features + +## There’s more + +Above, we listed 27 main public AdGuard repositories out of 96 total. If you want to go down the rabbit hole, you can [find the rest on the AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse). + +We’ll be waiting for your feedback there! Stay safe online and offline. diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/general/how-to-install.md b/i18n/hr/docusaurus-plugin-content-docs/current/general/how-to-install.md index 106a29529a8..4ba78d7a094 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/general/how-to-install.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/general/how-to-install.md @@ -1,6 +1,6 @@ --- title: How to install AdGuard -sidebar_position: 9 +sidebar_position: 10 --- Depending on which AdGuard app or browser extension you want to install, follow one of these links to find the relevant article: diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md index 16168d18402..0d80225d9e1 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md @@ -43,6 +43,14 @@ Here you can choose which proxy AdGuard should use to download filter updates or ## Use SockFilter driver -Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. +Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. If this option is disabled, AdGuard will switch to the older WFP driver instead. -If this option is disabled, AdGuard will switch to the older WFP driver instead. +SockFilter was first introduced in v8.0 RC. It is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md index 251e49cf286..1ab588bb16c 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Because of this, TDI-based traffic visibility becomes increasingly unstable. In AdGuard already treats the TDI driver as deprecated, and its complete removal is planned as the product evolves. +## Permanent solution + +From v8.0 RC, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows-8/settings/app-settings/network-settings/). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Temporary solution Certain Windows registry changes can force the browser to stop using AppContainer, causing its processes to run in a non-sandboxed mode again. Network Service stops using the WSK stack and falls back to a network path that the TDI driver can see. AdGuard then regains the ability to filter browser traffic. @@ -123,7 +131,3 @@ You should see the following policies active: If available, click _Reload policies_. Done! - -## Permanent solution - -We’re planning to add support for the SockFilter driver in the upcoming versions. It will fix the issue by solving conflicts in the WFP stack. [More information](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index 5945618ea9c..f8074e9cfa1 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -17,23 +17,35 @@ In this module you can select the checkbox _Use AdGuard as an HTTP proxy_ to use At last, there is a section with proxy settings. There you can specify which proxy server AdGuard should use to update filters, get new versions, and so on. -### SockFilter and other network drivers +### Enable traffic filtering -In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. +Traffic filtering is the core mechanism that allows AdGuard to inspect and control the network traffic generated by applications on your computer. When it is enabled, AdGuard intercepts outgoing and incoming connections and checks them against its filtering rules. If a request matches a blocking rule, AdGuard can block it, modify it, or allow it depending on the configuration. In AdGuard for Windows, this interception is implemented through network drivers. -**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. +If HTTPS filtering is enabled, AdGuard performs a controlled local TLS interception: it decrypts the traffic using its local certificate, applies filtering rules, and then re-encrypts the traffic before sending it to the browser. The driver simply provides the system-level access needed for AdGuard to intercept these connections. -The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +#### SockFilter **SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. -Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: +SockFilter was first implemented in version 7.22.4, and it is still considered unstable — you may encounter bugs. Once fully tested and implemented, SockFilter has the potential to offer several advantages over other drivers: -- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. - **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. -- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. -When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. +#### WFP + +**WFP** (Windows Filtering Platform) is a Microsoft networking framework built into Windows that allows software to filter and monitor network packets at different layers of the system networking stack. AdGuard uses WFP to safely hook into the network flow of applications and apply filtering rules before the traffic reaches the browser or the Internet. [More information](https://learn.microsoft.com/en-us/windows/win32/fwp/windows-filtering-platform-architecture-overview). + +While it is a powerful driver, it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) and lower Internet speed for some users. + +#### TDI + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. ### AdGuard VPN diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index ab90a964b9f..5699b31b033 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -44,12 +44,8 @@ Before you start manually writing your own rules read our detailed [syntax guide Many websites gather information about their visitors, such as their IP addresses, browser and operating system details, screen resolution, and the webpage from which the user came or was redirected. Some websites use cookies to mark and identify your browser, save your personal settings and preferences. This allows them to “recognize” you on your next visit. Tracking protection safeguards your personal information from these data- and statistics-gathering systems. -![Tracking protection levels \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection1.png) - You can adjust the _Tracking Protection_ settings as needed. For example, you can prevent websites from receiving the search request that you used to find them on the Internet, automatically delete third- and first-party cookies, and disable location sharing in your browser, to prevent tracking of your whereabouts. -![Tracking protection custom features \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection2.png) - To learn everything about _Tracking protection_ and its many options, [read this article](/general/stealth-mode). ### Browsing security diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md index 62370bf3eb1..bec08d0c665 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Because of this, TDI-based traffic visibility becomes increasingly unstable. In AdGuard already treats the TDI driver as deprecated, and its complete removal is planned as the product evolves. +## Permanent solution + +From v7.22.4, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows/features/network/#sockfilter-and-other-network-drivers). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Temporary solution Certain Windows registry changes can force the browser to stop using AppContainer, causing its processes to run in a non-sandboxed mode again. Network Service stops using the WSK stack and falls back to a network path that the TDI driver can see. AdGuard then regains the ability to filter browser traffic. @@ -136,7 +144,3 @@ You should see the following policies active: If available, click _Reload policies_. Done! - -## Permanent solution - -We’re planning to add support for the SockFilter driver in the upcoming versions. It will fix the issue by solving conflicts in the WFP stack. [More information](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/general/github-repos.md b/i18n/hu/docusaurus-plugin-content-docs/current/general/github-repos.md new file mode 100644 index 00000000000..dfb164c44bc --- /dev/null +++ b/i18n/hu/docusaurus-plugin-content-docs/current/general/github-repos.md @@ -0,0 +1,238 @@ +--- +title: AdGuard’s GitHub repositories +sidebar_position: 9 +--- + +At AdGuard, our goal is to make the Internet safer, more comfortable, and more transparent. This commitment is reflected not only in our product features and strict privacy policies, but also in the fact that we keep our work as open as possible. That includes actively interacting with our community. + +This is why [all of our products have public repositories](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse) — online spaces where anybody can see what we are working on, report issues directly to AdGuard developers, and even contribute to our open-source projects. The repositories cover our ad-blocking apps, filters, browser extensions, DNS solutions, VPN tools, developer utilities, and more. There are different platforms that offer such functionality, but the most popular one by far is GitHub, and all AdGuard projects are stored there. + +This article lists the most important repositories by category, summarizes the purpose of each one, and gives a simple breakdown of what users can do there. + +:::tip + +Pro tip: Creating an issue on GitHub is the most effective way to bring the attention of AdGuard developers to a problem. Just make sure to check that a similar issue doesn’t already exist and describe the problem in a comprehensive but concise way. If it does exist, you can upvote it. + +::: + +## What is Github and its repositories + +Very simply put, you can think of GitHub as sort of Google Docs for code, where multiple people can work on the same project, track changes, and see who made which updates. It provides a central, cloud-based place to store your code so it’s accessible from anywhere. It also has teamwork tools for reviewing changes, fixing issues, and merging everyone’s work smoothly. + +GitHub is widely used for open-source projects, letting anyone view the code, suggest improvements, and contribute. + +A repository (often called “repo” for short) is the most basic element of GitHub. It’s a place where you can store your code, your files, and each file’s revision history. Repositories can have multiple collaborators and can be either public or private. + +## What can you do in AdGuard’s repositories + +You can find links to key repositories below in this article or visit the [general AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all) for a full list. In most repos, you can: + +- **View README file** on the main page: it gives you an introduction to the product and its repo + ![README file \*border](https://cdn.adtidy.org/content/blog/github-repos/see-readme.png) + +- **Check existing bug reports or feature requests**, comment and upvote + ![Check issues \*border](https://cdn.adtidy.org/content/blog/github-repos/check-issues.png) + +- **Create issues** to report bugs or request features + ![Create issues \*border](https://cdn.adtidy.org/content/blog/github-repos/create-issue.png) + +- **Check releases** for different versions and their changelogs (and install an older version if needed) + ![Check releases \*border](https://cdn.adtidy.org/content/blog/github-repos/check-releases.png) + +- **Install any older or beta version** if needed + ![Download builds \*border](https://cdn.adtidy.org/content/blog/github-repos/download-releases.png) + +:::note + +If you are new to GitHub, you’ll need to create a GitHub account in order to create new issues and comment on the existing ones. + +::: + +In open-source repos advanced users can also: + +- **Browse code** to understand product logic, what technologies are used and how they are implemented +- **Fork and contribute** via pull requests + +Whether you’re a casual user, technical expert, or a developer, AdGuard welcomes all community participation across its GitHub repos. + +## Legal documents + +### [LegalDocs](https://github.com/AdguardTeam/LegalDocs) + +As part of our commitment to transparency, we host all legal documents — such as End-User License Agreements, Privacy Policies, and Terms and Conditions — on GitHub. Our _LegalDocs_ repo lets anyone check the full history of changes to these documents. + +## AdGuard Ad Blocker products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdguardForAndroid](https://github.com/AdguardTeam/AdguardForAndroid) + +Repository of AdGuard for Android — an app that provides system-wide ad blocking. + +### [AdguardForiOS](https://github.com/AdguardTeam/AdguardForiOS) + +Repository of AdGuard for iOS — Safari content blocker with DNS and custom filters. Users can also check open-source code. + +### [AdguardForWindows](https://github.com/AdguardTeam/AdguardForWindows) + +Repository of AdGuard for Windows. Non-open-source; GitHub used as an open bug tracker. + +### [AdguardForMac](https://github.com/AdguardTeam/AdguardForMac) + +Repository of AdGuard for Mac — macOS standalone content blocker. Bug tracker only. + +### [AdguardBrowserExtension](https://github.com/AdguardTeam/AdguardBrowserExtension) + +Repository of AdGuard Browser Extension — extension that provides ad blocking with enhanced privacy for Chrome, Firefox, Opera, Edge. + +### [AdguardForSafari](https://github.com/AdguardTeam/AdGuardForSafari) + +Repository of AdGuard for Safari — Safari ad blocking extension for Mac. Users can also check open-sourced code. + +### [AdGuardCLI](https://github.com/AdguardTeam/AdGuardCLI) + +Repository of AdGuard for Linux — a command‑line interface for managing ad blocking. + +## AdGuard VPN products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdGuardVPNForiOS](https://github.com/AdguardTeam/AdGuardVPNForiOS) + +Repository of AdGuard VPN for iOS. Serves as an open bug tracker. + +### [AdGuardVPNForAndroid](https://github.com/AdguardTeam/AdGuardVPNForAndroid) + +Repository of AdGuard VPN for Android. Serves as an open bug tracker. + +### [AdGuardVPNForWindows](https://github.com/AdguardTeam/AdGuardVPNForWindows) + +Repository of AdGuard VPN for Windows. Serves as an open bug tracker. + +### [AdGuardVPNForMac](https://github.com/AdguardTeam/AdGuardVPNForMac) + +Repository of AdGuard VPN for Mac — app designed for macOS. + +### [AdGuardVPNExtension](https://github.com/AdguardTeam/AdGuardVPNExtension) + +Repository of AdGuard VPN Browser Extension. + +### [AdGuardVPNCLI](https://github.com/AdguardTeam/AdGuardVPNCLI) + +Repository of AdGuard VPN for Linux — a command‑line interface for managing VPN connection. The repo acts as a bug tracker. + +## DNS-based products + +### [AdGuardDNS](https://github.com/AdguardTeam/AdGuardDNS) + +Open-source repository that is also used for tracking bugs and issues related to AdGuard DNS service. Users can: + +- View and report DNS issues +- Suggest improvements + +### [AdGuardHome](https://github.com/AdguardTeam/AdGuardHome) + +Repository of AdGuard Home — free network-wide software for blocking ads and trackers via DNS. Users can: + +- Check and file bug reports or feature requests +- Review or contribute to code +- Download and install releases + +## Documentation and Knowledge bases + +Knowledge bases are aimed to help users better understand and use AdGuard. They describe each AdGuard product in detail: from feature overviews and problem-solving guides to advanced setting manuals and API documentations. In the repositories users can: + +- Suggest corrections or edits to knowledge base articles +- Propose new articles +- Test or run the local version + +### [KnowledgeBase](https://github.com/AdguardTeam/KnowledgeBase) + +Central documentation for AdGuard Ad Blocker and the technologies related to it. + +### [KnowledgeBaseDNS](https://github.com/AdguardTeam/KnowledgeBaseDNS) + +Detailed feature overview, troubleshooting guides and documentation for AdGuard DNS (both Public and Private), AdGuard Home, and everything related to them. + +### [KnowledgeBaseVPN](https://github.com/AdguardTeam/KnowledgeBaseVPN) + +Detailed feature overview and troubleshooting guides for AdGuard VPN. + +### [KnowledgeBaseMail](https://github.com/AdguardTeam/KnowledgeBaseMail) + +Detailed feature overview and troubleshooting guides of AdGuard Mail. + +## Core libraries + +### [CoreLibs](https://github.com/AdguardTeam/CoreLibs) + +AdGuard’s cross-platform core filtering engine. Used in Android, Windows, and Mac products. Users can: + +- Explore filtering logic and DNS handling +- Report bugs and suggest features via Issues + +### [DNSLibs](https://github.com/AdguardTeam/DNSLibs) + +A DNS library used by CoreLibs and AdGuardHome. Users can: + +- Review and contribute to low-level DNS implementation +- Suggest optimizations + +### [VPNLibs](https://github.com/AdguardTeam/VPNLibs) + +Shared codebase used in AdGuard VPN products across platforms for AdGuard VPN protocol implementation. Users can: + +- Contribute to VPN stack behavior +- Report or view performance issues and bugs + +## Core ad blocking and filtering technologies + +### [AdguardFilters](https://github.com/AdguardTeam/AdguardFilters) + +Contains AdGuard’s core filter lists. Users can: + +- View and download filter lists +- Create issues to report false positives or suggest new rules +- Monitor updates to filter logic + +### [AdGuardSDNSFilter](https://github.com/AdguardTeam/AdGuardSDNSFilter) + +Repository of AdGuard DNS filter — the main DNS-level blocking list used in AdGuard DNS and DNS filtering features. Users can: + +- Inspect the current rule set +- Propose changes or additions + +### [AGLint](https://github.com/AdguardTeam/AGLint) + +A linter for adblock filter list syntax. Users can: + +- Install AGLint to check their projects for rule issues +- Contribute to lint rules + +### [Scriptlets](https://github.com/AdguardTeam/Scriptlets) + +JavaScript helpers used in filtering rules. Users can: + +- Explore available scriptlets +- Submit pull requests for new scriptlets + +### [tsurlfilter](https://github.com/AdguardTeam/tsurlfilter) + +TypeScript content blocker library for browser extensions. Users can: + +- Explore how filtering logic is implemented +- Contribute fixes and features + +## There’s more + +Above, we listed 27 main public AdGuard repositories out of 96 total. If you want to go down the rabbit hole, you can [find the rest on the AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse). + +We’ll be waiting for your feedback there! Stay safe online and offline. diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/general/how-to-install.md b/i18n/hu/docusaurus-plugin-content-docs/current/general/how-to-install.md index cc0f757af24..5e298f37419 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/general/how-to-install.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/general/how-to-install.md @@ -1,6 +1,6 @@ --- title: How to install AdGuard -sidebar_position: 9 +sidebar_position: 10 --- Depending on which AdGuard app or browser extension you want to install, follow one of these links to find the relevant article: diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md index ce6fd2fc56e..d382d325035 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md @@ -43,6 +43,14 @@ Qui puoi scegliere quale proxy AdGuard deve usare per scaricare gli aggiornament ## Usa il driver SockFilter -Abilita questa opzione per usare il driver SockFilter, che aiuta a bloccare inserzioni e tracciatori nelle app su Windows 8 e versioni successive. +Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. If this option is disabled, AdGuard will switch to the older WFP driver instead. -Se questa opzione viene disabilitata, AdGuard passerà al vecchio driver WFP. +SockFilter was first introduced in v8.0 RC. It is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md index fc7da814787..993ea39c9b0 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Per questo motivo, la visibilità del traffico basata su TDI diventa sempre più AdGuard già considera il driver TDI obsoleto e la sua completa rimozione è pianificata con l'evoluzione del prodotto. +## Soluzione permanente + +From v8.0 RC, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows-8/settings/app-settings/network-settings/). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Soluzione temporanea Certi cambiamenti del registro di Windows possono forzare il browser a fermare l'uso di AppContainer, causando nuovamente l'esecuzione dei suoi processi in una modalità non isolata. Il servizio della rete dedica ferma l'uso dello stack WSK e torna a un percorso di rete che il driver TDI può vedere. AdGuard quindi riacquista la capacità di filtrare il traffico del browser. @@ -123,7 +131,3 @@ Dovresti vedere le seguenti politiche attive: Se disponibile, clicca _Ricarica le politiche_. Fatto! - -## Soluzione permanente - -Abbiamo in programma di aggiungere il supporto per il driver SockFilter nelle prossime versioni. Risolverà l'inghippo sistemando i conflitti nello stack WFP. [Ulteriori informazioni](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index 51e3136a1d8..75e50399e38 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -17,23 +17,35 @@ In questo modulo puoi selezionare la casella di controllo _Usa AdGuard come prox Infine, esiste una sezione con le impostazioni proxy. Lì, puoi specificare quale server proxy dovrebbe essere usato da AdGuard per aggiornare i filtri, ottenere le nuove versioni e così via. -### SockFilter and other network drivers +### Enable traffic filtering -In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. +Traffic filtering is the core mechanism that allows AdGuard to inspect and control the network traffic generated by applications on your computer. When it is enabled, AdGuard intercepts outgoing and incoming connections and checks them against its filtering rules. If a request matches a blocking rule, AdGuard can block it, modify it, or allow it depending on the configuration. In AdGuard for Windows, this interception is implemented through network drivers. -**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. +If HTTPS filtering is enabled, AdGuard performs a controlled local TLS interception: it decrypts the traffic using its local certificate, applies filtering rules, and then re-encrypts the traffic before sending it to the browser. The driver simply provides the system-level access needed for AdGuard to intercept these connections. -The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +#### SockFilter **SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. -Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: +SockFilter was first implemented in version 7.22.4, and it is still considered unstable — you may encounter bugs. Once fully tested and implemented, SockFilter has the potential to offer several advantages over other drivers: -- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. - **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. -- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. -When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. +#### WFP + +**WFP** (Windows Filtering Platform) is a Microsoft networking framework built into Windows that allows software to filter and monitor network packets at different layers of the system networking stack. AdGuard uses WFP to safely hook into the network flow of applications and apply filtering rules before the traffic reaches the browser or the Internet. [More information](https://learn.microsoft.com/en-us/windows/win32/fwp/windows-filtering-platform-architecture-overview). + +While it is a powerful driver, it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) and lower Internet speed for some users. + +#### TDI + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. ### AdGuard VPN diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index 987e3a6d677..af598b8e016 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -44,12 +44,8 @@ Prima d'iniziare a scrivere manualmente le tue regole, leggi la nostra dettaglia Many websites gather information about their visitors, such as their IP addresses, browser and operating system details, screen resolution, and the webpage from which the user came or was redirected. Some websites use cookies to mark and identify your browser, save your personal settings and preferences. This allows them to “recognize” you on your next visit. Tracking protection safeguards your personal information from these data- and statistics-gathering systems. -![Tracking protection levels \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection1.png) - You can adjust the _Tracking Protection_ settings as needed. For example, you can prevent websites from receiving the search request that you used to find them on the Internet, automatically delete third- and first-party cookies, and disable location sharing in your browser, to prevent tracking of your whereabouts. -![Tracking protection custom features \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection2.png) - To learn everything about _Tracking protection_ and its many options, [read this article](/general/stealth-mode). ### Sicurezza di navigazione diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md index e22f031fd7f..34bcf271f16 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Per questo motivo, la visibilità del traffico basata su TDI diventa sempre più AdGuard già considera il driver TDI obsoleto e la sua completa rimozione è pianificata con l'evoluzione del prodotto. +## Soluzione permanente + +From v7.22.4, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows/features/network/#sockfilter-and-other-network-drivers). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Soluzione temporanea Certi cambiamenti del registro di Windows possono forzare il browser a fermare l'uso di AppContainer, causando nuovamente l'esecuzione dei suoi processi in una modalità non isolata. Il servizio della rete dedica ferma l'uso dello stack WSK e torna a un percorso di rete che il driver TDI può vedere. AdGuard quindi riacquista la capacità di filtrare il traffico del browser. @@ -136,7 +144,3 @@ Dovresti vedere le seguenti politiche attive: Se disponibile, clicca _Ricarica le politiche_. Fatto! - -## Soluzione permanente - -Abbiamo in programma di aggiungere il supporto per il driver SockFilter nelle prossime versioni. Risolverà l'inghippo sistemando i conflitti nello stack WFP. [Ulteriori informazioni](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/it/docusaurus-plugin-content-docs/current/general/github-repos.md b/i18n/it/docusaurus-plugin-content-docs/current/general/github-repos.md new file mode 100644 index 00000000000..dfb164c44bc --- /dev/null +++ b/i18n/it/docusaurus-plugin-content-docs/current/general/github-repos.md @@ -0,0 +1,238 @@ +--- +title: AdGuard’s GitHub repositories +sidebar_position: 9 +--- + +At AdGuard, our goal is to make the Internet safer, more comfortable, and more transparent. This commitment is reflected not only in our product features and strict privacy policies, but also in the fact that we keep our work as open as possible. That includes actively interacting with our community. + +This is why [all of our products have public repositories](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse) — online spaces where anybody can see what we are working on, report issues directly to AdGuard developers, and even contribute to our open-source projects. The repositories cover our ad-blocking apps, filters, browser extensions, DNS solutions, VPN tools, developer utilities, and more. There are different platforms that offer such functionality, but the most popular one by far is GitHub, and all AdGuard projects are stored there. + +This article lists the most important repositories by category, summarizes the purpose of each one, and gives a simple breakdown of what users can do there. + +:::tip + +Pro tip: Creating an issue on GitHub is the most effective way to bring the attention of AdGuard developers to a problem. Just make sure to check that a similar issue doesn’t already exist and describe the problem in a comprehensive but concise way. If it does exist, you can upvote it. + +::: + +## What is Github and its repositories + +Very simply put, you can think of GitHub as sort of Google Docs for code, where multiple people can work on the same project, track changes, and see who made which updates. It provides a central, cloud-based place to store your code so it’s accessible from anywhere. It also has teamwork tools for reviewing changes, fixing issues, and merging everyone’s work smoothly. + +GitHub is widely used for open-source projects, letting anyone view the code, suggest improvements, and contribute. + +A repository (often called “repo” for short) is the most basic element of GitHub. It’s a place where you can store your code, your files, and each file’s revision history. Repositories can have multiple collaborators and can be either public or private. + +## What can you do in AdGuard’s repositories + +You can find links to key repositories below in this article or visit the [general AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all) for a full list. In most repos, you can: + +- **View README file** on the main page: it gives you an introduction to the product and its repo + ![README file \*border](https://cdn.adtidy.org/content/blog/github-repos/see-readme.png) + +- **Check existing bug reports or feature requests**, comment and upvote + ![Check issues \*border](https://cdn.adtidy.org/content/blog/github-repos/check-issues.png) + +- **Create issues** to report bugs or request features + ![Create issues \*border](https://cdn.adtidy.org/content/blog/github-repos/create-issue.png) + +- **Check releases** for different versions and their changelogs (and install an older version if needed) + ![Check releases \*border](https://cdn.adtidy.org/content/blog/github-repos/check-releases.png) + +- **Install any older or beta version** if needed + ![Download builds \*border](https://cdn.adtidy.org/content/blog/github-repos/download-releases.png) + +:::note + +If you are new to GitHub, you’ll need to create a GitHub account in order to create new issues and comment on the existing ones. + +::: + +In open-source repos advanced users can also: + +- **Browse code** to understand product logic, what technologies are used and how they are implemented +- **Fork and contribute** via pull requests + +Whether you’re a casual user, technical expert, or a developer, AdGuard welcomes all community participation across its GitHub repos. + +## Legal documents + +### [LegalDocs](https://github.com/AdguardTeam/LegalDocs) + +As part of our commitment to transparency, we host all legal documents — such as End-User License Agreements, Privacy Policies, and Terms and Conditions — on GitHub. Our _LegalDocs_ repo lets anyone check the full history of changes to these documents. + +## AdGuard Ad Blocker products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdguardForAndroid](https://github.com/AdguardTeam/AdguardForAndroid) + +Repository of AdGuard for Android — an app that provides system-wide ad blocking. + +### [AdguardForiOS](https://github.com/AdguardTeam/AdguardForiOS) + +Repository of AdGuard for iOS — Safari content blocker with DNS and custom filters. Users can also check open-source code. + +### [AdguardForWindows](https://github.com/AdguardTeam/AdguardForWindows) + +Repository of AdGuard for Windows. Non-open-source; GitHub used as an open bug tracker. + +### [AdguardForMac](https://github.com/AdguardTeam/AdguardForMac) + +Repository of AdGuard for Mac — macOS standalone content blocker. Bug tracker only. + +### [AdguardBrowserExtension](https://github.com/AdguardTeam/AdguardBrowserExtension) + +Repository of AdGuard Browser Extension — extension that provides ad blocking with enhanced privacy for Chrome, Firefox, Opera, Edge. + +### [AdguardForSafari](https://github.com/AdguardTeam/AdGuardForSafari) + +Repository of AdGuard for Safari — Safari ad blocking extension for Mac. Users can also check open-sourced code. + +### [AdGuardCLI](https://github.com/AdguardTeam/AdGuardCLI) + +Repository of AdGuard for Linux — a command‑line interface for managing ad blocking. + +## AdGuard VPN products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdGuardVPNForiOS](https://github.com/AdguardTeam/AdGuardVPNForiOS) + +Repository of AdGuard VPN for iOS. Serves as an open bug tracker. + +### [AdGuardVPNForAndroid](https://github.com/AdguardTeam/AdGuardVPNForAndroid) + +Repository of AdGuard VPN for Android. Serves as an open bug tracker. + +### [AdGuardVPNForWindows](https://github.com/AdguardTeam/AdGuardVPNForWindows) + +Repository of AdGuard VPN for Windows. Serves as an open bug tracker. + +### [AdGuardVPNForMac](https://github.com/AdguardTeam/AdGuardVPNForMac) + +Repository of AdGuard VPN for Mac — app designed for macOS. + +### [AdGuardVPNExtension](https://github.com/AdguardTeam/AdGuardVPNExtension) + +Repository of AdGuard VPN Browser Extension. + +### [AdGuardVPNCLI](https://github.com/AdguardTeam/AdGuardVPNCLI) + +Repository of AdGuard VPN for Linux — a command‑line interface for managing VPN connection. The repo acts as a bug tracker. + +## DNS-based products + +### [AdGuardDNS](https://github.com/AdguardTeam/AdGuardDNS) + +Open-source repository that is also used for tracking bugs and issues related to AdGuard DNS service. Users can: + +- View and report DNS issues +- Suggest improvements + +### [AdGuardHome](https://github.com/AdguardTeam/AdGuardHome) + +Repository of AdGuard Home — free network-wide software for blocking ads and trackers via DNS. Users can: + +- Check and file bug reports or feature requests +- Review or contribute to code +- Download and install releases + +## Documentation and Knowledge bases + +Knowledge bases are aimed to help users better understand and use AdGuard. They describe each AdGuard product in detail: from feature overviews and problem-solving guides to advanced setting manuals and API documentations. In the repositories users can: + +- Suggest corrections or edits to knowledge base articles +- Propose new articles +- Test or run the local version + +### [KnowledgeBase](https://github.com/AdguardTeam/KnowledgeBase) + +Central documentation for AdGuard Ad Blocker and the technologies related to it. + +### [KnowledgeBaseDNS](https://github.com/AdguardTeam/KnowledgeBaseDNS) + +Detailed feature overview, troubleshooting guides and documentation for AdGuard DNS (both Public and Private), AdGuard Home, and everything related to them. + +### [KnowledgeBaseVPN](https://github.com/AdguardTeam/KnowledgeBaseVPN) + +Detailed feature overview and troubleshooting guides for AdGuard VPN. + +### [KnowledgeBaseMail](https://github.com/AdguardTeam/KnowledgeBaseMail) + +Detailed feature overview and troubleshooting guides of AdGuard Mail. + +## Core libraries + +### [CoreLibs](https://github.com/AdguardTeam/CoreLibs) + +AdGuard’s cross-platform core filtering engine. Used in Android, Windows, and Mac products. Users can: + +- Explore filtering logic and DNS handling +- Report bugs and suggest features via Issues + +### [DNSLibs](https://github.com/AdguardTeam/DNSLibs) + +A DNS library used by CoreLibs and AdGuardHome. Users can: + +- Review and contribute to low-level DNS implementation +- Suggest optimizations + +### [VPNLibs](https://github.com/AdguardTeam/VPNLibs) + +Shared codebase used in AdGuard VPN products across platforms for AdGuard VPN protocol implementation. Users can: + +- Contribute to VPN stack behavior +- Report or view performance issues and bugs + +## Core ad blocking and filtering technologies + +### [AdguardFilters](https://github.com/AdguardTeam/AdguardFilters) + +Contains AdGuard’s core filter lists. Users can: + +- View and download filter lists +- Create issues to report false positives or suggest new rules +- Monitor updates to filter logic + +### [AdGuardSDNSFilter](https://github.com/AdguardTeam/AdGuardSDNSFilter) + +Repository of AdGuard DNS filter — the main DNS-level blocking list used in AdGuard DNS and DNS filtering features. Users can: + +- Inspect the current rule set +- Propose changes or additions + +### [AGLint](https://github.com/AdguardTeam/AGLint) + +A linter for adblock filter list syntax. Users can: + +- Install AGLint to check their projects for rule issues +- Contribute to lint rules + +### [Scriptlets](https://github.com/AdguardTeam/Scriptlets) + +JavaScript helpers used in filtering rules. Users can: + +- Explore available scriptlets +- Submit pull requests for new scriptlets + +### [tsurlfilter](https://github.com/AdguardTeam/tsurlfilter) + +TypeScript content blocker library for browser extensions. Users can: + +- Explore how filtering logic is implemented +- Contribute fixes and features + +## There’s more + +Above, we listed 27 main public AdGuard repositories out of 96 total. If you want to go down the rabbit hole, you can [find the rest on the AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse). + +We’ll be waiting for your feedback there! Stay safe online and offline. diff --git a/i18n/it/docusaurus-plugin-content-docs/current/general/how-to-install.md b/i18n/it/docusaurus-plugin-content-docs/current/general/how-to-install.md index 297fff52c61..1db612762c5 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/general/how-to-install.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/general/how-to-install.md @@ -1,6 +1,6 @@ --- title: Come installare AdGuard -sidebar_position: 9 +sidebar_position: 10 --- A seconda di quale app o estensione del browser di AdGuard desideri installare, segui uno di questi link per trovare l'articolo rilevante: diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md index ba1793f91b0..821189049fb 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md @@ -43,6 +43,14 @@ Here you can choose which proxy AdGuard should use to download filter updates or ## Use SockFilter driver -Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. +Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. If this option is disabled, AdGuard will switch to the older WFP driver instead. -If this option is disabled, AdGuard will switch to the older WFP driver instead. +SockFilter was first introduced in v8.0 RC. It is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md index f407442c719..660b91ebc2d 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Because of this, TDI-based traffic visibility becomes increasingly unstable. In AdGuard already treats the TDI driver as deprecated, and its complete removal is planned as the product evolves. +## Permanent solution + +From v8.0 RC, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows-8/settings/app-settings/network-settings/). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Temporary solution Certain Windows registry changes can force the browser to stop using AppContainer, causing its processes to run in a non-sandboxed mode again. Network Service stops using the WSK stack and falls back to a network path that the TDI driver can see. AdGuard then regains the ability to filter browser traffic. @@ -123,7 +131,3 @@ You should see the following policies active: If available, click _Reload policies_. 完了です！ - -## Permanent solution - -We’re planning to add support for the SockFilter driver in the upcoming versions. It will fix the issue by solving conflicts in the WFP stack. [More information](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index 78c85113b99..d9333ec0b0a 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -17,23 +17,35 @@ sidebar_position: 4 最後に、プロキシ設定のセクションがあります。 そこで、AdGuard がフィルタの更新や新バージョンの取得などに使用するプロキシサーバーを指定できます。 -### SockFilter and other network drivers +### Enable traffic filtering -In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. +Traffic filtering is the core mechanism that allows AdGuard to inspect and control the network traffic generated by applications on your computer. When it is enabled, AdGuard intercepts outgoing and incoming connections and checks them against its filtering rules. If a request matches a blocking rule, AdGuard can block it, modify it, or allow it depending on the configuration. In AdGuard for Windows, this interception is implemented through network drivers. -**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. +If HTTPS filtering is enabled, AdGuard performs a controlled local TLS interception: it decrypts the traffic using its local certificate, applies filtering rules, and then re-encrypts the traffic before sending it to the browser. The driver simply provides the system-level access needed for AdGuard to intercept these connections. -The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +#### SockFilter **SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. -Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: +SockFilter was first implemented in version 7.22.4, and it is still considered unstable — you may encounter bugs. Once fully tested and implemented, SockFilter has the potential to offer several advantages over other drivers: -- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. - **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. -- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. -When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. +#### WFP + +**WFP** (Windows Filtering Platform) is a Microsoft networking framework built into Windows that allows software to filter and monitor network packets at different layers of the system networking stack. AdGuard uses WFP to safely hook into the network flow of applications and apply filtering rules before the traffic reaches the browser or the Internet. [More information](https://learn.microsoft.com/en-us/windows/win32/fwp/windows-filtering-platform-architecture-overview). + +While it is a powerful driver, it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) and lower Internet speed for some users. + +#### TDI + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. ### AdGuard VPN diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index 5e644d0f76a..d3548e2c448 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -44,12 +44,8 @@ In the Ad blocking module you can: Many websites gather information about their visitors, such as their IP addresses, browser and operating system details, screen resolution, and the webpage from which the user came or was redirected. Some websites use cookies to mark and identify your browser, save your personal settings and preferences. This allows them to “recognize” you on your next visit. Tracking protection safeguards your personal information from these data- and statistics-gathering systems. -![Tracking protection levels \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection1.png) - You can adjust the _Tracking Protection_ settings as needed. For example, you can prevent websites from receiving the search request that you used to find them on the Internet, automatically delete third- and first-party cookies, and disable location sharing in your browser, to prevent tracking of your whereabouts. -![Tracking protection custom features \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection2.png) - To learn everything about _Tracking protection_ and its many options, [read this article](/general/stealth-mode). ### ブラウジング・セキュリティ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md index 77680059563..496b7ffd006 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Because of this, TDI-based traffic visibility becomes increasingly unstable. In AdGuard already treats the TDI driver as deprecated, and its complete removal is planned as the product evolves. +## Permanent solution + +From v7.22.4, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows/features/network/#sockfilter-and-other-network-drivers). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Temporary solution Certain Windows registry changes can force the browser to stop using AppContainer, causing its processes to run in a non-sandboxed mode again. Network Service stops using the WSK stack and falls back to a network path that the TDI driver can see. AdGuard then regains the ability to filter browser traffic. @@ -136,7 +144,3 @@ You should see the following policies active: If available, click _Reload policies_. 完了です！ - -## Permanent solution - -We’re planning to add support for the SockFilter driver in the upcoming versions. It will fix the issue by solving conflicts in the WFP stack. [More information](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/general/github-repos.md b/i18n/ja/docusaurus-plugin-content-docs/current/general/github-repos.md new file mode 100644 index 00000000000..dfb164c44bc --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/general/github-repos.md @@ -0,0 +1,238 @@ +--- +title: AdGuard’s GitHub repositories +sidebar_position: 9 +--- + +At AdGuard, our goal is to make the Internet safer, more comfortable, and more transparent. This commitment is reflected not only in our product features and strict privacy policies, but also in the fact that we keep our work as open as possible. That includes actively interacting with our community. + +This is why [all of our products have public repositories](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse) — online spaces where anybody can see what we are working on, report issues directly to AdGuard developers, and even contribute to our open-source projects. The repositories cover our ad-blocking apps, filters, browser extensions, DNS solutions, VPN tools, developer utilities, and more. There are different platforms that offer such functionality, but the most popular one by far is GitHub, and all AdGuard projects are stored there. + +This article lists the most important repositories by category, summarizes the purpose of each one, and gives a simple breakdown of what users can do there. + +:::tip + +Pro tip: Creating an issue on GitHub is the most effective way to bring the attention of AdGuard developers to a problem. Just make sure to check that a similar issue doesn’t already exist and describe the problem in a comprehensive but concise way. If it does exist, you can upvote it. + +::: + +## What is Github and its repositories + +Very simply put, you can think of GitHub as sort of Google Docs for code, where multiple people can work on the same project, track changes, and see who made which updates. It provides a central, cloud-based place to store your code so it’s accessible from anywhere. It also has teamwork tools for reviewing changes, fixing issues, and merging everyone’s work smoothly. + +GitHub is widely used for open-source projects, letting anyone view the code, suggest improvements, and contribute. + +A repository (often called “repo” for short) is the most basic element of GitHub. It’s a place where you can store your code, your files, and each file’s revision history. Repositories can have multiple collaborators and can be either public or private. + +## What can you do in AdGuard’s repositories + +You can find links to key repositories below in this article or visit the [general AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all) for a full list. In most repos, you can: + +- **View README file** on the main page: it gives you an introduction to the product and its repo + ![README file \*border](https://cdn.adtidy.org/content/blog/github-repos/see-readme.png) + +- **Check existing bug reports or feature requests**, comment and upvote + ![Check issues \*border](https://cdn.adtidy.org/content/blog/github-repos/check-issues.png) + +- **Create issues** to report bugs or request features + ![Create issues \*border](https://cdn.adtidy.org/content/blog/github-repos/create-issue.png) + +- **Check releases** for different versions and their changelogs (and install an older version if needed) + ![Check releases \*border](https://cdn.adtidy.org/content/blog/github-repos/check-releases.png) + +- **Install any older or beta version** if needed + ![Download builds \*border](https://cdn.adtidy.org/content/blog/github-repos/download-releases.png) + +:::note + +If you are new to GitHub, you’ll need to create a GitHub account in order to create new issues and comment on the existing ones. + +::: + +In open-source repos advanced users can also: + +- **Browse code** to understand product logic, what technologies are used and how they are implemented +- **Fork and contribute** via pull requests + +Whether you’re a casual user, technical expert, or a developer, AdGuard welcomes all community participation across its GitHub repos. + +## Legal documents + +### [LegalDocs](https://github.com/AdguardTeam/LegalDocs) + +As part of our commitment to transparency, we host all legal documents — such as End-User License Agreements, Privacy Policies, and Terms and Conditions — on GitHub. Our _LegalDocs_ repo lets anyone check the full history of changes to these documents. + +## AdGuard Ad Blocker products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdguardForAndroid](https://github.com/AdguardTeam/AdguardForAndroid) + +Repository of AdGuard for Android — an app that provides system-wide ad blocking. + +### [AdguardForiOS](https://github.com/AdguardTeam/AdguardForiOS) + +Repository of AdGuard for iOS — Safari content blocker with DNS and custom filters. Users can also check open-source code. + +### [AdguardForWindows](https://github.com/AdguardTeam/AdguardForWindows) + +Repository of AdGuard for Windows. Non-open-source; GitHub used as an open bug tracker. + +### [AdguardForMac](https://github.com/AdguardTeam/AdguardForMac) + +Repository of AdGuard for Mac — macOS standalone content blocker. Bug tracker only. + +### [AdguardBrowserExtension](https://github.com/AdguardTeam/AdguardBrowserExtension) + +Repository of AdGuard Browser Extension — extension that provides ad blocking with enhanced privacy for Chrome, Firefox, Opera, Edge. + +### [AdguardForSafari](https://github.com/AdguardTeam/AdGuardForSafari) + +Repository of AdGuard for Safari — Safari ad blocking extension for Mac. Users can also check open-sourced code. + +### [AdGuardCLI](https://github.com/AdguardTeam/AdGuardCLI) + +Repository of AdGuard for Linux — a command‑line interface for managing ad blocking. + +## AdGuard VPN products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdGuardVPNForiOS](https://github.com/AdguardTeam/AdGuardVPNForiOS) + +Repository of AdGuard VPN for iOS. Serves as an open bug tracker. + +### [AdGuardVPNForAndroid](https://github.com/AdguardTeam/AdGuardVPNForAndroid) + +Repository of AdGuard VPN for Android. Serves as an open bug tracker. + +### [AdGuardVPNForWindows](https://github.com/AdguardTeam/AdGuardVPNForWindows) + +Repository of AdGuard VPN for Windows. Serves as an open bug tracker. + +### [AdGuardVPNForMac](https://github.com/AdguardTeam/AdGuardVPNForMac) + +Repository of AdGuard VPN for Mac — app designed for macOS. + +### [AdGuardVPNExtension](https://github.com/AdguardTeam/AdGuardVPNExtension) + +Repository of AdGuard VPN Browser Extension. + +### [AdGuardVPNCLI](https://github.com/AdguardTeam/AdGuardVPNCLI) + +Repository of AdGuard VPN for Linux — a command‑line interface for managing VPN connection. The repo acts as a bug tracker. + +## DNS-based products + +### [AdGuardDNS](https://github.com/AdguardTeam/AdGuardDNS) + +Open-source repository that is also used for tracking bugs and issues related to AdGuard DNS service. Users can: + +- View and report DNS issues +- Suggest improvements + +### [AdGuardHome](https://github.com/AdguardTeam/AdGuardHome) + +Repository of AdGuard Home — free network-wide software for blocking ads and trackers via DNS. Users can: + +- Check and file bug reports or feature requests +- Review or contribute to code +- Download and install releases + +## Documentation and Knowledge bases + +Knowledge bases are aimed to help users better understand and use AdGuard. They describe each AdGuard product in detail: from feature overviews and problem-solving guides to advanced setting manuals and API documentations. In the repositories users can: + +- Suggest corrections or edits to knowledge base articles +- Propose new articles +- Test or run the local version + +### [KnowledgeBase](https://github.com/AdguardTeam/KnowledgeBase) + +Central documentation for AdGuard Ad Blocker and the technologies related to it. + +### [KnowledgeBaseDNS](https://github.com/AdguardTeam/KnowledgeBaseDNS) + +Detailed feature overview, troubleshooting guides and documentation for AdGuard DNS (both Public and Private), AdGuard Home, and everything related to them. + +### [KnowledgeBaseVPN](https://github.com/AdguardTeam/KnowledgeBaseVPN) + +Detailed feature overview and troubleshooting guides for AdGuard VPN. + +### [KnowledgeBaseMail](https://github.com/AdguardTeam/KnowledgeBaseMail) + +Detailed feature overview and troubleshooting guides of AdGuard Mail. + +## Core libraries + +### [CoreLibs](https://github.com/AdguardTeam/CoreLibs) + +AdGuard’s cross-platform core filtering engine. Used in Android, Windows, and Mac products. Users can: + +- Explore filtering logic and DNS handling +- Report bugs and suggest features via Issues + +### [DNSLibs](https://github.com/AdguardTeam/DNSLibs) + +A DNS library used by CoreLibs and AdGuardHome. Users can: + +- Review and contribute to low-level DNS implementation +- Suggest optimizations + +### [VPNLibs](https://github.com/AdguardTeam/VPNLibs) + +Shared codebase used in AdGuard VPN products across platforms for AdGuard VPN protocol implementation. Users can: + +- Contribute to VPN stack behavior +- Report or view performance issues and bugs + +## Core ad blocking and filtering technologies + +### [AdguardFilters](https://github.com/AdguardTeam/AdguardFilters) + +Contains AdGuard’s core filter lists. Users can: + +- View and download filter lists +- Create issues to report false positives or suggest new rules +- Monitor updates to filter logic + +### [AdGuardSDNSFilter](https://github.com/AdguardTeam/AdGuardSDNSFilter) + +Repository of AdGuard DNS filter — the main DNS-level blocking list used in AdGuard DNS and DNS filtering features. Users can: + +- Inspect the current rule set +- Propose changes or additions + +### [AGLint](https://github.com/AdguardTeam/AGLint) + +A linter for adblock filter list syntax. Users can: + +- Install AGLint to check their projects for rule issues +- Contribute to lint rules + +### [Scriptlets](https://github.com/AdguardTeam/Scriptlets) + +JavaScript helpers used in filtering rules. Users can: + +- Explore available scriptlets +- Submit pull requests for new scriptlets + +### [tsurlfilter](https://github.com/AdguardTeam/tsurlfilter) + +TypeScript content blocker library for browser extensions. Users can: + +- Explore how filtering logic is implemented +- Contribute fixes and features + +## There’s more + +Above, we listed 27 main public AdGuard repositories out of 96 total. If you want to go down the rabbit hole, you can [find the rest on the AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse). + +We’ll be waiting for your feedback there! Stay safe online and offline. diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/general/how-to-install.md b/i18n/ja/docusaurus-plugin-content-docs/current/general/how-to-install.md index 32a20cc559a..50d8271f273 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/general/how-to-install.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/general/how-to-install.md @@ -1,6 +1,6 @@ --- title: AdGuard のインストール方法 -sidebar_position: 9 +sidebar_position: 10 --- インストールしたいAdGuardアプリ・ブラウザ拡張機能に応じて、以下のリンクから関連記事をご覧ください。 diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md index 518fe07b7f0..f79107801cd 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md @@ -43,6 +43,14 @@ Here you can choose which proxy AdGuard should use to download filter updates or ## Use SockFilter driver -Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. +Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. If this option is disabled, AdGuard will switch to the older WFP driver instead. -If this option is disabled, AdGuard will switch to the older WFP driver instead. +SockFilter was first introduced in v8.0 RC. It is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md index 81199a20c11..a85deb60e68 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Because of this, TDI-based traffic visibility becomes increasingly unstable. In AdGuard already treats the TDI driver as deprecated, and its complete removal is planned as the product evolves. +## Permanent solution + +From v8.0 RC, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows-8/settings/app-settings/network-settings/). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Temporary solution Certain Windows registry changes can force the browser to stop using AppContainer, causing its processes to run in a non-sandboxed mode again. Network Service stops using the WSK stack and falls back to a network path that the TDI driver can see. AdGuard then regains the ability to filter browser traffic. @@ -123,7 +131,3 @@ You should see the following policies active: If available, click _Reload policies_. 끝! - -## Permanent solution - -We’re planning to add support for the SockFilter driver in the upcoming versions. It will fix the issue by solving conflicts in the WFP stack. [More information](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index 776a2a38c0e..28d7243095b 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -17,23 +17,35 @@ sidebar_position: 4 마지막으로 프록시 설정 섹션이 있습니다. 여기에서 필터 업데이트, 새 버전 가져오기 등에 AdGuard가 사용할 프록시 서버를 지정할 수 있습니다. -### SockFilter and other network drivers +### Enable traffic filtering -In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. +Traffic filtering is the core mechanism that allows AdGuard to inspect and control the network traffic generated by applications on your computer. When it is enabled, AdGuard intercepts outgoing and incoming connections and checks them against its filtering rules. If a request matches a blocking rule, AdGuard can block it, modify it, or allow it depending on the configuration. In AdGuard for Windows, this interception is implemented through network drivers. -**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. +If HTTPS filtering is enabled, AdGuard performs a controlled local TLS interception: it decrypts the traffic using its local certificate, applies filtering rules, and then re-encrypts the traffic before sending it to the browser. The driver simply provides the system-level access needed for AdGuard to intercept these connections. -The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +#### SockFilter **SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. -Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: +SockFilter was first implemented in version 7.22.4, and it is still considered unstable — you may encounter bugs. Once fully tested and implemented, SockFilter has the potential to offer several advantages over other drivers: -- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. - **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. -- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. -When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. +#### WFP + +**WFP** (Windows Filtering Platform) is a Microsoft networking framework built into Windows that allows software to filter and monitor network packets at different layers of the system networking stack. AdGuard uses WFP to safely hook into the network flow of applications and apply filtering rules before the traffic reaches the browser or the Internet. [More information](https://learn.microsoft.com/en-us/windows/win32/fwp/windows-filtering-platform-architecture-overview). + +While it is a powerful driver, it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) and lower Internet speed for some users. + +#### TDI + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. ### AdGuard VPN diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index 5ee26428549..fb07af417be 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -44,12 +44,8 @@ In the Ad blocking module you can: Many websites gather information about their visitors, such as their IP addresses, browser and operating system details, screen resolution, and the webpage from which the user came or was redirected. Some websites use cookies to mark and identify your browser, save your personal settings and preferences. This allows them to “recognize” you on your next visit. Tracking protection safeguards your personal information from these data- and statistics-gathering systems. -![Tracking protection levels \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection1.png) - You can adjust the _Tracking Protection_ settings as needed. For example, you can prevent websites from receiving the search request that you used to find them on the Internet, automatically delete third- and first-party cookies, and disable location sharing in your browser, to prevent tracking of your whereabouts. -![Tracking protection custom features \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection2.png) - To learn everything about _Tracking protection_ and its many options, [read this article](/general/stealth-mode). ### 브라우징 보안 diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md index d8199f58dac..ce56f6acbf2 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Because of this, TDI-based traffic visibility becomes increasingly unstable. In AdGuard already treats the TDI driver as deprecated, and its complete removal is planned as the product evolves. +## Permanent solution + +From v7.22.4, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows/features/network/#sockfilter-and-other-network-drivers). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Temporary solution Certain Windows registry changes can force the browser to stop using AppContainer, causing its processes to run in a non-sandboxed mode again. Network Service stops using the WSK stack and falls back to a network path that the TDI driver can see. AdGuard then regains the ability to filter browser traffic. @@ -136,7 +144,3 @@ You should see the following policies active: If available, click _Reload policies_. 끝! - -## Permanent solution - -We’re planning to add support for the SockFilter driver in the upcoming versions. It will fix the issue by solving conflicts in the WFP stack. [More information](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/general/github-repos.md b/i18n/ko/docusaurus-plugin-content-docs/current/general/github-repos.md new file mode 100644 index 00000000000..dfb164c44bc --- /dev/null +++ b/i18n/ko/docusaurus-plugin-content-docs/current/general/github-repos.md @@ -0,0 +1,238 @@ +--- +title: AdGuard’s GitHub repositories +sidebar_position: 9 +--- + +At AdGuard, our goal is to make the Internet safer, more comfortable, and more transparent. This commitment is reflected not only in our product features and strict privacy policies, but also in the fact that we keep our work as open as possible. That includes actively interacting with our community. + +This is why [all of our products have public repositories](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse) — online spaces where anybody can see what we are working on, report issues directly to AdGuard developers, and even contribute to our open-source projects. The repositories cover our ad-blocking apps, filters, browser extensions, DNS solutions, VPN tools, developer utilities, and more. There are different platforms that offer such functionality, but the most popular one by far is GitHub, and all AdGuard projects are stored there. + +This article lists the most important repositories by category, summarizes the purpose of each one, and gives a simple breakdown of what users can do there. + +:::tip + +Pro tip: Creating an issue on GitHub is the most effective way to bring the attention of AdGuard developers to a problem. Just make sure to check that a similar issue doesn’t already exist and describe the problem in a comprehensive but concise way. If it does exist, you can upvote it. + +::: + +## What is Github and its repositories + +Very simply put, you can think of GitHub as sort of Google Docs for code, where multiple people can work on the same project, track changes, and see who made which updates. It provides a central, cloud-based place to store your code so it’s accessible from anywhere. It also has teamwork tools for reviewing changes, fixing issues, and merging everyone’s work smoothly. + +GitHub is widely used for open-source projects, letting anyone view the code, suggest improvements, and contribute. + +A repository (often called “repo” for short) is the most basic element of GitHub. It’s a place where you can store your code, your files, and each file’s revision history. Repositories can have multiple collaborators and can be either public or private. + +## What can you do in AdGuard’s repositories + +You can find links to key repositories below in this article or visit the [general AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all) for a full list. In most repos, you can: + +- **View README file** on the main page: it gives you an introduction to the product and its repo + ![README file \*border](https://cdn.adtidy.org/content/blog/github-repos/see-readme.png) + +- **Check existing bug reports or feature requests**, comment and upvote + ![Check issues \*border](https://cdn.adtidy.org/content/blog/github-repos/check-issues.png) + +- **Create issues** to report bugs or request features + ![Create issues \*border](https://cdn.adtidy.org/content/blog/github-repos/create-issue.png) + +- **Check releases** for different versions and their changelogs (and install an older version if needed) + ![Check releases \*border](https://cdn.adtidy.org/content/blog/github-repos/check-releases.png) + +- **Install any older or beta version** if needed + ![Download builds \*border](https://cdn.adtidy.org/content/blog/github-repos/download-releases.png) + +:::note + +If you are new to GitHub, you’ll need to create a GitHub account in order to create new issues and comment on the existing ones. + +::: + +In open-source repos advanced users can also: + +- **Browse code** to understand product logic, what technologies are used and how they are implemented +- **Fork and contribute** via pull requests + +Whether you’re a casual user, technical expert, or a developer, AdGuard welcomes all community participation across its GitHub repos. + +## Legal documents + +### [LegalDocs](https://github.com/AdguardTeam/LegalDocs) + +As part of our commitment to transparency, we host all legal documents — such as End-User License Agreements, Privacy Policies, and Terms and Conditions — on GitHub. Our _LegalDocs_ repo lets anyone check the full history of changes to these documents. + +## AdGuard Ad Blocker products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdguardForAndroid](https://github.com/AdguardTeam/AdguardForAndroid) + +Repository of AdGuard for Android — an app that provides system-wide ad blocking. + +### [AdguardForiOS](https://github.com/AdguardTeam/AdguardForiOS) + +Repository of AdGuard for iOS — Safari content blocker with DNS and custom filters. Users can also check open-source code. + +### [AdguardForWindows](https://github.com/AdguardTeam/AdguardForWindows) + +Repository of AdGuard for Windows. Non-open-source; GitHub used as an open bug tracker. + +### [AdguardForMac](https://github.com/AdguardTeam/AdguardForMac) + +Repository of AdGuard for Mac — macOS standalone content blocker. Bug tracker only. + +### [AdguardBrowserExtension](https://github.com/AdguardTeam/AdguardBrowserExtension) + +Repository of AdGuard Browser Extension — extension that provides ad blocking with enhanced privacy for Chrome, Firefox, Opera, Edge. + +### [AdguardForSafari](https://github.com/AdguardTeam/AdGuardForSafari) + +Repository of AdGuard for Safari — Safari ad blocking extension for Mac. Users can also check open-sourced code. + +### [AdGuardCLI](https://github.com/AdguardTeam/AdGuardCLI) + +Repository of AdGuard for Linux — a command‑line interface for managing ad blocking. + +## AdGuard VPN products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdGuardVPNForiOS](https://github.com/AdguardTeam/AdGuardVPNForiOS) + +Repository of AdGuard VPN for iOS. Serves as an open bug tracker. + +### [AdGuardVPNForAndroid](https://github.com/AdguardTeam/AdGuardVPNForAndroid) + +Repository of AdGuard VPN for Android. Serves as an open bug tracker. + +### [AdGuardVPNForWindows](https://github.com/AdguardTeam/AdGuardVPNForWindows) + +Repository of AdGuard VPN for Windows. Serves as an open bug tracker. + +### [AdGuardVPNForMac](https://github.com/AdguardTeam/AdGuardVPNForMac) + +Repository of AdGuard VPN for Mac — app designed for macOS. + +### [AdGuardVPNExtension](https://github.com/AdguardTeam/AdGuardVPNExtension) + +Repository of AdGuard VPN Browser Extension. + +### [AdGuardVPNCLI](https://github.com/AdguardTeam/AdGuardVPNCLI) + +Repository of AdGuard VPN for Linux — a command‑line interface for managing VPN connection. The repo acts as a bug tracker. + +## DNS-based products + +### [AdGuardDNS](https://github.com/AdguardTeam/AdGuardDNS) + +Open-source repository that is also used for tracking bugs and issues related to AdGuard DNS service. Users can: + +- View and report DNS issues +- Suggest improvements + +### [AdGuardHome](https://github.com/AdguardTeam/AdGuardHome) + +Repository of AdGuard Home — free network-wide software for blocking ads and trackers via DNS. Users can: + +- Check and file bug reports or feature requests +- Review or contribute to code +- Download and install releases + +## Documentation and Knowledge bases + +Knowledge bases are aimed to help users better understand and use AdGuard. They describe each AdGuard product in detail: from feature overviews and problem-solving guides to advanced setting manuals and API documentations. In the repositories users can: + +- Suggest corrections or edits to knowledge base articles +- Propose new articles +- Test or run the local version + +### [KnowledgeBase](https://github.com/AdguardTeam/KnowledgeBase) + +Central documentation for AdGuard Ad Blocker and the technologies related to it. + +### [KnowledgeBaseDNS](https://github.com/AdguardTeam/KnowledgeBaseDNS) + +Detailed feature overview, troubleshooting guides and documentation for AdGuard DNS (both Public and Private), AdGuard Home, and everything related to them. + +### [KnowledgeBaseVPN](https://github.com/AdguardTeam/KnowledgeBaseVPN) + +Detailed feature overview and troubleshooting guides for AdGuard VPN. + +### [KnowledgeBaseMail](https://github.com/AdguardTeam/KnowledgeBaseMail) + +Detailed feature overview and troubleshooting guides of AdGuard Mail. + +## Core libraries + +### [CoreLibs](https://github.com/AdguardTeam/CoreLibs) + +AdGuard’s cross-platform core filtering engine. Used in Android, Windows, and Mac products. Users can: + +- Explore filtering logic and DNS handling +- Report bugs and suggest features via Issues + +### [DNSLibs](https://github.com/AdguardTeam/DNSLibs) + +A DNS library used by CoreLibs and AdGuardHome. Users can: + +- Review and contribute to low-level DNS implementation +- Suggest optimizations + +### [VPNLibs](https://github.com/AdguardTeam/VPNLibs) + +Shared codebase used in AdGuard VPN products across platforms for AdGuard VPN protocol implementation. Users can: + +- Contribute to VPN stack behavior +- Report or view performance issues and bugs + +## Core ad blocking and filtering technologies + +### [AdguardFilters](https://github.com/AdguardTeam/AdguardFilters) + +Contains AdGuard’s core filter lists. Users can: + +- View and download filter lists +- Create issues to report false positives or suggest new rules +- Monitor updates to filter logic + +### [AdGuardSDNSFilter](https://github.com/AdguardTeam/AdGuardSDNSFilter) + +Repository of AdGuard DNS filter — the main DNS-level blocking list used in AdGuard DNS and DNS filtering features. Users can: + +- Inspect the current rule set +- Propose changes or additions + +### [AGLint](https://github.com/AdguardTeam/AGLint) + +A linter for adblock filter list syntax. Users can: + +- Install AGLint to check their projects for rule issues +- Contribute to lint rules + +### [Scriptlets](https://github.com/AdguardTeam/Scriptlets) + +JavaScript helpers used in filtering rules. Users can: + +- Explore available scriptlets +- Submit pull requests for new scriptlets + +### [tsurlfilter](https://github.com/AdguardTeam/tsurlfilter) + +TypeScript content blocker library for browser extensions. Users can: + +- Explore how filtering logic is implemented +- Contribute fixes and features + +## There’s more + +Above, we listed 27 main public AdGuard repositories out of 96 total. If you want to go down the rabbit hole, you can [find the rest on the AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse). + +We’ll be waiting for your feedback there! Stay safe online and offline. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/general/how-to-install.md b/i18n/ko/docusaurus-plugin-content-docs/current/general/how-to-install.md index b4472bdfa94..e907a80ddeb 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/general/how-to-install.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/general/how-to-install.md @@ -1,6 +1,6 @@ --- title: AdGuard를 설치하는 방법 -sidebar_position: 9 +sidebar_position: 10 --- 설치하려는 AdGuard 앱 또는 확장 프로그램에 따라 다음 링크 중 하나를 클릭하여 관련 지침을 따르세요. diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md index 3953f47d26f..05642d350b0 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md @@ -43,6 +43,14 @@ Here you can choose which proxy AdGuard should use to download filter updates or ## Use SockFilter driver -Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. +Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. If this option is disabled, AdGuard will switch to the older WFP driver instead. -If this option is disabled, AdGuard will switch to the older WFP driver instead. +SockFilter was first introduced in v8.0 RC. It is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md index 251e49cf286..1ab588bb16c 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Because of this, TDI-based traffic visibility becomes increasingly unstable. In AdGuard already treats the TDI driver as deprecated, and its complete removal is planned as the product evolves. +## Permanent solution + +From v8.0 RC, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows-8/settings/app-settings/network-settings/). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Temporary solution Certain Windows registry changes can force the browser to stop using AppContainer, causing its processes to run in a non-sandboxed mode again. Network Service stops using the WSK stack and falls back to a network path that the TDI driver can see. AdGuard then regains the ability to filter browser traffic. @@ -123,7 +131,3 @@ You should see the following policies active: If available, click _Reload policies_. Done! - -## Permanent solution - -We’re planning to add support for the SockFilter driver in the upcoming versions. It will fix the issue by solving conflicts in the WFP stack. [More information](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index 5945618ea9c..f8074e9cfa1 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -17,23 +17,35 @@ In this module you can select the checkbox _Use AdGuard as an HTTP proxy_ to use At last, there is a section with proxy settings. There you can specify which proxy server AdGuard should use to update filters, get new versions, and so on. -### SockFilter and other network drivers +### Enable traffic filtering -In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. +Traffic filtering is the core mechanism that allows AdGuard to inspect and control the network traffic generated by applications on your computer. When it is enabled, AdGuard intercepts outgoing and incoming connections and checks them against its filtering rules. If a request matches a blocking rule, AdGuard can block it, modify it, or allow it depending on the configuration. In AdGuard for Windows, this interception is implemented through network drivers. -**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. +If HTTPS filtering is enabled, AdGuard performs a controlled local TLS interception: it decrypts the traffic using its local certificate, applies filtering rules, and then re-encrypts the traffic before sending it to the browser. The driver simply provides the system-level access needed for AdGuard to intercept these connections. -The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +#### SockFilter **SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. -Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: +SockFilter was first implemented in version 7.22.4, and it is still considered unstable — you may encounter bugs. Once fully tested and implemented, SockFilter has the potential to offer several advantages over other drivers: -- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. - **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. -- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. -When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. +#### WFP + +**WFP** (Windows Filtering Platform) is a Microsoft networking framework built into Windows that allows software to filter and monitor network packets at different layers of the system networking stack. AdGuard uses WFP to safely hook into the network flow of applications and apply filtering rules before the traffic reaches the browser or the Internet. [More information](https://learn.microsoft.com/en-us/windows/win32/fwp/windows-filtering-platform-architecture-overview). + +While it is a powerful driver, it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) and lower Internet speed for some users. + +#### TDI + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. ### AdGuard VPN diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index ab90a964b9f..5699b31b033 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -44,12 +44,8 @@ Before you start manually writing your own rules read our detailed [syntax guide Many websites gather information about their visitors, such as their IP addresses, browser and operating system details, screen resolution, and the webpage from which the user came or was redirected. Some websites use cookies to mark and identify your browser, save your personal settings and preferences. This allows them to “recognize” you on your next visit. Tracking protection safeguards your personal information from these data- and statistics-gathering systems. -![Tracking protection levels \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection1.png) - You can adjust the _Tracking Protection_ settings as needed. For example, you can prevent websites from receiving the search request that you used to find them on the Internet, automatically delete third- and first-party cookies, and disable location sharing in your browser, to prevent tracking of your whereabouts. -![Tracking protection custom features \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection2.png) - To learn everything about _Tracking protection_ and its many options, [read this article](/general/stealth-mode). ### Browsing security diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md index 62370bf3eb1..bec08d0c665 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Because of this, TDI-based traffic visibility becomes increasingly unstable. In AdGuard already treats the TDI driver as deprecated, and its complete removal is planned as the product evolves. +## Permanent solution + +From v7.22.4, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows/features/network/#sockfilter-and-other-network-drivers). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Temporary solution Certain Windows registry changes can force the browser to stop using AppContainer, causing its processes to run in a non-sandboxed mode again. Network Service stops using the WSK stack and falls back to a network path that the TDI driver can see. AdGuard then regains the ability to filter browser traffic. @@ -136,7 +144,3 @@ You should see the following policies active: If available, click _Reload policies_. Done! - -## Permanent solution - -We’re planning to add support for the SockFilter driver in the upcoming versions. It will fix the issue by solving conflicts in the WFP stack. [More information](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/general/github-repos.md b/i18n/nl/docusaurus-plugin-content-docs/current/general/github-repos.md new file mode 100644 index 00000000000..dfb164c44bc --- /dev/null +++ b/i18n/nl/docusaurus-plugin-content-docs/current/general/github-repos.md @@ -0,0 +1,238 @@ +--- +title: AdGuard’s GitHub repositories +sidebar_position: 9 +--- + +At AdGuard, our goal is to make the Internet safer, more comfortable, and more transparent. This commitment is reflected not only in our product features and strict privacy policies, but also in the fact that we keep our work as open as possible. That includes actively interacting with our community. + +This is why [all of our products have public repositories](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse) — online spaces where anybody can see what we are working on, report issues directly to AdGuard developers, and even contribute to our open-source projects. The repositories cover our ad-blocking apps, filters, browser extensions, DNS solutions, VPN tools, developer utilities, and more. There are different platforms that offer such functionality, but the most popular one by far is GitHub, and all AdGuard projects are stored there. + +This article lists the most important repositories by category, summarizes the purpose of each one, and gives a simple breakdown of what users can do there. + +:::tip + +Pro tip: Creating an issue on GitHub is the most effective way to bring the attention of AdGuard developers to a problem. Just make sure to check that a similar issue doesn’t already exist and describe the problem in a comprehensive but concise way. If it does exist, you can upvote it. + +::: + +## What is Github and its repositories + +Very simply put, you can think of GitHub as sort of Google Docs for code, where multiple people can work on the same project, track changes, and see who made which updates. It provides a central, cloud-based place to store your code so it’s accessible from anywhere. It also has teamwork tools for reviewing changes, fixing issues, and merging everyone’s work smoothly. + +GitHub is widely used for open-source projects, letting anyone view the code, suggest improvements, and contribute. + +A repository (often called “repo” for short) is the most basic element of GitHub. It’s a place where you can store your code, your files, and each file’s revision history. Repositories can have multiple collaborators and can be either public or private. + +## What can you do in AdGuard’s repositories + +You can find links to key repositories below in this article or visit the [general AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all) for a full list. In most repos, you can: + +- **View README file** on the main page: it gives you an introduction to the product and its repo + ![README file \*border](https://cdn.adtidy.org/content/blog/github-repos/see-readme.png) + +- **Check existing bug reports or feature requests**, comment and upvote + ![Check issues \*border](https://cdn.adtidy.org/content/blog/github-repos/check-issues.png) + +- **Create issues** to report bugs or request features + ![Create issues \*border](https://cdn.adtidy.org/content/blog/github-repos/create-issue.png) + +- **Check releases** for different versions and their changelogs (and install an older version if needed) + ![Check releases \*border](https://cdn.adtidy.org/content/blog/github-repos/check-releases.png) + +- **Install any older or beta version** if needed + ![Download builds \*border](https://cdn.adtidy.org/content/blog/github-repos/download-releases.png) + +:::note + +If you are new to GitHub, you’ll need to create a GitHub account in order to create new issues and comment on the existing ones. + +::: + +In open-source repos advanced users can also: + +- **Browse code** to understand product logic, what technologies are used and how they are implemented +- **Fork and contribute** via pull requests + +Whether you’re a casual user, technical expert, or a developer, AdGuard welcomes all community participation across its GitHub repos. + +## Legal documents + +### [LegalDocs](https://github.com/AdguardTeam/LegalDocs) + +As part of our commitment to transparency, we host all legal documents — such as End-User License Agreements, Privacy Policies, and Terms and Conditions — on GitHub. Our _LegalDocs_ repo lets anyone check the full history of changes to these documents. + +## AdGuard Ad Blocker products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdguardForAndroid](https://github.com/AdguardTeam/AdguardForAndroid) + +Repository of AdGuard for Android — an app that provides system-wide ad blocking. + +### [AdguardForiOS](https://github.com/AdguardTeam/AdguardForiOS) + +Repository of AdGuard for iOS — Safari content blocker with DNS and custom filters. Users can also check open-source code. + +### [AdguardForWindows](https://github.com/AdguardTeam/AdguardForWindows) + +Repository of AdGuard for Windows. Non-open-source; GitHub used as an open bug tracker. + +### [AdguardForMac](https://github.com/AdguardTeam/AdguardForMac) + +Repository of AdGuard for Mac — macOS standalone content blocker. Bug tracker only. + +### [AdguardBrowserExtension](https://github.com/AdguardTeam/AdguardBrowserExtension) + +Repository of AdGuard Browser Extension — extension that provides ad blocking with enhanced privacy for Chrome, Firefox, Opera, Edge. + +### [AdguardForSafari](https://github.com/AdguardTeam/AdGuardForSafari) + +Repository of AdGuard for Safari — Safari ad blocking extension for Mac. Users can also check open-sourced code. + +### [AdGuardCLI](https://github.com/AdguardTeam/AdGuardCLI) + +Repository of AdGuard for Linux — a command‑line interface for managing ad blocking. + +## AdGuard VPN products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdGuardVPNForiOS](https://github.com/AdguardTeam/AdGuardVPNForiOS) + +Repository of AdGuard VPN for iOS. Serves as an open bug tracker. + +### [AdGuardVPNForAndroid](https://github.com/AdguardTeam/AdGuardVPNForAndroid) + +Repository of AdGuard VPN for Android. Serves as an open bug tracker. + +### [AdGuardVPNForWindows](https://github.com/AdguardTeam/AdGuardVPNForWindows) + +Repository of AdGuard VPN for Windows. Serves as an open bug tracker. + +### [AdGuardVPNForMac](https://github.com/AdguardTeam/AdGuardVPNForMac) + +Repository of AdGuard VPN for Mac — app designed for macOS. + +### [AdGuardVPNExtension](https://github.com/AdguardTeam/AdGuardVPNExtension) + +Repository of AdGuard VPN Browser Extension. + +### [AdGuardVPNCLI](https://github.com/AdguardTeam/AdGuardVPNCLI) + +Repository of AdGuard VPN for Linux — a command‑line interface for managing VPN connection. The repo acts as a bug tracker. + +## DNS-based products + +### [AdGuardDNS](https://github.com/AdguardTeam/AdGuardDNS) + +Open-source repository that is also used for tracking bugs and issues related to AdGuard DNS service. Users can: + +- View and report DNS issues +- Suggest improvements + +### [AdGuardHome](https://github.com/AdguardTeam/AdGuardHome) + +Repository of AdGuard Home — free network-wide software for blocking ads and trackers via DNS. Users can: + +- Check and file bug reports or feature requests +- Review or contribute to code +- Download and install releases + +## Documentation and Knowledge bases + +Knowledge bases are aimed to help users better understand and use AdGuard. They describe each AdGuard product in detail: from feature overviews and problem-solving guides to advanced setting manuals and API documentations. In the repositories users can: + +- Suggest corrections or edits to knowledge base articles +- Propose new articles +- Test or run the local version + +### [KnowledgeBase](https://github.com/AdguardTeam/KnowledgeBase) + +Central documentation for AdGuard Ad Blocker and the technologies related to it. + +### [KnowledgeBaseDNS](https://github.com/AdguardTeam/KnowledgeBaseDNS) + +Detailed feature overview, troubleshooting guides and documentation for AdGuard DNS (both Public and Private), AdGuard Home, and everything related to them. + +### [KnowledgeBaseVPN](https://github.com/AdguardTeam/KnowledgeBaseVPN) + +Detailed feature overview and troubleshooting guides for AdGuard VPN. + +### [KnowledgeBaseMail](https://github.com/AdguardTeam/KnowledgeBaseMail) + +Detailed feature overview and troubleshooting guides of AdGuard Mail. + +## Core libraries + +### [CoreLibs](https://github.com/AdguardTeam/CoreLibs) + +AdGuard’s cross-platform core filtering engine. Used in Android, Windows, and Mac products. Users can: + +- Explore filtering logic and DNS handling +- Report bugs and suggest features via Issues + +### [DNSLibs](https://github.com/AdguardTeam/DNSLibs) + +A DNS library used by CoreLibs and AdGuardHome. Users can: + +- Review and contribute to low-level DNS implementation +- Suggest optimizations + +### [VPNLibs](https://github.com/AdguardTeam/VPNLibs) + +Shared codebase used in AdGuard VPN products across platforms for AdGuard VPN protocol implementation. Users can: + +- Contribute to VPN stack behavior +- Report or view performance issues and bugs + +## Core ad blocking and filtering technologies + +### [AdguardFilters](https://github.com/AdguardTeam/AdguardFilters) + +Contains AdGuard’s core filter lists. Users can: + +- View and download filter lists +- Create issues to report false positives or suggest new rules +- Monitor updates to filter logic + +### [AdGuardSDNSFilter](https://github.com/AdguardTeam/AdGuardSDNSFilter) + +Repository of AdGuard DNS filter — the main DNS-level blocking list used in AdGuard DNS and DNS filtering features. Users can: + +- Inspect the current rule set +- Propose changes or additions + +### [AGLint](https://github.com/AdguardTeam/AGLint) + +A linter for adblock filter list syntax. Users can: + +- Install AGLint to check their projects for rule issues +- Contribute to lint rules + +### [Scriptlets](https://github.com/AdguardTeam/Scriptlets) + +JavaScript helpers used in filtering rules. Users can: + +- Explore available scriptlets +- Submit pull requests for new scriptlets + +### [tsurlfilter](https://github.com/AdguardTeam/tsurlfilter) + +TypeScript content blocker library for browser extensions. Users can: + +- Explore how filtering logic is implemented +- Contribute fixes and features + +## There’s more + +Above, we listed 27 main public AdGuard repositories out of 96 total. If you want to go down the rabbit hole, you can [find the rest on the AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse). + +We’ll be waiting for your feedback there! Stay safe online and offline. diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/general/how-to-install.md b/i18n/nl/docusaurus-plugin-content-docs/current/general/how-to-install.md index 106a29529a8..4ba78d7a094 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/general/how-to-install.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/general/how-to-install.md @@ -1,6 +1,6 @@ --- title: How to install AdGuard -sidebar_position: 9 +sidebar_position: 10 --- Depending on which AdGuard app or browser extension you want to install, follow one of these links to find the relevant article: diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md index 3953f47d26f..05642d350b0 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md @@ -43,6 +43,14 @@ Here you can choose which proxy AdGuard should use to download filter updates or ## Use SockFilter driver -Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. +Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. If this option is disabled, AdGuard will switch to the older WFP driver instead. -If this option is disabled, AdGuard will switch to the older WFP driver instead. +SockFilter was first introduced in v8.0 RC. It is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md index 251e49cf286..1ab588bb16c 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Because of this, TDI-based traffic visibility becomes increasingly unstable. In AdGuard already treats the TDI driver as deprecated, and its complete removal is planned as the product evolves. +## Permanent solution + +From v8.0 RC, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows-8/settings/app-settings/network-settings/). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Temporary solution Certain Windows registry changes can force the browser to stop using AppContainer, causing its processes to run in a non-sandboxed mode again. Network Service stops using the WSK stack and falls back to a network path that the TDI driver can see. AdGuard then regains the ability to filter browser traffic. @@ -123,7 +131,3 @@ You should see the following policies active: If available, click _Reload policies_. Done! - -## Permanent solution - -We’re planning to add support for the SockFilter driver in the upcoming versions. It will fix the issue by solving conflicts in the WFP stack. [More information](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index 5945618ea9c..f8074e9cfa1 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -17,23 +17,35 @@ In this module you can select the checkbox _Use AdGuard as an HTTP proxy_ to use At last, there is a section with proxy settings. There you can specify which proxy server AdGuard should use to update filters, get new versions, and so on. -### SockFilter and other network drivers +### Enable traffic filtering -In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. +Traffic filtering is the core mechanism that allows AdGuard to inspect and control the network traffic generated by applications on your computer. When it is enabled, AdGuard intercepts outgoing and incoming connections and checks them against its filtering rules. If a request matches a blocking rule, AdGuard can block it, modify it, or allow it depending on the configuration. In AdGuard for Windows, this interception is implemented through network drivers. -**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. +If HTTPS filtering is enabled, AdGuard performs a controlled local TLS interception: it decrypts the traffic using its local certificate, applies filtering rules, and then re-encrypts the traffic before sending it to the browser. The driver simply provides the system-level access needed for AdGuard to intercept these connections. -The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +#### SockFilter **SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. -Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: +SockFilter was first implemented in version 7.22.4, and it is still considered unstable — you may encounter bugs. Once fully tested and implemented, SockFilter has the potential to offer several advantages over other drivers: -- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. - **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. -- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. -When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. +#### WFP + +**WFP** (Windows Filtering Platform) is a Microsoft networking framework built into Windows that allows software to filter and monitor network packets at different layers of the system networking stack. AdGuard uses WFP to safely hook into the network flow of applications and apply filtering rules before the traffic reaches the browser or the Internet. [More information](https://learn.microsoft.com/en-us/windows/win32/fwp/windows-filtering-platform-architecture-overview). + +While it is a powerful driver, it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) and lower Internet speed for some users. + +#### TDI + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. ### AdGuard VPN diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index ab90a964b9f..5699b31b033 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -44,12 +44,8 @@ Before you start manually writing your own rules read our detailed [syntax guide Many websites gather information about their visitors, such as their IP addresses, browser and operating system details, screen resolution, and the webpage from which the user came or was redirected. Some websites use cookies to mark and identify your browser, save your personal settings and preferences. This allows them to “recognize” you on your next visit. Tracking protection safeguards your personal information from these data- and statistics-gathering systems. -![Tracking protection levels \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection1.png) - You can adjust the _Tracking Protection_ settings as needed. For example, you can prevent websites from receiving the search request that you used to find them on the Internet, automatically delete third- and first-party cookies, and disable location sharing in your browser, to prevent tracking of your whereabouts. -![Tracking protection custom features \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection2.png) - To learn everything about _Tracking protection_ and its many options, [read this article](/general/stealth-mode). ### Browsing security diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md index 62370bf3eb1..bec08d0c665 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Because of this, TDI-based traffic visibility becomes increasingly unstable. In AdGuard already treats the TDI driver as deprecated, and its complete removal is planned as the product evolves. +## Permanent solution + +From v7.22.4, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows/features/network/#sockfilter-and-other-network-drivers). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Temporary solution Certain Windows registry changes can force the browser to stop using AppContainer, causing its processes to run in a non-sandboxed mode again. Network Service stops using the WSK stack and falls back to a network path that the TDI driver can see. AdGuard then regains the ability to filter browser traffic. @@ -136,7 +144,3 @@ You should see the following policies active: If available, click _Reload policies_. Done! - -## Permanent solution - -We’re planning to add support for the SockFilter driver in the upcoming versions. It will fix the issue by solving conflicts in the WFP stack. [More information](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/no/docusaurus-plugin-content-docs/current/general/github-repos.md b/i18n/no/docusaurus-plugin-content-docs/current/general/github-repos.md new file mode 100644 index 00000000000..dfb164c44bc --- /dev/null +++ b/i18n/no/docusaurus-plugin-content-docs/current/general/github-repos.md @@ -0,0 +1,238 @@ +--- +title: AdGuard’s GitHub repositories +sidebar_position: 9 +--- + +At AdGuard, our goal is to make the Internet safer, more comfortable, and more transparent. This commitment is reflected not only in our product features and strict privacy policies, but also in the fact that we keep our work as open as possible. That includes actively interacting with our community. + +This is why [all of our products have public repositories](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse) — online spaces where anybody can see what we are working on, report issues directly to AdGuard developers, and even contribute to our open-source projects. The repositories cover our ad-blocking apps, filters, browser extensions, DNS solutions, VPN tools, developer utilities, and more. There are different platforms that offer such functionality, but the most popular one by far is GitHub, and all AdGuard projects are stored there. + +This article lists the most important repositories by category, summarizes the purpose of each one, and gives a simple breakdown of what users can do there. + +:::tip + +Pro tip: Creating an issue on GitHub is the most effective way to bring the attention of AdGuard developers to a problem. Just make sure to check that a similar issue doesn’t already exist and describe the problem in a comprehensive but concise way. If it does exist, you can upvote it. + +::: + +## What is Github and its repositories + +Very simply put, you can think of GitHub as sort of Google Docs for code, where multiple people can work on the same project, track changes, and see who made which updates. It provides a central, cloud-based place to store your code so it’s accessible from anywhere. It also has teamwork tools for reviewing changes, fixing issues, and merging everyone’s work smoothly. + +GitHub is widely used for open-source projects, letting anyone view the code, suggest improvements, and contribute. + +A repository (often called “repo” for short) is the most basic element of GitHub. It’s a place where you can store your code, your files, and each file’s revision history. Repositories can have multiple collaborators and can be either public or private. + +## What can you do in AdGuard’s repositories + +You can find links to key repositories below in this article or visit the [general AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all) for a full list. In most repos, you can: + +- **View README file** on the main page: it gives you an introduction to the product and its repo + ![README file \*border](https://cdn.adtidy.org/content/blog/github-repos/see-readme.png) + +- **Check existing bug reports or feature requests**, comment and upvote + ![Check issues \*border](https://cdn.adtidy.org/content/blog/github-repos/check-issues.png) + +- **Create issues** to report bugs or request features + ![Create issues \*border](https://cdn.adtidy.org/content/blog/github-repos/create-issue.png) + +- **Check releases** for different versions and their changelogs (and install an older version if needed) + ![Check releases \*border](https://cdn.adtidy.org/content/blog/github-repos/check-releases.png) + +- **Install any older or beta version** if needed + ![Download builds \*border](https://cdn.adtidy.org/content/blog/github-repos/download-releases.png) + +:::note + +If you are new to GitHub, you’ll need to create a GitHub account in order to create new issues and comment on the existing ones. + +::: + +In open-source repos advanced users can also: + +- **Browse code** to understand product logic, what technologies are used and how they are implemented +- **Fork and contribute** via pull requests + +Whether you’re a casual user, technical expert, or a developer, AdGuard welcomes all community participation across its GitHub repos. + +## Legal documents + +### [LegalDocs](https://github.com/AdguardTeam/LegalDocs) + +As part of our commitment to transparency, we host all legal documents — such as End-User License Agreements, Privacy Policies, and Terms and Conditions — on GitHub. Our _LegalDocs_ repo lets anyone check the full history of changes to these documents. + +## AdGuard Ad Blocker products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdguardForAndroid](https://github.com/AdguardTeam/AdguardForAndroid) + +Repository of AdGuard for Android — an app that provides system-wide ad blocking. + +### [AdguardForiOS](https://github.com/AdguardTeam/AdguardForiOS) + +Repository of AdGuard for iOS — Safari content blocker with DNS and custom filters. Users can also check open-source code. + +### [AdguardForWindows](https://github.com/AdguardTeam/AdguardForWindows) + +Repository of AdGuard for Windows. Non-open-source; GitHub used as an open bug tracker. + +### [AdguardForMac](https://github.com/AdguardTeam/AdguardForMac) + +Repository of AdGuard for Mac — macOS standalone content blocker. Bug tracker only. + +### [AdguardBrowserExtension](https://github.com/AdguardTeam/AdguardBrowserExtension) + +Repository of AdGuard Browser Extension — extension that provides ad blocking with enhanced privacy for Chrome, Firefox, Opera, Edge. + +### [AdguardForSafari](https://github.com/AdguardTeam/AdGuardForSafari) + +Repository of AdGuard for Safari — Safari ad blocking extension for Mac. Users can also check open-sourced code. + +### [AdGuardCLI](https://github.com/AdguardTeam/AdGuardCLI) + +Repository of AdGuard for Linux — a command‑line interface for managing ad blocking. + +## AdGuard VPN products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdGuardVPNForiOS](https://github.com/AdguardTeam/AdGuardVPNForiOS) + +Repository of AdGuard VPN for iOS. Serves as an open bug tracker. + +### [AdGuardVPNForAndroid](https://github.com/AdguardTeam/AdGuardVPNForAndroid) + +Repository of AdGuard VPN for Android. Serves as an open bug tracker. + +### [AdGuardVPNForWindows](https://github.com/AdguardTeam/AdGuardVPNForWindows) + +Repository of AdGuard VPN for Windows. Serves as an open bug tracker. + +### [AdGuardVPNForMac](https://github.com/AdguardTeam/AdGuardVPNForMac) + +Repository of AdGuard VPN for Mac — app designed for macOS. + +### [AdGuardVPNExtension](https://github.com/AdguardTeam/AdGuardVPNExtension) + +Repository of AdGuard VPN Browser Extension. + +### [AdGuardVPNCLI](https://github.com/AdguardTeam/AdGuardVPNCLI) + +Repository of AdGuard VPN for Linux — a command‑line interface for managing VPN connection. The repo acts as a bug tracker. + +## DNS-based products + +### [AdGuardDNS](https://github.com/AdguardTeam/AdGuardDNS) + +Open-source repository that is also used for tracking bugs and issues related to AdGuard DNS service. Users can: + +- View and report DNS issues +- Suggest improvements + +### [AdGuardHome](https://github.com/AdguardTeam/AdGuardHome) + +Repository of AdGuard Home — free network-wide software for blocking ads and trackers via DNS. Users can: + +- Check and file bug reports or feature requests +- Review or contribute to code +- Download and install releases + +## Documentation and Knowledge bases + +Knowledge bases are aimed to help users better understand and use AdGuard. They describe each AdGuard product in detail: from feature overviews and problem-solving guides to advanced setting manuals and API documentations. In the repositories users can: + +- Suggest corrections or edits to knowledge base articles +- Propose new articles +- Test or run the local version + +### [KnowledgeBase](https://github.com/AdguardTeam/KnowledgeBase) + +Central documentation for AdGuard Ad Blocker and the technologies related to it. + +### [KnowledgeBaseDNS](https://github.com/AdguardTeam/KnowledgeBaseDNS) + +Detailed feature overview, troubleshooting guides and documentation for AdGuard DNS (both Public and Private), AdGuard Home, and everything related to them. + +### [KnowledgeBaseVPN](https://github.com/AdguardTeam/KnowledgeBaseVPN) + +Detailed feature overview and troubleshooting guides for AdGuard VPN. + +### [KnowledgeBaseMail](https://github.com/AdguardTeam/KnowledgeBaseMail) + +Detailed feature overview and troubleshooting guides of AdGuard Mail. + +## Core libraries + +### [CoreLibs](https://github.com/AdguardTeam/CoreLibs) + +AdGuard’s cross-platform core filtering engine. Used in Android, Windows, and Mac products. Users can: + +- Explore filtering logic and DNS handling +- Report bugs and suggest features via Issues + +### [DNSLibs](https://github.com/AdguardTeam/DNSLibs) + +A DNS library used by CoreLibs and AdGuardHome. Users can: + +- Review and contribute to low-level DNS implementation +- Suggest optimizations + +### [VPNLibs](https://github.com/AdguardTeam/VPNLibs) + +Shared codebase used in AdGuard VPN products across platforms for AdGuard VPN protocol implementation. Users can: + +- Contribute to VPN stack behavior +- Report or view performance issues and bugs + +## Core ad blocking and filtering technologies + +### [AdguardFilters](https://github.com/AdguardTeam/AdguardFilters) + +Contains AdGuard’s core filter lists. Users can: + +- View and download filter lists +- Create issues to report false positives or suggest new rules +- Monitor updates to filter logic + +### [AdGuardSDNSFilter](https://github.com/AdguardTeam/AdGuardSDNSFilter) + +Repository of AdGuard DNS filter — the main DNS-level blocking list used in AdGuard DNS and DNS filtering features. Users can: + +- Inspect the current rule set +- Propose changes or additions + +### [AGLint](https://github.com/AdguardTeam/AGLint) + +A linter for adblock filter list syntax. Users can: + +- Install AGLint to check their projects for rule issues +- Contribute to lint rules + +### [Scriptlets](https://github.com/AdguardTeam/Scriptlets) + +JavaScript helpers used in filtering rules. Users can: + +- Explore available scriptlets +- Submit pull requests for new scriptlets + +### [tsurlfilter](https://github.com/AdguardTeam/tsurlfilter) + +TypeScript content blocker library for browser extensions. Users can: + +- Explore how filtering logic is implemented +- Contribute fixes and features + +## There’s more + +Above, we listed 27 main public AdGuard repositories out of 96 total. If you want to go down the rabbit hole, you can [find the rest on the AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse). + +We’ll be waiting for your feedback there! Stay safe online and offline. diff --git a/i18n/no/docusaurus-plugin-content-docs/current/general/how-to-install.md b/i18n/no/docusaurus-plugin-content-docs/current/general/how-to-install.md index 106a29529a8..4ba78d7a094 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/general/how-to-install.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/general/how-to-install.md @@ -1,6 +1,6 @@ --- title: How to install AdGuard -sidebar_position: 9 +sidebar_position: 10 --- Depending on which AdGuard app or browser extension you want to install, follow one of these links to find the relevant article: diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md index 3953f47d26f..05642d350b0 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md @@ -43,6 +43,14 @@ Here you can choose which proxy AdGuard should use to download filter updates or ## Use SockFilter driver -Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. +Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. If this option is disabled, AdGuard will switch to the older WFP driver instead. -If this option is disabled, AdGuard will switch to the older WFP driver instead. +SockFilter was first introduced in v8.0 RC. It is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md index 251e49cf286..1ab588bb16c 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Because of this, TDI-based traffic visibility becomes increasingly unstable. In AdGuard already treats the TDI driver as deprecated, and its complete removal is planned as the product evolves. +## Permanent solution + +From v8.0 RC, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows-8/settings/app-settings/network-settings/). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Temporary solution Certain Windows registry changes can force the browser to stop using AppContainer, causing its processes to run in a non-sandboxed mode again. Network Service stops using the WSK stack and falls back to a network path that the TDI driver can see. AdGuard then regains the ability to filter browser traffic. @@ -123,7 +131,3 @@ You should see the following policies active: If available, click _Reload policies_. Done! - -## Permanent solution - -We’re planning to add support for the SockFilter driver in the upcoming versions. It will fix the issue by solving conflicts in the WFP stack. [More information](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index 5945618ea9c..f8074e9cfa1 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -17,23 +17,35 @@ In this module you can select the checkbox _Use AdGuard as an HTTP proxy_ to use At last, there is a section with proxy settings. There you can specify which proxy server AdGuard should use to update filters, get new versions, and so on. -### SockFilter and other network drivers +### Enable traffic filtering -In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. +Traffic filtering is the core mechanism that allows AdGuard to inspect and control the network traffic generated by applications on your computer. When it is enabled, AdGuard intercepts outgoing and incoming connections and checks them against its filtering rules. If a request matches a blocking rule, AdGuard can block it, modify it, or allow it depending on the configuration. In AdGuard for Windows, this interception is implemented through network drivers. -**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. +If HTTPS filtering is enabled, AdGuard performs a controlled local TLS interception: it decrypts the traffic using its local certificate, applies filtering rules, and then re-encrypts the traffic before sending it to the browser. The driver simply provides the system-level access needed for AdGuard to intercept these connections. -The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +#### SockFilter **SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. -Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: +SockFilter was first implemented in version 7.22.4, and it is still considered unstable — you may encounter bugs. Once fully tested and implemented, SockFilter has the potential to offer several advantages over other drivers: -- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. - **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. -- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. -When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. +#### WFP + +**WFP** (Windows Filtering Platform) is a Microsoft networking framework built into Windows that allows software to filter and monitor network packets at different layers of the system networking stack. AdGuard uses WFP to safely hook into the network flow of applications and apply filtering rules before the traffic reaches the browser or the Internet. [More information](https://learn.microsoft.com/en-us/windows/win32/fwp/windows-filtering-platform-architecture-overview). + +While it is a powerful driver, it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) and lower Internet speed for some users. + +#### TDI + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. ### AdGuard VPN diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index ab90a964b9f..5699b31b033 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -44,12 +44,8 @@ Before you start manually writing your own rules read our detailed [syntax guide Many websites gather information about their visitors, such as their IP addresses, browser and operating system details, screen resolution, and the webpage from which the user came or was redirected. Some websites use cookies to mark and identify your browser, save your personal settings and preferences. This allows them to “recognize” you on your next visit. Tracking protection safeguards your personal information from these data- and statistics-gathering systems. -![Tracking protection levels \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection1.png) - You can adjust the _Tracking Protection_ settings as needed. For example, you can prevent websites from receiving the search request that you used to find them on the Internet, automatically delete third- and first-party cookies, and disable location sharing in your browser, to prevent tracking of your whereabouts. -![Tracking protection custom features \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection2.png) - To learn everything about _Tracking protection_ and its many options, [read this article](/general/stealth-mode). ### Browsing security diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md index 62370bf3eb1..bec08d0c665 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Because of this, TDI-based traffic visibility becomes increasingly unstable. In AdGuard already treats the TDI driver as deprecated, and its complete removal is planned as the product evolves. +## Permanent solution + +From v7.22.4, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows/features/network/#sockfilter-and-other-network-drivers). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Temporary solution Certain Windows registry changes can force the browser to stop using AppContainer, causing its processes to run in a non-sandboxed mode again. Network Service stops using the WSK stack and falls back to a network path that the TDI driver can see. AdGuard then regains the ability to filter browser traffic. @@ -136,7 +144,3 @@ You should see the following policies active: If available, click _Reload policies_. Done! - -## Permanent solution - -We’re planning to add support for the SockFilter driver in the upcoming versions. It will fix the issue by solving conflicts in the WFP stack. [More information](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/general/github-repos.md b/i18n/pl/docusaurus-plugin-content-docs/current/general/github-repos.md new file mode 100644 index 00000000000..dfb164c44bc --- /dev/null +++ b/i18n/pl/docusaurus-plugin-content-docs/current/general/github-repos.md @@ -0,0 +1,238 @@ +--- +title: AdGuard’s GitHub repositories +sidebar_position: 9 +--- + +At AdGuard, our goal is to make the Internet safer, more comfortable, and more transparent. This commitment is reflected not only in our product features and strict privacy policies, but also in the fact that we keep our work as open as possible. That includes actively interacting with our community. + +This is why [all of our products have public repositories](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse) — online spaces where anybody can see what we are working on, report issues directly to AdGuard developers, and even contribute to our open-source projects. The repositories cover our ad-blocking apps, filters, browser extensions, DNS solutions, VPN tools, developer utilities, and more. There are different platforms that offer such functionality, but the most popular one by far is GitHub, and all AdGuard projects are stored there. + +This article lists the most important repositories by category, summarizes the purpose of each one, and gives a simple breakdown of what users can do there. + +:::tip + +Pro tip: Creating an issue on GitHub is the most effective way to bring the attention of AdGuard developers to a problem. Just make sure to check that a similar issue doesn’t already exist and describe the problem in a comprehensive but concise way. If it does exist, you can upvote it. + +::: + +## What is Github and its repositories + +Very simply put, you can think of GitHub as sort of Google Docs for code, where multiple people can work on the same project, track changes, and see who made which updates. It provides a central, cloud-based place to store your code so it’s accessible from anywhere. It also has teamwork tools for reviewing changes, fixing issues, and merging everyone’s work smoothly. + +GitHub is widely used for open-source projects, letting anyone view the code, suggest improvements, and contribute. + +A repository (often called “repo” for short) is the most basic element of GitHub. It’s a place where you can store your code, your files, and each file’s revision history. Repositories can have multiple collaborators and can be either public or private. + +## What can you do in AdGuard’s repositories + +You can find links to key repositories below in this article or visit the [general AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all) for a full list. In most repos, you can: + +- **View README file** on the main page: it gives you an introduction to the product and its repo + ![README file \*border](https://cdn.adtidy.org/content/blog/github-repos/see-readme.png) + +- **Check existing bug reports or feature requests**, comment and upvote + ![Check issues \*border](https://cdn.adtidy.org/content/blog/github-repos/check-issues.png) + +- **Create issues** to report bugs or request features + ![Create issues \*border](https://cdn.adtidy.org/content/blog/github-repos/create-issue.png) + +- **Check releases** for different versions and their changelogs (and install an older version if needed) + ![Check releases \*border](https://cdn.adtidy.org/content/blog/github-repos/check-releases.png) + +- **Install any older or beta version** if needed + ![Download builds \*border](https://cdn.adtidy.org/content/blog/github-repos/download-releases.png) + +:::note + +If you are new to GitHub, you’ll need to create a GitHub account in order to create new issues and comment on the existing ones. + +::: + +In open-source repos advanced users can also: + +- **Browse code** to understand product logic, what technologies are used and how they are implemented +- **Fork and contribute** via pull requests + +Whether you’re a casual user, technical expert, or a developer, AdGuard welcomes all community participation across its GitHub repos. + +## Legal documents + +### [LegalDocs](https://github.com/AdguardTeam/LegalDocs) + +As part of our commitment to transparency, we host all legal documents — such as End-User License Agreements, Privacy Policies, and Terms and Conditions — on GitHub. Our _LegalDocs_ repo lets anyone check the full history of changes to these documents. + +## AdGuard Ad Blocker products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdguardForAndroid](https://github.com/AdguardTeam/AdguardForAndroid) + +Repository of AdGuard for Android — an app that provides system-wide ad blocking. + +### [AdguardForiOS](https://github.com/AdguardTeam/AdguardForiOS) + +Repository of AdGuard for iOS — Safari content blocker with DNS and custom filters. Users can also check open-source code. + +### [AdguardForWindows](https://github.com/AdguardTeam/AdguardForWindows) + +Repository of AdGuard for Windows. Non-open-source; GitHub used as an open bug tracker. + +### [AdguardForMac](https://github.com/AdguardTeam/AdguardForMac) + +Repository of AdGuard for Mac — macOS standalone content blocker. Bug tracker only. + +### [AdguardBrowserExtension](https://github.com/AdguardTeam/AdguardBrowserExtension) + +Repository of AdGuard Browser Extension — extension that provides ad blocking with enhanced privacy for Chrome, Firefox, Opera, Edge. + +### [AdguardForSafari](https://github.com/AdguardTeam/AdGuardForSafari) + +Repository of AdGuard for Safari — Safari ad blocking extension for Mac. Users can also check open-sourced code. + +### [AdGuardCLI](https://github.com/AdguardTeam/AdGuardCLI) + +Repository of AdGuard for Linux — a command‑line interface for managing ad blocking. + +## AdGuard VPN products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdGuardVPNForiOS](https://github.com/AdguardTeam/AdGuardVPNForiOS) + +Repository of AdGuard VPN for iOS. Serves as an open bug tracker. + +### [AdGuardVPNForAndroid](https://github.com/AdguardTeam/AdGuardVPNForAndroid) + +Repository of AdGuard VPN for Android. Serves as an open bug tracker. + +### [AdGuardVPNForWindows](https://github.com/AdguardTeam/AdGuardVPNForWindows) + +Repository of AdGuard VPN for Windows. Serves as an open bug tracker. + +### [AdGuardVPNForMac](https://github.com/AdguardTeam/AdGuardVPNForMac) + +Repository of AdGuard VPN for Mac — app designed for macOS. + +### [AdGuardVPNExtension](https://github.com/AdguardTeam/AdGuardVPNExtension) + +Repository of AdGuard VPN Browser Extension. + +### [AdGuardVPNCLI](https://github.com/AdguardTeam/AdGuardVPNCLI) + +Repository of AdGuard VPN for Linux — a command‑line interface for managing VPN connection. The repo acts as a bug tracker. + +## DNS-based products + +### [AdGuardDNS](https://github.com/AdguardTeam/AdGuardDNS) + +Open-source repository that is also used for tracking bugs and issues related to AdGuard DNS service. Users can: + +- View and report DNS issues +- Suggest improvements + +### [AdGuardHome](https://github.com/AdguardTeam/AdGuardHome) + +Repository of AdGuard Home — free network-wide software for blocking ads and trackers via DNS. Users can: + +- Check and file bug reports or feature requests +- Review or contribute to code +- Download and install releases + +## Documentation and Knowledge bases + +Knowledge bases are aimed to help users better understand and use AdGuard. They describe each AdGuard product in detail: from feature overviews and problem-solving guides to advanced setting manuals and API documentations. In the repositories users can: + +- Suggest corrections or edits to knowledge base articles +- Propose new articles +- Test or run the local version + +### [KnowledgeBase](https://github.com/AdguardTeam/KnowledgeBase) + +Central documentation for AdGuard Ad Blocker and the technologies related to it. + +### [KnowledgeBaseDNS](https://github.com/AdguardTeam/KnowledgeBaseDNS) + +Detailed feature overview, troubleshooting guides and documentation for AdGuard DNS (both Public and Private), AdGuard Home, and everything related to them. + +### [KnowledgeBaseVPN](https://github.com/AdguardTeam/KnowledgeBaseVPN) + +Detailed feature overview and troubleshooting guides for AdGuard VPN. + +### [KnowledgeBaseMail](https://github.com/AdguardTeam/KnowledgeBaseMail) + +Detailed feature overview and troubleshooting guides of AdGuard Mail. + +## Core libraries + +### [CoreLibs](https://github.com/AdguardTeam/CoreLibs) + +AdGuard’s cross-platform core filtering engine. Used in Android, Windows, and Mac products. Users can: + +- Explore filtering logic and DNS handling +- Report bugs and suggest features via Issues + +### [DNSLibs](https://github.com/AdguardTeam/DNSLibs) + +A DNS library used by CoreLibs and AdGuardHome. Users can: + +- Review and contribute to low-level DNS implementation +- Suggest optimizations + +### [VPNLibs](https://github.com/AdguardTeam/VPNLibs) + +Shared codebase used in AdGuard VPN products across platforms for AdGuard VPN protocol implementation. Users can: + +- Contribute to VPN stack behavior +- Report or view performance issues and bugs + +## Core ad blocking and filtering technologies + +### [AdguardFilters](https://github.com/AdguardTeam/AdguardFilters) + +Contains AdGuard’s core filter lists. Users can: + +- View and download filter lists +- Create issues to report false positives or suggest new rules +- Monitor updates to filter logic + +### [AdGuardSDNSFilter](https://github.com/AdguardTeam/AdGuardSDNSFilter) + +Repository of AdGuard DNS filter — the main DNS-level blocking list used in AdGuard DNS and DNS filtering features. Users can: + +- Inspect the current rule set +- Propose changes or additions + +### [AGLint](https://github.com/AdguardTeam/AGLint) + +A linter for adblock filter list syntax. Users can: + +- Install AGLint to check their projects for rule issues +- Contribute to lint rules + +### [Scriptlets](https://github.com/AdguardTeam/Scriptlets) + +JavaScript helpers used in filtering rules. Users can: + +- Explore available scriptlets +- Submit pull requests for new scriptlets + +### [tsurlfilter](https://github.com/AdguardTeam/tsurlfilter) + +TypeScript content blocker library for browser extensions. Users can: + +- Explore how filtering logic is implemented +- Contribute fixes and features + +## There’s more + +Above, we listed 27 main public AdGuard repositories out of 96 total. If you want to go down the rabbit hole, you can [find the rest on the AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse). + +We’ll be waiting for your feedback there! Stay safe online and offline. diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/general/how-to-install.md b/i18n/pl/docusaurus-plugin-content-docs/current/general/how-to-install.md index 106a29529a8..4ba78d7a094 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/general/how-to-install.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/general/how-to-install.md @@ -1,6 +1,6 @@ --- title: How to install AdGuard -sidebar_position: 9 +sidebar_position: 10 --- Depending on which AdGuard app or browser extension you want to install, follow one of these links to find the relevant article: diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md index 2211c84aaeb..b860bda9e8e 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md @@ -43,6 +43,14 @@ Here you can choose which proxy AdGuard should use to download filter updates or ## Use SockFilter driver -Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. +Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. If this option is disabled, AdGuard will switch to the older WFP driver instead. -If this option is disabled, AdGuard will switch to the older WFP driver instead. +SockFilter was first introduced in v8.0 RC. It is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md index 10cd3af8150..eb366af601b 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Because of this, TDI-based traffic visibility becomes increasingly unstable. In AdGuard already treats the TDI driver as deprecated, and its complete removal is planned as the product evolves. +## Permanent solution + +From v8.0 RC, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows-8/settings/app-settings/network-settings/). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Temporary solution Certain Windows registry changes can force the browser to stop using AppContainer, causing its processes to run in a non-sandboxed mode again. Network Service stops using the WSK stack and falls back to a network path that the TDI driver can see. AdGuard then regains the ability to filter browser traffic. @@ -123,7 +131,3 @@ You should see the following policies active: If available, click _Reload policies_. Pronto! - -## Permanent solution - -We’re planning to add support for the SockFilter driver in the upcoming versions. It will fix the issue by solving conflicts in the WFP stack. [More information](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index 23859d3cce0..2bb02447249 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -17,23 +17,35 @@ Neste módulo você pode selecionar a caixa de verificação _Usar AdGuard como Por fim, há uma seção com configurações de proxy. Lá você pode especificar qual servidor proxy o AdGuard deve usar para atualizar filtros, obter novas versões e assim por diante. -### SockFilter and other network drivers +### Enable traffic filtering -In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. +Traffic filtering is the core mechanism that allows AdGuard to inspect and control the network traffic generated by applications on your computer. When it is enabled, AdGuard intercepts outgoing and incoming connections and checks them against its filtering rules. If a request matches a blocking rule, AdGuard can block it, modify it, or allow it depending on the configuration. In AdGuard for Windows, this interception is implemented through network drivers. -**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. +If HTTPS filtering is enabled, AdGuard performs a controlled local TLS interception: it decrypts the traffic using its local certificate, applies filtering rules, and then re-encrypts the traffic before sending it to the browser. The driver simply provides the system-level access needed for AdGuard to intercept these connections. -The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +#### SockFilter **SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. -Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: +SockFilter was first implemented in version 7.22.4, and it is still considered unstable — you may encounter bugs. Once fully tested and implemented, SockFilter has the potential to offer several advantages over other drivers: -- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. - **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. -- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. -When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. +#### WFP + +**WFP** (Windows Filtering Platform) is a Microsoft networking framework built into Windows that allows software to filter and monitor network packets at different layers of the system networking stack. AdGuard uses WFP to safely hook into the network flow of applications and apply filtering rules before the traffic reaches the browser or the Internet. [More information](https://learn.microsoft.com/en-us/windows/win32/fwp/windows-filtering-platform-architecture-overview). + +While it is a powerful driver, it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) and lower Internet speed for some users. + +#### TDI + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. ### AdGuard VPN diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index 778b0bcf1cd..400ef4e08e7 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -44,12 +44,8 @@ Antes de começar a escrever manualmente suas próprias regras, leia nosso [guia Many websites gather information about their visitors, such as their IP addresses, browser and operating system details, screen resolution, and the webpage from which the user came or was redirected. Some websites use cookies to mark and identify your browser, save your personal settings and preferences. This allows them to “recognize” you on your next visit. Tracking protection safeguards your personal information from these data- and statistics-gathering systems. -![Tracking protection levels \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection1.png) - You can adjust the _Tracking Protection_ settings as needed. For example, you can prevent websites from receiving the search request that you used to find them on the Internet, automatically delete third- and first-party cookies, and disable location sharing in your browser, to prevent tracking of your whereabouts. -![Tracking protection custom features \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection2.png) - To learn everything about _Tracking protection_ and its many options, [read this article](/general/stealth-mode). ### Segurança da navegação diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md index 10cb00f6e9f..8d7df3fe00a 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Because of this, TDI-based traffic visibility becomes increasingly unstable. In AdGuard already treats the TDI driver as deprecated, and its complete removal is planned as the product evolves. +## Permanent solution + +From v7.22.4, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows/features/network/#sockfilter-and-other-network-drivers). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Temporary solution Certain Windows registry changes can force the browser to stop using AppContainer, causing its processes to run in a non-sandboxed mode again. Network Service stops using the WSK stack and falls back to a network path that the TDI driver can see. AdGuard then regains the ability to filter browser traffic. @@ -136,7 +144,3 @@ You should see the following policies active: If available, click _Reload policies_. Pronto! - -## Permanent solution - -We’re planning to add support for the SockFilter driver in the upcoming versions. It will fix the issue by solving conflicts in the WFP stack. [More information](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/github-repos.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/github-repos.md new file mode 100644 index 00000000000..dfb164c44bc --- /dev/null +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/github-repos.md @@ -0,0 +1,238 @@ +--- +title: AdGuard’s GitHub repositories +sidebar_position: 9 +--- + +At AdGuard, our goal is to make the Internet safer, more comfortable, and more transparent. This commitment is reflected not only in our product features and strict privacy policies, but also in the fact that we keep our work as open as possible. That includes actively interacting with our community. + +This is why [all of our products have public repositories](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse) — online spaces where anybody can see what we are working on, report issues directly to AdGuard developers, and even contribute to our open-source projects. The repositories cover our ad-blocking apps, filters, browser extensions, DNS solutions, VPN tools, developer utilities, and more. There are different platforms that offer such functionality, but the most popular one by far is GitHub, and all AdGuard projects are stored there. + +This article lists the most important repositories by category, summarizes the purpose of each one, and gives a simple breakdown of what users can do there. + +:::tip + +Pro tip: Creating an issue on GitHub is the most effective way to bring the attention of AdGuard developers to a problem. Just make sure to check that a similar issue doesn’t already exist and describe the problem in a comprehensive but concise way. If it does exist, you can upvote it. + +::: + +## What is Github and its repositories + +Very simply put, you can think of GitHub as sort of Google Docs for code, where multiple people can work on the same project, track changes, and see who made which updates. It provides a central, cloud-based place to store your code so it’s accessible from anywhere. It also has teamwork tools for reviewing changes, fixing issues, and merging everyone’s work smoothly. + +GitHub is widely used for open-source projects, letting anyone view the code, suggest improvements, and contribute. + +A repository (often called “repo” for short) is the most basic element of GitHub. It’s a place where you can store your code, your files, and each file’s revision history. Repositories can have multiple collaborators and can be either public or private. + +## What can you do in AdGuard’s repositories + +You can find links to key repositories below in this article or visit the [general AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all) for a full list. In most repos, you can: + +- **View README file** on the main page: it gives you an introduction to the product and its repo + ![README file \*border](https://cdn.adtidy.org/content/blog/github-repos/see-readme.png) + +- **Check existing bug reports or feature requests**, comment and upvote + ![Check issues \*border](https://cdn.adtidy.org/content/blog/github-repos/check-issues.png) + +- **Create issues** to report bugs or request features + ![Create issues \*border](https://cdn.adtidy.org/content/blog/github-repos/create-issue.png) + +- **Check releases** for different versions and their changelogs (and install an older version if needed) + ![Check releases \*border](https://cdn.adtidy.org/content/blog/github-repos/check-releases.png) + +- **Install any older or beta version** if needed + ![Download builds \*border](https://cdn.adtidy.org/content/blog/github-repos/download-releases.png) + +:::note + +If you are new to GitHub, you’ll need to create a GitHub account in order to create new issues and comment on the existing ones. + +::: + +In open-source repos advanced users can also: + +- **Browse code** to understand product logic, what technologies are used and how they are implemented +- **Fork and contribute** via pull requests + +Whether you’re a casual user, technical expert, or a developer, AdGuard welcomes all community participation across its GitHub repos. + +## Legal documents + +### [LegalDocs](https://github.com/AdguardTeam/LegalDocs) + +As part of our commitment to transparency, we host all legal documents — such as End-User License Agreements, Privacy Policies, and Terms and Conditions — on GitHub. Our _LegalDocs_ repo lets anyone check the full history of changes to these documents. + +## AdGuard Ad Blocker products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdguardForAndroid](https://github.com/AdguardTeam/AdguardForAndroid) + +Repository of AdGuard for Android — an app that provides system-wide ad blocking. + +### [AdguardForiOS](https://github.com/AdguardTeam/AdguardForiOS) + +Repository of AdGuard for iOS — Safari content blocker with DNS and custom filters. Users can also check open-source code. + +### [AdguardForWindows](https://github.com/AdguardTeam/AdguardForWindows) + +Repository of AdGuard for Windows. Non-open-source; GitHub used as an open bug tracker. + +### [AdguardForMac](https://github.com/AdguardTeam/AdguardForMac) + +Repository of AdGuard for Mac — macOS standalone content blocker. Bug tracker only. + +### [AdguardBrowserExtension](https://github.com/AdguardTeam/AdguardBrowserExtension) + +Repository of AdGuard Browser Extension — extension that provides ad blocking with enhanced privacy for Chrome, Firefox, Opera, Edge. + +### [AdguardForSafari](https://github.com/AdguardTeam/AdGuardForSafari) + +Repository of AdGuard for Safari — Safari ad blocking extension for Mac. Users can also check open-sourced code. + +### [AdGuardCLI](https://github.com/AdguardTeam/AdGuardCLI) + +Repository of AdGuard for Linux — a command‑line interface for managing ad blocking. + +## AdGuard VPN products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdGuardVPNForiOS](https://github.com/AdguardTeam/AdGuardVPNForiOS) + +Repository of AdGuard VPN for iOS. Serves as an open bug tracker. + +### [AdGuardVPNForAndroid](https://github.com/AdguardTeam/AdGuardVPNForAndroid) + +Repository of AdGuard VPN for Android. Serves as an open bug tracker. + +### [AdGuardVPNForWindows](https://github.com/AdguardTeam/AdGuardVPNForWindows) + +Repository of AdGuard VPN for Windows. Serves as an open bug tracker. + +### [AdGuardVPNForMac](https://github.com/AdguardTeam/AdGuardVPNForMac) + +Repository of AdGuard VPN for Mac — app designed for macOS. + +### [AdGuardVPNExtension](https://github.com/AdguardTeam/AdGuardVPNExtension) + +Repository of AdGuard VPN Browser Extension. + +### [AdGuardVPNCLI](https://github.com/AdguardTeam/AdGuardVPNCLI) + +Repository of AdGuard VPN for Linux — a command‑line interface for managing VPN connection. The repo acts as a bug tracker. + +## DNS-based products + +### [AdGuardDNS](https://github.com/AdguardTeam/AdGuardDNS) + +Open-source repository that is also used for tracking bugs and issues related to AdGuard DNS service. Users can: + +- View and report DNS issues +- Suggest improvements + +### [AdGuardHome](https://github.com/AdguardTeam/AdGuardHome) + +Repository of AdGuard Home — free network-wide software for blocking ads and trackers via DNS. Users can: + +- Check and file bug reports or feature requests +- Review or contribute to code +- Download and install releases + +## Documentation and Knowledge bases + +Knowledge bases are aimed to help users better understand and use AdGuard. They describe each AdGuard product in detail: from feature overviews and problem-solving guides to advanced setting manuals and API documentations. In the repositories users can: + +- Suggest corrections or edits to knowledge base articles +- Propose new articles +- Test or run the local version + +### [KnowledgeBase](https://github.com/AdguardTeam/KnowledgeBase) + +Central documentation for AdGuard Ad Blocker and the technologies related to it. + +### [KnowledgeBaseDNS](https://github.com/AdguardTeam/KnowledgeBaseDNS) + +Detailed feature overview, troubleshooting guides and documentation for AdGuard DNS (both Public and Private), AdGuard Home, and everything related to them. + +### [KnowledgeBaseVPN](https://github.com/AdguardTeam/KnowledgeBaseVPN) + +Detailed feature overview and troubleshooting guides for AdGuard VPN. + +### [KnowledgeBaseMail](https://github.com/AdguardTeam/KnowledgeBaseMail) + +Detailed feature overview and troubleshooting guides of AdGuard Mail. + +## Core libraries + +### [CoreLibs](https://github.com/AdguardTeam/CoreLibs) + +AdGuard’s cross-platform core filtering engine. Used in Android, Windows, and Mac products. Users can: + +- Explore filtering logic and DNS handling +- Report bugs and suggest features via Issues + +### [DNSLibs](https://github.com/AdguardTeam/DNSLibs) + +A DNS library used by CoreLibs and AdGuardHome. Users can: + +- Review and contribute to low-level DNS implementation +- Suggest optimizations + +### [VPNLibs](https://github.com/AdguardTeam/VPNLibs) + +Shared codebase used in AdGuard VPN products across platforms for AdGuard VPN protocol implementation. Users can: + +- Contribute to VPN stack behavior +- Report or view performance issues and bugs + +## Core ad blocking and filtering technologies + +### [AdguardFilters](https://github.com/AdguardTeam/AdguardFilters) + +Contains AdGuard’s core filter lists. Users can: + +- View and download filter lists +- Create issues to report false positives or suggest new rules +- Monitor updates to filter logic + +### [AdGuardSDNSFilter](https://github.com/AdguardTeam/AdGuardSDNSFilter) + +Repository of AdGuard DNS filter — the main DNS-level blocking list used in AdGuard DNS and DNS filtering features. Users can: + +- Inspect the current rule set +- Propose changes or additions + +### [AGLint](https://github.com/AdguardTeam/AGLint) + +A linter for adblock filter list syntax. Users can: + +- Install AGLint to check their projects for rule issues +- Contribute to lint rules + +### [Scriptlets](https://github.com/AdguardTeam/Scriptlets) + +JavaScript helpers used in filtering rules. Users can: + +- Explore available scriptlets +- Submit pull requests for new scriptlets + +### [tsurlfilter](https://github.com/AdguardTeam/tsurlfilter) + +TypeScript content blocker library for browser extensions. Users can: + +- Explore how filtering logic is implemented +- Contribute fixes and features + +## There’s more + +Above, we listed 27 main public AdGuard repositories out of 96 total. If you want to go down the rabbit hole, you can [find the rest on the AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse). + +We’ll be waiting for your feedback there! Stay safe online and offline. diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/how-to-install.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/how-to-install.md index e7e6b5e31b6..42d55205011 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/how-to-install.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/how-to-install.md @@ -1,6 +1,6 @@ --- title: How to install AdGuard -sidebar_position: 9 +sidebar_position: 10 --- Depending on which AdGuard app or browser extension you want to install, follow one of these links to find the relevant article: diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md index 3953f47d26f..05642d350b0 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md @@ -43,6 +43,14 @@ Here you can choose which proxy AdGuard should use to download filter updates or ## Use SockFilter driver -Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. +Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. If this option is disabled, AdGuard will switch to the older WFP driver instead. -If this option is disabled, AdGuard will switch to the older WFP driver instead. +SockFilter was first introduced in v8.0 RC. It is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md index 251e49cf286..1ab588bb16c 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Because of this, TDI-based traffic visibility becomes increasingly unstable. In AdGuard already treats the TDI driver as deprecated, and its complete removal is planned as the product evolves. +## Permanent solution + +From v8.0 RC, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows-8/settings/app-settings/network-settings/). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Temporary solution Certain Windows registry changes can force the browser to stop using AppContainer, causing its processes to run in a non-sandboxed mode again. Network Service stops using the WSK stack and falls back to a network path that the TDI driver can see. AdGuard then regains the ability to filter browser traffic. @@ -123,7 +131,3 @@ You should see the following policies active: If available, click _Reload policies_. Done! - -## Permanent solution - -We’re planning to add support for the SockFilter driver in the upcoming versions. It will fix the issue by solving conflicts in the WFP stack. [More information](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index 4291a773b47..6640b2382bf 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -17,23 +17,35 @@ In this module you can select the checkbox _Use AdGuard as an HTTP proxy_ to use At last, there is a section with proxy settings. There you can specify which proxy server AdGuard should use to update filters, get new versions, and so on. -### SockFilter and other network drivers +### Enable traffic filtering -In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. +Traffic filtering is the core mechanism that allows AdGuard to inspect and control the network traffic generated by applications on your computer. When it is enabled, AdGuard intercepts outgoing and incoming connections and checks them against its filtering rules. If a request matches a blocking rule, AdGuard can block it, modify it, or allow it depending on the configuration. In AdGuard for Windows, this interception is implemented through network drivers. -**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. +If HTTPS filtering is enabled, AdGuard performs a controlled local TLS interception: it decrypts the traffic using its local certificate, applies filtering rules, and then re-encrypts the traffic before sending it to the browser. The driver simply provides the system-level access needed for AdGuard to intercept these connections. -The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +#### SockFilter **SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. -Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: +SockFilter was first implemented in version 7.22.4, and it is still considered unstable — you may encounter bugs. Once fully tested and implemented, SockFilter has the potential to offer several advantages over other drivers: -- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. - **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. -- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. -When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. +#### WFP + +**WFP** (Windows Filtering Platform) is a Microsoft networking framework built into Windows that allows software to filter and monitor network packets at different layers of the system networking stack. AdGuard uses WFP to safely hook into the network flow of applications and apply filtering rules before the traffic reaches the browser or the Internet. [More information](https://learn.microsoft.com/en-us/windows/win32/fwp/windows-filtering-platform-architecture-overview). + +While it is a powerful driver, it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) and lower Internet speed for some users. + +#### TDI + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. ### AdGuard VPN diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index c3e4b5dd852..1dd96d2e10a 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -44,12 +44,8 @@ Before you start manually writing your own rules read our detailed [syntax guide Many websites gather information about their visitors, such as their IP addresses, browser and operating system details, screen resolution, and the webpage from which the user came or was redirected. Some websites use cookies to mark and identify your browser, save your personal settings and preferences. This allows them to “recognize” you on your next visit. Tracking protection safeguards your personal information from these data- and statistics-gathering systems. -![Tracking protection levels \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection1.png) - You can adjust the _Tracking Protection_ settings as needed. For example, you can prevent websites from receiving the search request that you used to find them on the Internet, automatically delete third- and first-party cookies, and disable location sharing in your browser, to prevent tracking of your whereabouts. -![Tracking protection custom features \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection2.png) - To learn everything about _Tracking protection_ and its many options, [read this article](/general/stealth-mode). ### Browsing security diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md index 708d37bed3a..fffa43f1b28 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Because of this, TDI-based traffic visibility becomes increasingly unstable. In AdGuard already treats the TDI driver as deprecated, and its complete removal is planned as the product evolves. +## Permanent solution + +From v7.22.4, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows/features/network/#sockfilter-and-other-network-drivers). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Temporary solution Certain Windows registry changes can force the browser to stop using AppContainer, causing its processes to run in a non-sandboxed mode again. Network Service stops using the WSK stack and falls back to a network path that the TDI driver can see. AdGuard then regains the ability to filter browser traffic. @@ -136,7 +144,3 @@ You should see the following policies active: If available, click _Reload policies_. Done! - -## Permanent solution - -We’re planning to add support for the SockFilter driver in the upcoming versions. It will fix the issue by solving conflicts in the WFP stack. [More information](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/general/github-repos.md b/i18n/pt/docusaurus-plugin-content-docs/current/general/github-repos.md new file mode 100644 index 00000000000..dfb164c44bc --- /dev/null +++ b/i18n/pt/docusaurus-plugin-content-docs/current/general/github-repos.md @@ -0,0 +1,238 @@ +--- +title: AdGuard’s GitHub repositories +sidebar_position: 9 +--- + +At AdGuard, our goal is to make the Internet safer, more comfortable, and more transparent. This commitment is reflected not only in our product features and strict privacy policies, but also in the fact that we keep our work as open as possible. That includes actively interacting with our community. + +This is why [all of our products have public repositories](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse) — online spaces where anybody can see what we are working on, report issues directly to AdGuard developers, and even contribute to our open-source projects. The repositories cover our ad-blocking apps, filters, browser extensions, DNS solutions, VPN tools, developer utilities, and more. There are different platforms that offer such functionality, but the most popular one by far is GitHub, and all AdGuard projects are stored there. + +This article lists the most important repositories by category, summarizes the purpose of each one, and gives a simple breakdown of what users can do there. + +:::tip + +Pro tip: Creating an issue on GitHub is the most effective way to bring the attention of AdGuard developers to a problem. Just make sure to check that a similar issue doesn’t already exist and describe the problem in a comprehensive but concise way. If it does exist, you can upvote it. + +::: + +## What is Github and its repositories + +Very simply put, you can think of GitHub as sort of Google Docs for code, where multiple people can work on the same project, track changes, and see who made which updates. It provides a central, cloud-based place to store your code so it’s accessible from anywhere. It also has teamwork tools for reviewing changes, fixing issues, and merging everyone’s work smoothly. + +GitHub is widely used for open-source projects, letting anyone view the code, suggest improvements, and contribute. + +A repository (often called “repo” for short) is the most basic element of GitHub. It’s a place where you can store your code, your files, and each file’s revision history. Repositories can have multiple collaborators and can be either public or private. + +## What can you do in AdGuard’s repositories + +You can find links to key repositories below in this article or visit the [general AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all) for a full list. In most repos, you can: + +- **View README file** on the main page: it gives you an introduction to the product and its repo + ![README file \*border](https://cdn.adtidy.org/content/blog/github-repos/see-readme.png) + +- **Check existing bug reports or feature requests**, comment and upvote + ![Check issues \*border](https://cdn.adtidy.org/content/blog/github-repos/check-issues.png) + +- **Create issues** to report bugs or request features + ![Create issues \*border](https://cdn.adtidy.org/content/blog/github-repos/create-issue.png) + +- **Check releases** for different versions and their changelogs (and install an older version if needed) + ![Check releases \*border](https://cdn.adtidy.org/content/blog/github-repos/check-releases.png) + +- **Install any older or beta version** if needed + ![Download builds \*border](https://cdn.adtidy.org/content/blog/github-repos/download-releases.png) + +:::note + +If you are new to GitHub, you’ll need to create a GitHub account in order to create new issues and comment on the existing ones. + +::: + +In open-source repos advanced users can also: + +- **Browse code** to understand product logic, what technologies are used and how they are implemented +- **Fork and contribute** via pull requests + +Whether you’re a casual user, technical expert, or a developer, AdGuard welcomes all community participation across its GitHub repos. + +## Legal documents + +### [LegalDocs](https://github.com/AdguardTeam/LegalDocs) + +As part of our commitment to transparency, we host all legal documents — such as End-User License Agreements, Privacy Policies, and Terms and Conditions — on GitHub. Our _LegalDocs_ repo lets anyone check the full history of changes to these documents. + +## AdGuard Ad Blocker products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdguardForAndroid](https://github.com/AdguardTeam/AdguardForAndroid) + +Repository of AdGuard for Android — an app that provides system-wide ad blocking. + +### [AdguardForiOS](https://github.com/AdguardTeam/AdguardForiOS) + +Repository of AdGuard for iOS — Safari content blocker with DNS and custom filters. Users can also check open-source code. + +### [AdguardForWindows](https://github.com/AdguardTeam/AdguardForWindows) + +Repository of AdGuard for Windows. Non-open-source; GitHub used as an open bug tracker. + +### [AdguardForMac](https://github.com/AdguardTeam/AdguardForMac) + +Repository of AdGuard for Mac — macOS standalone content blocker. Bug tracker only. + +### [AdguardBrowserExtension](https://github.com/AdguardTeam/AdguardBrowserExtension) + +Repository of AdGuard Browser Extension — extension that provides ad blocking with enhanced privacy for Chrome, Firefox, Opera, Edge. + +### [AdguardForSafari](https://github.com/AdguardTeam/AdGuardForSafari) + +Repository of AdGuard for Safari — Safari ad blocking extension for Mac. Users can also check open-sourced code. + +### [AdGuardCLI](https://github.com/AdguardTeam/AdGuardCLI) + +Repository of AdGuard for Linux — a command‑line interface for managing ad blocking. + +## AdGuard VPN products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdGuardVPNForiOS](https://github.com/AdguardTeam/AdGuardVPNForiOS) + +Repository of AdGuard VPN for iOS. Serves as an open bug tracker. + +### [AdGuardVPNForAndroid](https://github.com/AdguardTeam/AdGuardVPNForAndroid) + +Repository of AdGuard VPN for Android. Serves as an open bug tracker. + +### [AdGuardVPNForWindows](https://github.com/AdguardTeam/AdGuardVPNForWindows) + +Repository of AdGuard VPN for Windows. Serves as an open bug tracker. + +### [AdGuardVPNForMac](https://github.com/AdguardTeam/AdGuardVPNForMac) + +Repository of AdGuard VPN for Mac — app designed for macOS. + +### [AdGuardVPNExtension](https://github.com/AdguardTeam/AdGuardVPNExtension) + +Repository of AdGuard VPN Browser Extension. + +### [AdGuardVPNCLI](https://github.com/AdguardTeam/AdGuardVPNCLI) + +Repository of AdGuard VPN for Linux — a command‑line interface for managing VPN connection. The repo acts as a bug tracker. + +## DNS-based products + +### [AdGuardDNS](https://github.com/AdguardTeam/AdGuardDNS) + +Open-source repository that is also used for tracking bugs and issues related to AdGuard DNS service. Users can: + +- View and report DNS issues +- Suggest improvements + +### [AdGuardHome](https://github.com/AdguardTeam/AdGuardHome) + +Repository of AdGuard Home — free network-wide software for blocking ads and trackers via DNS. Users can: + +- Check and file bug reports or feature requests +- Review or contribute to code +- Download and install releases + +## Documentation and Knowledge bases + +Knowledge bases are aimed to help users better understand and use AdGuard. They describe each AdGuard product in detail: from feature overviews and problem-solving guides to advanced setting manuals and API documentations. In the repositories users can: + +- Suggest corrections or edits to knowledge base articles +- Propose new articles +- Test or run the local version + +### [KnowledgeBase](https://github.com/AdguardTeam/KnowledgeBase) + +Central documentation for AdGuard Ad Blocker and the technologies related to it. + +### [KnowledgeBaseDNS](https://github.com/AdguardTeam/KnowledgeBaseDNS) + +Detailed feature overview, troubleshooting guides and documentation for AdGuard DNS (both Public and Private), AdGuard Home, and everything related to them. + +### [KnowledgeBaseVPN](https://github.com/AdguardTeam/KnowledgeBaseVPN) + +Detailed feature overview and troubleshooting guides for AdGuard VPN. + +### [KnowledgeBaseMail](https://github.com/AdguardTeam/KnowledgeBaseMail) + +Detailed feature overview and troubleshooting guides of AdGuard Mail. + +## Core libraries + +### [CoreLibs](https://github.com/AdguardTeam/CoreLibs) + +AdGuard’s cross-platform core filtering engine. Used in Android, Windows, and Mac products. Users can: + +- Explore filtering logic and DNS handling +- Report bugs and suggest features via Issues + +### [DNSLibs](https://github.com/AdguardTeam/DNSLibs) + +A DNS library used by CoreLibs and AdGuardHome. Users can: + +- Review and contribute to low-level DNS implementation +- Suggest optimizations + +### [VPNLibs](https://github.com/AdguardTeam/VPNLibs) + +Shared codebase used in AdGuard VPN products across platforms for AdGuard VPN protocol implementation. Users can: + +- Contribute to VPN stack behavior +- Report or view performance issues and bugs + +## Core ad blocking and filtering technologies + +### [AdguardFilters](https://github.com/AdguardTeam/AdguardFilters) + +Contains AdGuard’s core filter lists. Users can: + +- View and download filter lists +- Create issues to report false positives or suggest new rules +- Monitor updates to filter logic + +### [AdGuardSDNSFilter](https://github.com/AdguardTeam/AdGuardSDNSFilter) + +Repository of AdGuard DNS filter — the main DNS-level blocking list used in AdGuard DNS and DNS filtering features. Users can: + +- Inspect the current rule set +- Propose changes or additions + +### [AGLint](https://github.com/AdguardTeam/AGLint) + +A linter for adblock filter list syntax. Users can: + +- Install AGLint to check their projects for rule issues +- Contribute to lint rules + +### [Scriptlets](https://github.com/AdguardTeam/Scriptlets) + +JavaScript helpers used in filtering rules. Users can: + +- Explore available scriptlets +- Submit pull requests for new scriptlets + +### [tsurlfilter](https://github.com/AdguardTeam/tsurlfilter) + +TypeScript content blocker library for browser extensions. Users can: + +- Explore how filtering logic is implemented +- Contribute fixes and features + +## There’s more + +Above, we listed 27 main public AdGuard repositories out of 96 total. If you want to go down the rabbit hole, you can [find the rest on the AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse). + +We’ll be waiting for your feedback there! Stay safe online and offline. diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/general/how-to-install.md b/i18n/pt/docusaurus-plugin-content-docs/current/general/how-to-install.md index 106a29529a8..4ba78d7a094 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/general/how-to-install.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/general/how-to-install.md @@ -1,6 +1,6 @@ --- title: How to install AdGuard -sidebar_position: 9 +sidebar_position: 10 --- Depending on which AdGuard app or browser extension you want to install, follow one of these links to find the relevant article: diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md index 3953f47d26f..05642d350b0 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md @@ -43,6 +43,14 @@ Here you can choose which proxy AdGuard should use to download filter updates or ## Use SockFilter driver -Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. +Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. If this option is disabled, AdGuard will switch to the older WFP driver instead. -If this option is disabled, AdGuard will switch to the older WFP driver instead. +SockFilter was first introduced in v8.0 RC. It is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md index 3b49b357f65..81b84e96389 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Because of this, TDI-based traffic visibility becomes increasingly unstable. In AdGuard already treats the TDI driver as deprecated, and its complete removal is planned as the product evolves. +## Permanent solution + +From v8.0 RC, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows-8/settings/app-settings/network-settings/). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Temporary solution Certain Windows registry changes can force the browser to stop using AppContainer, causing its processes to run in a non-sandboxed mode again. Network Service stops using the WSK stack and falls back to a network path that the TDI driver can see. AdGuard then regains the ability to filter browser traffic. @@ -123,7 +131,3 @@ You should see the following policies active: If available, click _Reload policies_. Terminat! - -## Permanent solution - -We’re planning to add support for the SockFilter driver in the upcoming versions. It will fix the issue by solving conflicts in the WFP stack. [More information](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index 9f66682d0f4..e430f99fa46 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -17,23 +17,35 @@ Modulul _Rețea_ este dedicat filtrării rețelei, și aici veți găsi opțiuni În cele din urmă, există o secțiune dedicată setărilor proxy. Acolo puteți specifica ce server proxy ar trebui să folosească AdGuard pentru a actualiza filtrele, a obține versiunile noi și așa mai departe. -### SockFilter and other network drivers +### Enable traffic filtering -In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. +Traffic filtering is the core mechanism that allows AdGuard to inspect and control the network traffic generated by applications on your computer. When it is enabled, AdGuard intercepts outgoing and incoming connections and checks them against its filtering rules. If a request matches a blocking rule, AdGuard can block it, modify it, or allow it depending on the configuration. In AdGuard for Windows, this interception is implemented through network drivers. -**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. +If HTTPS filtering is enabled, AdGuard performs a controlled local TLS interception: it decrypts the traffic using its local certificate, applies filtering rules, and then re-encrypts the traffic before sending it to the browser. The driver simply provides the system-level access needed for AdGuard to intercept these connections. -The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +#### SockFilter **SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. -Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: +SockFilter was first implemented in version 7.22.4, and it is still considered unstable — you may encounter bugs. Once fully tested and implemented, SockFilter has the potential to offer several advantages over other drivers: -- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. - **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. -- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. -When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. +#### WFP + +**WFP** (Windows Filtering Platform) is a Microsoft networking framework built into Windows that allows software to filter and monitor network packets at different layers of the system networking stack. AdGuard uses WFP to safely hook into the network flow of applications and apply filtering rules before the traffic reaches the browser or the Internet. [More information](https://learn.microsoft.com/en-us/windows/win32/fwp/windows-filtering-platform-architecture-overview). + +While it is a powerful driver, it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) and lower Internet speed for some users. + +#### TDI + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. ### AdGuard VPN diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index 4df8fbab309..5b26bca4070 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -44,12 +44,8 @@ In the Ad blocking module you can: Many websites gather information about their visitors, such as their IP addresses, browser and operating system details, screen resolution, and the webpage from which the user came or was redirected. Some websites use cookies to mark and identify your browser, save your personal settings and preferences. This allows them to “recognize” you on your next visit. Tracking protection safeguards your personal information from these data- and statistics-gathering systems. -![Tracking protection levels \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection1.png) - You can adjust the _Tracking Protection_ settings as needed. For example, you can prevent websites from receiving the search request that you used to find them on the Internet, automatically delete third- and first-party cookies, and disable location sharing in your browser, to prevent tracking of your whereabouts. -![Tracking protection custom features \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection2.png) - To learn everything about _Tracking protection_ and its many options, [read this article](/general/stealth-mode). ### Securitate la navigare diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md index bda8a426ab4..09f8386a6b7 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Because of this, TDI-based traffic visibility becomes increasingly unstable. In AdGuard already treats the TDI driver as deprecated, and its complete removal is planned as the product evolves. +## Permanent solution + +From v7.22.4, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows/features/network/#sockfilter-and-other-network-drivers). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Temporary solution Certain Windows registry changes can force the browser to stop using AppContainer, causing its processes to run in a non-sandboxed mode again. Network Service stops using the WSK stack and falls back to a network path that the TDI driver can see. AdGuard then regains the ability to filter browser traffic. @@ -136,7 +144,3 @@ You should see the following policies active: If available, click _Reload policies_. Terminat! - -## Permanent solution - -We’re planning to add support for the SockFilter driver in the upcoming versions. It will fix the issue by solving conflicts in the WFP stack. [More information](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/general/github-repos.md b/i18n/ro/docusaurus-plugin-content-docs/current/general/github-repos.md new file mode 100644 index 00000000000..dfb164c44bc --- /dev/null +++ b/i18n/ro/docusaurus-plugin-content-docs/current/general/github-repos.md @@ -0,0 +1,238 @@ +--- +title: AdGuard’s GitHub repositories +sidebar_position: 9 +--- + +At AdGuard, our goal is to make the Internet safer, more comfortable, and more transparent. This commitment is reflected not only in our product features and strict privacy policies, but also in the fact that we keep our work as open as possible. That includes actively interacting with our community. + +This is why [all of our products have public repositories](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse) — online spaces where anybody can see what we are working on, report issues directly to AdGuard developers, and even contribute to our open-source projects. The repositories cover our ad-blocking apps, filters, browser extensions, DNS solutions, VPN tools, developer utilities, and more. There are different platforms that offer such functionality, but the most popular one by far is GitHub, and all AdGuard projects are stored there. + +This article lists the most important repositories by category, summarizes the purpose of each one, and gives a simple breakdown of what users can do there. + +:::tip + +Pro tip: Creating an issue on GitHub is the most effective way to bring the attention of AdGuard developers to a problem. Just make sure to check that a similar issue doesn’t already exist and describe the problem in a comprehensive but concise way. If it does exist, you can upvote it. + +::: + +## What is Github and its repositories + +Very simply put, you can think of GitHub as sort of Google Docs for code, where multiple people can work on the same project, track changes, and see who made which updates. It provides a central, cloud-based place to store your code so it’s accessible from anywhere. It also has teamwork tools for reviewing changes, fixing issues, and merging everyone’s work smoothly. + +GitHub is widely used for open-source projects, letting anyone view the code, suggest improvements, and contribute. + +A repository (often called “repo” for short) is the most basic element of GitHub. It’s a place where you can store your code, your files, and each file’s revision history. Repositories can have multiple collaborators and can be either public or private. + +## What can you do in AdGuard’s repositories + +You can find links to key repositories below in this article or visit the [general AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all) for a full list. In most repos, you can: + +- **View README file** on the main page: it gives you an introduction to the product and its repo + ![README file \*border](https://cdn.adtidy.org/content/blog/github-repos/see-readme.png) + +- **Check existing bug reports or feature requests**, comment and upvote + ![Check issues \*border](https://cdn.adtidy.org/content/blog/github-repos/check-issues.png) + +- **Create issues** to report bugs or request features + ![Create issues \*border](https://cdn.adtidy.org/content/blog/github-repos/create-issue.png) + +- **Check releases** for different versions and their changelogs (and install an older version if needed) + ![Check releases \*border](https://cdn.adtidy.org/content/blog/github-repos/check-releases.png) + +- **Install any older or beta version** if needed + ![Download builds \*border](https://cdn.adtidy.org/content/blog/github-repos/download-releases.png) + +:::note + +If you are new to GitHub, you’ll need to create a GitHub account in order to create new issues and comment on the existing ones. + +::: + +In open-source repos advanced users can also: + +- **Browse code** to understand product logic, what technologies are used and how they are implemented +- **Fork and contribute** via pull requests + +Whether you’re a casual user, technical expert, or a developer, AdGuard welcomes all community participation across its GitHub repos. + +## Legal documents + +### [LegalDocs](https://github.com/AdguardTeam/LegalDocs) + +As part of our commitment to transparency, we host all legal documents — such as End-User License Agreements, Privacy Policies, and Terms and Conditions — on GitHub. Our _LegalDocs_ repo lets anyone check the full history of changes to these documents. + +## AdGuard Ad Blocker products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdguardForAndroid](https://github.com/AdguardTeam/AdguardForAndroid) + +Repository of AdGuard for Android — an app that provides system-wide ad blocking. + +### [AdguardForiOS](https://github.com/AdguardTeam/AdguardForiOS) + +Repository of AdGuard for iOS — Safari content blocker with DNS and custom filters. Users can also check open-source code. + +### [AdguardForWindows](https://github.com/AdguardTeam/AdguardForWindows) + +Repository of AdGuard for Windows. Non-open-source; GitHub used as an open bug tracker. + +### [AdguardForMac](https://github.com/AdguardTeam/AdguardForMac) + +Repository of AdGuard for Mac — macOS standalone content blocker. Bug tracker only. + +### [AdguardBrowserExtension](https://github.com/AdguardTeam/AdguardBrowserExtension) + +Repository of AdGuard Browser Extension — extension that provides ad blocking with enhanced privacy for Chrome, Firefox, Opera, Edge. + +### [AdguardForSafari](https://github.com/AdguardTeam/AdGuardForSafari) + +Repository of AdGuard for Safari — Safari ad blocking extension for Mac. Users can also check open-sourced code. + +### [AdGuardCLI](https://github.com/AdguardTeam/AdGuardCLI) + +Repository of AdGuard for Linux — a command‑line interface for managing ad blocking. + +## AdGuard VPN products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdGuardVPNForiOS](https://github.com/AdguardTeam/AdGuardVPNForiOS) + +Repository of AdGuard VPN for iOS. Serves as an open bug tracker. + +### [AdGuardVPNForAndroid](https://github.com/AdguardTeam/AdGuardVPNForAndroid) + +Repository of AdGuard VPN for Android. Serves as an open bug tracker. + +### [AdGuardVPNForWindows](https://github.com/AdguardTeam/AdGuardVPNForWindows) + +Repository of AdGuard VPN for Windows. Serves as an open bug tracker. + +### [AdGuardVPNForMac](https://github.com/AdguardTeam/AdGuardVPNForMac) + +Repository of AdGuard VPN for Mac — app designed for macOS. + +### [AdGuardVPNExtension](https://github.com/AdguardTeam/AdGuardVPNExtension) + +Repository of AdGuard VPN Browser Extension. + +### [AdGuardVPNCLI](https://github.com/AdguardTeam/AdGuardVPNCLI) + +Repository of AdGuard VPN for Linux — a command‑line interface for managing VPN connection. The repo acts as a bug tracker. + +## DNS-based products + +### [AdGuardDNS](https://github.com/AdguardTeam/AdGuardDNS) + +Open-source repository that is also used for tracking bugs and issues related to AdGuard DNS service. Users can: + +- View and report DNS issues +- Suggest improvements + +### [AdGuardHome](https://github.com/AdguardTeam/AdGuardHome) + +Repository of AdGuard Home — free network-wide software for blocking ads and trackers via DNS. Users can: + +- Check and file bug reports or feature requests +- Review or contribute to code +- Download and install releases + +## Documentation and Knowledge bases + +Knowledge bases are aimed to help users better understand and use AdGuard. They describe each AdGuard product in detail: from feature overviews and problem-solving guides to advanced setting manuals and API documentations. In the repositories users can: + +- Suggest corrections or edits to knowledge base articles +- Propose new articles +- Test or run the local version + +### [KnowledgeBase](https://github.com/AdguardTeam/KnowledgeBase) + +Central documentation for AdGuard Ad Blocker and the technologies related to it. + +### [KnowledgeBaseDNS](https://github.com/AdguardTeam/KnowledgeBaseDNS) + +Detailed feature overview, troubleshooting guides and documentation for AdGuard DNS (both Public and Private), AdGuard Home, and everything related to them. + +### [KnowledgeBaseVPN](https://github.com/AdguardTeam/KnowledgeBaseVPN) + +Detailed feature overview and troubleshooting guides for AdGuard VPN. + +### [KnowledgeBaseMail](https://github.com/AdguardTeam/KnowledgeBaseMail) + +Detailed feature overview and troubleshooting guides of AdGuard Mail. + +## Core libraries + +### [CoreLibs](https://github.com/AdguardTeam/CoreLibs) + +AdGuard’s cross-platform core filtering engine. Used in Android, Windows, and Mac products. Users can: + +- Explore filtering logic and DNS handling +- Report bugs and suggest features via Issues + +### [DNSLibs](https://github.com/AdguardTeam/DNSLibs) + +A DNS library used by CoreLibs and AdGuardHome. Users can: + +- Review and contribute to low-level DNS implementation +- Suggest optimizations + +### [VPNLibs](https://github.com/AdguardTeam/VPNLibs) + +Shared codebase used in AdGuard VPN products across platforms for AdGuard VPN protocol implementation. Users can: + +- Contribute to VPN stack behavior +- Report or view performance issues and bugs + +## Core ad blocking and filtering technologies + +### [AdguardFilters](https://github.com/AdguardTeam/AdguardFilters) + +Contains AdGuard’s core filter lists. Users can: + +- View and download filter lists +- Create issues to report false positives or suggest new rules +- Monitor updates to filter logic + +### [AdGuardSDNSFilter](https://github.com/AdguardTeam/AdGuardSDNSFilter) + +Repository of AdGuard DNS filter — the main DNS-level blocking list used in AdGuard DNS and DNS filtering features. Users can: + +- Inspect the current rule set +- Propose changes or additions + +### [AGLint](https://github.com/AdguardTeam/AGLint) + +A linter for adblock filter list syntax. Users can: + +- Install AGLint to check their projects for rule issues +- Contribute to lint rules + +### [Scriptlets](https://github.com/AdguardTeam/Scriptlets) + +JavaScript helpers used in filtering rules. Users can: + +- Explore available scriptlets +- Submit pull requests for new scriptlets + +### [tsurlfilter](https://github.com/AdguardTeam/tsurlfilter) + +TypeScript content blocker library for browser extensions. Users can: + +- Explore how filtering logic is implemented +- Contribute fixes and features + +## There’s more + +Above, we listed 27 main public AdGuard repositories out of 96 total. If you want to go down the rabbit hole, you can [find the rest on the AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse). + +We’ll be waiting for your feedback there! Stay safe online and offline. diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/general/how-to-install.md b/i18n/ro/docusaurus-plugin-content-docs/current/general/how-to-install.md index 7fa5a598e03..098c024bd64 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/general/how-to-install.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/general/how-to-install.md @@ -1,6 +1,6 @@ --- title: How to install AdGuard -sidebar_position: 9 +sidebar_position: 10 --- În funcție de care aplicație AdGuard sau extensie de browser doriți să instalați, urmați unul dintre aceste linkuri pentru a găsi articolul relevant: diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/adguard-browser-extension.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/adguard-browser-extension.md index 2d7ef95e4ab..b53f9158702 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/adguard-browser-extension.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/adguard-browser-extension.md @@ -11,7 +11,7 @@ sidebar_position: 1 - [Функции](/adguard-browser-extension/features) - Main features and settings available in AdGuard Browser Extension + Основные функции и настройки, доступные в Браузерном расширении AdGuard - [Доступность](/adguard-browser-extension/availability) @@ -23,7 +23,7 @@ sidebar_position: 1 - [Совместимость с автономным приложением](/adguard-browser-extension/compatibility) - Compatibility of AdGuard Browser Extension with the AdGuard desktop apps + Совместимость Браузерного расширения AdGuard с десктопными приложениями AdGuard - [Браузерное расширение AdGuard для Chrome MV3](/adguard-browser-extension/mv3-version/) diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/features.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/features.md index bedc1116f04..91e7a79daa9 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/features.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/features.md @@ -9,18 +9,18 @@ sidebar_position: 1 ::: -- [Main menu](/adguard-browser-extension/features/main-menu.md) +- [Главное меню](/adguard-browser-extension/features/main-menu.md) - The main popup from which you can access settings, filtering log and statistics, and report problems + Основное всплывающее окно, из которого вы можете получить доступ к настройкам, журналу фильтрации и статистике, а также сообщить о проблемах -- [Filters](/adguard-browser-extension/features/filters.md) +- [Фильтры](/adguard-browser-extension/features/filters.md) Фильтры и пользовательские правила для настройки блокировки рекламы -- [Tracking protection (Stealth Mode)](/adguard-browser-extension/features/stealth-mode.md) +- [Защита от трекинга](/adguard-browser-extension/features/stealth-mode.md) - Settings to block cookies, UTM tags, and online analytics that collect user information + Настройки блокировки файлов куки, UTM-меток и онлайн-аналитики, собирающей информацию о пользователях -- [Other features and options](/adguard-browser-extension/features/other-features.md) +- [Другие функции и опции](/adguard-browser-extension/features/other-features.md) - General and additional settings, links to privacy documents and GitHub repository + Основные и дополнительные настройки, ссылки на юридические документы и репозиторий на GitHub diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/stealth-mode.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/stealth-mode.md index e59c067b28f..5ccc72178da 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/stealth-mode.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/stealth-mode.md @@ -1,5 +1,5 @@ --- -title: Tracking protection (formerly Stealth Mode) +title: Защита от трекинга (ранее Антитрекинг) sidebar_position: 3 --- @@ -9,20 +9,20 @@ sidebar_position: 3 ::: -The purpose of _Tracking protection_ is to safeguard your sensitive personal data from online trackers and fraudsters. There are slight differences in the tracking protection features between Chromium-based browsers, which support MV3, and non-Chromium browsers, which support MV2. +Цель _Защиты от трекинга_ — защитить ваши конфиденциальные личные данные от онлайн-трекеров и мошенников. Существуют небольшие различия в функциях защиты от трекинга между браузерами на базе Chromium, которые поддерживают MV3, и не-Chromium браузерами, которые поддерживают MV2. -![Tracking protection in Chromium-based browsers \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_mv3_trackingProtection.png) +![Защита от трекинга в браузерах на основе Chromium \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_mv3_trackingProtection.png) -_Tracking protection_ in Chromium-based browsers +_Защита от трекинга_ в браузерах на базе Chromium -![Tracking protection in non-Chromium browsers \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_mv2_trackingProtection.png) +![Защита от трекинга в браузерах, не основанных на Chromium \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_mv2_trackingProtection.png) -_Tracking protection_ in non-Chromium browsers +_Защита от трекинга_ в не-Chromium браузерах -_Tracking protection_ features prevent websites from seeing the search query you used to find them on the Internet, automatically delete third-party and website cookies, and more. A [separate article](/general/stealth-mode) is devoted to all these features. +Функции _Защиты от трекинга_ не позволяют сайтам видеть поисковые запросы, с помощью которых вы нашли их в интернете, автоматически удаляют сторонние куки и куки сайта. Всем этим функциям посвящена [отдельная статья](/general/stealth-mode). :::note -Browser extensions are limited to a specific browser and are subject to its technical restrictions. Therefore, they cannot offer all the tracking protection features available in full-fledged ad-blocking apps. +Браузерные расширения ограничены конкретным браузером и подвержены его техническим ограничениям. Поэтому они не могут предложить все функции защиты от трекинга, доступные в комплексных приложениях для блокировки рекламы. ::: diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md index d1e6bdd8101..9a9a9f17871 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md @@ -1,15 +1,15 @@ --- -title: Ad blocking issues on search websites in Opera +title: Проблемы с блокировкой рекламы на поисковых сайтах в браузере Opera sidebar_position: 3 --- -If AdGuard Browser Extension fails to block ads on search websites in Opera, either automatically or manually, it means that the extension does not have permission to access search page results. +Если Браузерное расширение AdGuard не блокирует рекламу на поисковых сайтах в Opera автоматически или при ручной настройке, значит у него нет разрешения на доступ к результатам поиска. -To grant the required permission: +Чтобы предоставить необходимое разрешение: -![Allow access to search page results](https://cdn.adtidy.org/content/kb/ad_blocker/browser_extension/allow-access.png) +![Разрешить доступ к результатам поиска](https://cdn.adtidy.org/content/kb/ad_blocker/browser_extension/allow-access.png) -1. Click the cube icon next to the address bar → _Manage extensions..._. -2. Find AdGuard AdBlocker in the list of installed extensions and tick the box next to _Allow access to search page results_. +1. Кликните по иконке куба рядом с адресной строкой → _Управление расширениями..._. +2. Найдите AdGuard Антибаннер в списке установленных расширений и поставьте галочку напротив _Разрешить доступ к результатам на странице поиска_. -Once this is done, ads on search websites will be blocked as expected. +После этого реклама на сайтах поисковых систем будет блокироваться корректно. diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/features/features.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/features/features.md index 7c4181abcbd..099fc25c12b 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/features/features.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/features/features.md @@ -11,7 +11,7 @@ sidebar_position: 1 - [Защита Safari](/adguard-for-ios/features/safari-protection.md) - Available features and settings in the _Safari protection_ tab: _Filters_, _User rules_, and _Allowlist_ + Доступные функции и настройки во вкладке _Защита Safari_: _Фильтры_, _Пользовательские правила_ и _Белый список_ - [DNS-защита](/adguard-for-ios/features/dns-protection/) @@ -35,7 +35,7 @@ sidebar_position: 1 - [Другие функции](/adguard-for-ios/features/other-features.md) - General settings: theme, settings and statistics reset, auto-update, inverting the allowlist, and advanced mode. + Основные настройки: тема, сброс настроек и статистики, автообновление, инвертирование белого списка и расширенный режим. - [Совместимость с AdGuard VPN](/adguard-for-ios/features/compatibility-with-adguard-vpn.md) diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/features/features.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/features/features.md index ff8b97b7431..8c9d9cb14fa 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/features/features.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/features/features.md @@ -27,7 +27,7 @@ sidebar_position: 1 - [Защита от трекинга](/adguard-for-mac/features/stealth.md) - Settings to block cookies, UTM tags, and online analytics that collect user information + Настройки блокировки файлов куки, UTM-меток и онлайн-аналитики, собирающей информацию о пользователях - [Безопасность](/adguard-for-mac/features/security.md) @@ -35,7 +35,7 @@ sidebar_position: 1 - [Браузерный помощник](/adguard-for-mac/features/browser-assistant.md) - An extension that complements the desktop app and allows you to manage filtering from your browser + Расширение, которое дополняет десктопное приложение и позволяет управлять фильтрацией из браузера - [Расширения](/adguard-for-mac/features/extensions.md) diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md index d02bd4f602d..7558a57f4ca 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md @@ -43,6 +43,14 @@ sidebar_position: 3 ## Использовать драйвер SockFilter -Включите эту опцию, чтобы использовать драйвер SockFilter, который помогает блокировать рекламу и трекеры в приложениях на Windows 8 и более поздних версиях. +Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. If this option is disabled, AdGuard will switch to the older WFP driver instead. -Если эта опция отключена, AdGuard переключится на более старый WFP-драйвер. +SockFilter was first introduced in v8.0 RC. It is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md index 3fdbc75bd72..1b6e2fcfa4a 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ TDI-драйвер — это устаревшая технология Windows, AdGuard уже считает TDI-драйвер устаревшим и планирует его полное удаление. +## Постоянное решение + +From v8.0 RC, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows-8/settings/app-settings/network-settings/). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Временное решение Определённые изменения в реестре Windows могут заставить браузер перестать использовать AppContainer, в результате чего его процессы снова будут работать вне песочницы. Network Service прекращает использование стека WSK и переключается на сетевой путь, который виден TDI-драйверу. После этого AdGuard восстанавливает способность фильтровать трафик браузера. @@ -123,7 +131,3 @@ AdGuard уже считает TDI-драйвер устаревшим и пла Если такая опция есть, нажмите _Reload policies_. Готово! - -## Постоянное решение - -В будущих версиях мы планируем добавить поддержку драйвера SockFilter. Это решит проблему, устранив конфликты в стеке WFP. [Больше информации](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/adguard-for-windows.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/adguard-for-windows.md index ad85fb49119..852c4061b6a 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/adguard-for-windows.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/adguard-for-windows.md @@ -11,7 +11,7 @@ sidebar_position: 1 - [Функции](/adguard-for-windows/features/features.md) - Main features and settings available in AdGuard for Windows + Основные функции и настройки, доступные в AdGuard для Windows - [Установка](/adguard-for-windows/installation.md) @@ -19,7 +19,7 @@ sidebar_position: 1 - [Браузерный помощник](/adguard-for-windows/browser-assistant.md) - An extension that complements the desktop app and allows you to manage filtering from your browser + Расширение, которое дополняет десктопное приложение и позволяет управлять фильтрацией из браузера - [Решение проблем](/adguard-for-windows/solving-problems/solving-problems.md) diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/features/features.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/features/features.md index 9a7a1feb554..db7ebd9be31 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/features/features.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/features/features.md @@ -11,7 +11,7 @@ sidebar_position: 1 - [Главный экран](/adguard-for-windows/features/home-screen/) - On the main screen you’ll find _Settings_, _Support_, _License_, and _About_, as well as statistics on blocked ads and trackers + На главном экране вы найдёте разделы _Настройки_, _Поддержка_, _Лицензия_ и _О программе_, а также статистику по заблокированной рекламе и трекерам - [Настройки](/adguard-for-windows/features/settings/) @@ -27,4 +27,4 @@ sidebar_position: 1 - [Другие функции](/adguard-for-windows/features/others/) - Support, license management, tray menu options, app version and updates + Поддержка, управление лицензиями, опции трей-меню, версии и обновления приложения diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index cb6b98101bb..825ac7a22f9 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -17,23 +17,35 @@ sidebar_position: 4 Наконец, есть раздел с настройками прокси. Там вы можете указать, какой прокси-сервер AdGuard должен использовать для обновления фильтров или получения новых версий. -### SockFilter and other network drivers +### Enable traffic filtering -In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. +Traffic filtering is the core mechanism that allows AdGuard to inspect and control the network traffic generated by applications on your computer. When it is enabled, AdGuard intercepts outgoing and incoming connections and checks them against its filtering rules. If a request matches a blocking rule, AdGuard can block it, modify it, or allow it depending on the configuration. In AdGuard for Windows, this interception is implemented through network drivers. -**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. +If HTTPS filtering is enabled, AdGuard performs a controlled local TLS interception: it decrypts the traffic using its local certificate, applies filtering rules, and then re-encrypts the traffic before sending it to the browser. The driver simply provides the system-level access needed for AdGuard to intercept these connections. -The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +#### SockFilter **SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. -Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: +SockFilter was first implemented in version 7.22.4, and it is still considered unstable — you may encounter bugs. Once fully tested and implemented, SockFilter has the potential to offer several advantages over other drivers: -- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. - **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. -- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. -When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. +#### WFP + +**WFP** (Windows Filtering Platform) is a Microsoft networking framework built into Windows that allows software to filter and monitor network packets at different layers of the system networking stack. AdGuard uses WFP to safely hook into the network flow of applications and apply filtering rules before the traffic reaches the browser or the Internet. [More information](https://learn.microsoft.com/en-us/windows/win32/fwp/windows-filtering-platform-architecture-overview). + +While it is a powerful driver, it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) and lower Internet speed for some users. + +#### TDI + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. ### AdGuard VPN diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index b7cca1952a2..270c7818d1f 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -44,17 +44,13 @@ sidebar_position: 2 Many websites gather information about their visitors, such as their IP addresses, browser and operating system details, screen resolution, and the webpage from which the user came or was redirected. Some websites use cookies to mark and identify your browser, save your personal settings and preferences. This allows them to “recognize” you on your next visit. Tracking protection safeguards your personal information from these data- and statistics-gathering systems. -![Tracking protection levels \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection1.png) - You can adjust the _Tracking Protection_ settings as needed. For example, you can prevent websites from receiving the search request that you used to find them on the Internet, automatically delete third- and first-party cookies, and disable location sharing in your browser, to prevent tracking of your whereabouts. -![Tracking protection custom features \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection2.png) - -To learn everything about _Tracking protection_ and its many options, [read this article](/general/stealth-mode). +[Больше о Защите от трекинга](/general/stealth-mode) ### Защита от фишинга -Browsing security gives strong protection against malicious and phishing websites. No, AdGuard for Windows is not an antivirus. It will neither stop the download of a virus when it’s already started, nor delete the already existing ones. But it will warn you if you’re about to proceed to a website whose domain has been added to our “untrusted sites” database, or to download a file from such website. You can find more information about how this module works in the [dedicated article](/general/browsing-security). +Browsing security gives strong protection against malicious and phishing websites. No, AdGuard for Windows is not an antivirus. It will neither stop the download of a virus when it’s already started, nor delete the already existing ones. But it will warn you if you’re about to proceed to a website whose domain has been added to our “untrusted sites” database, or to download a file from such website. [Как работает Защита от фишинга](/general/browsing-security) In this module, you can: @@ -64,7 +60,7 @@ In this module, you can: ![Browsing security \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/browsing_security.png) -In case you want to learn more about Browsing security, read [this article](/general/browsing-security). +[Больше о Защите от фишинга](/general/browsing-security) ### DNS Protection @@ -97,4 +93,4 @@ In the _Parental control_ module you can enable the _Safe search_ and manage the ![Browser Assistant \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/browser_assistant.png) -From this tab you can easily proceed to install AdGuard Browser Assistant, which primary function is to manage filtering directly from the browser. We explained more about how to work with it and what to do if there is no Browser Assistant for your browser in the [separate article](/adguard-for-windows/browser-assistant.md). +From this tab you can easily proceed to install AdGuard Browser Assistant, which primary function is to manage filtering directly from the browser. Подробнее о том, как с ним работать и что делать, если для вашего браузера нет Помощника, мы рассказали [в отдельной статье](/adguard-for-windows/browser-assistant.md). diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md index f51dbf9a497..2435dbfb14b 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ TDI-драйвер — это устаревшая технология Windows, AdGuard уже считает TDI-драйвер устаревшим и планирует его полное удаление. +## Постоянное решение + +From v7.22.4, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows/features/network/#sockfilter-and-other-network-drivers). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Временное решение Определённые изменения в реестре Windows могут заставить браузер перестать использовать AppContainer, в результате чего его процессы снова будут работать вне песочницы. Network Service прекращает использование стека WSK и переключается на сетевой путь, который виден TDI-драйверу. После этого AdGuard восстанавливает способность фильтровать трафик браузера. @@ -136,7 +144,3 @@ You can revert these changes using the undo .reg files provided below. These fil Если такая опция есть, нажмите _Reload policies_. Готово! - -## Постоянное решение - -В будущих версиях мы планируем добавить поддержку драйвера SockFilter. Это решит проблему, устранив конфликты в стеке WFP. [Больше информации](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/general/github-repos.md b/i18n/ru/docusaurus-plugin-content-docs/current/general/github-repos.md new file mode 100644 index 00000000000..dfb164c44bc --- /dev/null +++ b/i18n/ru/docusaurus-plugin-content-docs/current/general/github-repos.md @@ -0,0 +1,238 @@ +--- +title: AdGuard’s GitHub repositories +sidebar_position: 9 +--- + +At AdGuard, our goal is to make the Internet safer, more comfortable, and more transparent. This commitment is reflected not only in our product features and strict privacy policies, but also in the fact that we keep our work as open as possible. That includes actively interacting with our community. + +This is why [all of our products have public repositories](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse) — online spaces where anybody can see what we are working on, report issues directly to AdGuard developers, and even contribute to our open-source projects. The repositories cover our ad-blocking apps, filters, browser extensions, DNS solutions, VPN tools, developer utilities, and more. There are different platforms that offer such functionality, but the most popular one by far is GitHub, and all AdGuard projects are stored there. + +This article lists the most important repositories by category, summarizes the purpose of each one, and gives a simple breakdown of what users can do there. + +:::tip + +Pro tip: Creating an issue on GitHub is the most effective way to bring the attention of AdGuard developers to a problem. Just make sure to check that a similar issue doesn’t already exist and describe the problem in a comprehensive but concise way. If it does exist, you can upvote it. + +::: + +## What is Github and its repositories + +Very simply put, you can think of GitHub as sort of Google Docs for code, where multiple people can work on the same project, track changes, and see who made which updates. It provides a central, cloud-based place to store your code so it’s accessible from anywhere. It also has teamwork tools for reviewing changes, fixing issues, and merging everyone’s work smoothly. + +GitHub is widely used for open-source projects, letting anyone view the code, suggest improvements, and contribute. + +A repository (often called “repo” for short) is the most basic element of GitHub. It’s a place where you can store your code, your files, and each file’s revision history. Repositories can have multiple collaborators and can be either public or private. + +## What can you do in AdGuard’s repositories + +You can find links to key repositories below in this article or visit the [general AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all) for a full list. In most repos, you can: + +- **View README file** on the main page: it gives you an introduction to the product and its repo + ![README file \*border](https://cdn.adtidy.org/content/blog/github-repos/see-readme.png) + +- **Check existing bug reports or feature requests**, comment and upvote + ![Check issues \*border](https://cdn.adtidy.org/content/blog/github-repos/check-issues.png) + +- **Create issues** to report bugs or request features + ![Create issues \*border](https://cdn.adtidy.org/content/blog/github-repos/create-issue.png) + +- **Check releases** for different versions and their changelogs (and install an older version if needed) + ![Check releases \*border](https://cdn.adtidy.org/content/blog/github-repos/check-releases.png) + +- **Install any older or beta version** if needed + ![Download builds \*border](https://cdn.adtidy.org/content/blog/github-repos/download-releases.png) + +:::note + +If you are new to GitHub, you’ll need to create a GitHub account in order to create new issues and comment on the existing ones. + +::: + +In open-source repos advanced users can also: + +- **Browse code** to understand product logic, what technologies are used and how they are implemented +- **Fork and contribute** via pull requests + +Whether you’re a casual user, technical expert, or a developer, AdGuard welcomes all community participation across its GitHub repos. + +## Legal documents + +### [LegalDocs](https://github.com/AdguardTeam/LegalDocs) + +As part of our commitment to transparency, we host all legal documents — such as End-User License Agreements, Privacy Policies, and Terms and Conditions — on GitHub. Our _LegalDocs_ repo lets anyone check the full history of changes to these documents. + +## AdGuard Ad Blocker products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdguardForAndroid](https://github.com/AdguardTeam/AdguardForAndroid) + +Repository of AdGuard for Android — an app that provides system-wide ad blocking. + +### [AdguardForiOS](https://github.com/AdguardTeam/AdguardForiOS) + +Repository of AdGuard for iOS — Safari content blocker with DNS and custom filters. Users can also check open-source code. + +### [AdguardForWindows](https://github.com/AdguardTeam/AdguardForWindows) + +Repository of AdGuard for Windows. Non-open-source; GitHub used as an open bug tracker. + +### [AdguardForMac](https://github.com/AdguardTeam/AdguardForMac) + +Repository of AdGuard for Mac — macOS standalone content blocker. Bug tracker only. + +### [AdguardBrowserExtension](https://github.com/AdguardTeam/AdguardBrowserExtension) + +Repository of AdGuard Browser Extension — extension that provides ad blocking with enhanced privacy for Chrome, Firefox, Opera, Edge. + +### [AdguardForSafari](https://github.com/AdguardTeam/AdGuardForSafari) + +Repository of AdGuard for Safari — Safari ad blocking extension for Mac. Users can also check open-sourced code. + +### [AdGuardCLI](https://github.com/AdguardTeam/AdGuardCLI) + +Repository of AdGuard for Linux — a command‑line interface for managing ad blocking. + +## AdGuard VPN products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdGuardVPNForiOS](https://github.com/AdguardTeam/AdGuardVPNForiOS) + +Repository of AdGuard VPN for iOS. Serves as an open bug tracker. + +### [AdGuardVPNForAndroid](https://github.com/AdguardTeam/AdGuardVPNForAndroid) + +Repository of AdGuard VPN for Android. Serves as an open bug tracker. + +### [AdGuardVPNForWindows](https://github.com/AdguardTeam/AdGuardVPNForWindows) + +Repository of AdGuard VPN for Windows. Serves as an open bug tracker. + +### [AdGuardVPNForMac](https://github.com/AdguardTeam/AdGuardVPNForMac) + +Repository of AdGuard VPN for Mac — app designed for macOS. + +### [AdGuardVPNExtension](https://github.com/AdguardTeam/AdGuardVPNExtension) + +Repository of AdGuard VPN Browser Extension. + +### [AdGuardVPNCLI](https://github.com/AdguardTeam/AdGuardVPNCLI) + +Repository of AdGuard VPN for Linux — a command‑line interface for managing VPN connection. The repo acts as a bug tracker. + +## DNS-based products + +### [AdGuardDNS](https://github.com/AdguardTeam/AdGuardDNS) + +Open-source repository that is also used for tracking bugs and issues related to AdGuard DNS service. Users can: + +- View and report DNS issues +- Suggest improvements + +### [AdGuardHome](https://github.com/AdguardTeam/AdGuardHome) + +Repository of AdGuard Home — free network-wide software for blocking ads and trackers via DNS. Users can: + +- Check and file bug reports or feature requests +- Review or contribute to code +- Download and install releases + +## Documentation and Knowledge bases + +Knowledge bases are aimed to help users better understand and use AdGuard. They describe each AdGuard product in detail: from feature overviews and problem-solving guides to advanced setting manuals and API documentations. In the repositories users can: + +- Suggest corrections or edits to knowledge base articles +- Propose new articles +- Test or run the local version + +### [KnowledgeBase](https://github.com/AdguardTeam/KnowledgeBase) + +Central documentation for AdGuard Ad Blocker and the technologies related to it. + +### [KnowledgeBaseDNS](https://github.com/AdguardTeam/KnowledgeBaseDNS) + +Detailed feature overview, troubleshooting guides and documentation for AdGuard DNS (both Public and Private), AdGuard Home, and everything related to them. + +### [KnowledgeBaseVPN](https://github.com/AdguardTeam/KnowledgeBaseVPN) + +Detailed feature overview and troubleshooting guides for AdGuard VPN. + +### [KnowledgeBaseMail](https://github.com/AdguardTeam/KnowledgeBaseMail) + +Detailed feature overview and troubleshooting guides of AdGuard Mail. + +## Core libraries + +### [CoreLibs](https://github.com/AdguardTeam/CoreLibs) + +AdGuard’s cross-platform core filtering engine. Used in Android, Windows, and Mac products. Users can: + +- Explore filtering logic and DNS handling +- Report bugs and suggest features via Issues + +### [DNSLibs](https://github.com/AdguardTeam/DNSLibs) + +A DNS library used by CoreLibs and AdGuardHome. Users can: + +- Review and contribute to low-level DNS implementation +- Suggest optimizations + +### [VPNLibs](https://github.com/AdguardTeam/VPNLibs) + +Shared codebase used in AdGuard VPN products across platforms for AdGuard VPN protocol implementation. Users can: + +- Contribute to VPN stack behavior +- Report or view performance issues and bugs + +## Core ad blocking and filtering technologies + +### [AdguardFilters](https://github.com/AdguardTeam/AdguardFilters) + +Contains AdGuard’s core filter lists. Users can: + +- View and download filter lists +- Create issues to report false positives or suggest new rules +- Monitor updates to filter logic + +### [AdGuardSDNSFilter](https://github.com/AdguardTeam/AdGuardSDNSFilter) + +Repository of AdGuard DNS filter — the main DNS-level blocking list used in AdGuard DNS and DNS filtering features. Users can: + +- Inspect the current rule set +- Propose changes or additions + +### [AGLint](https://github.com/AdguardTeam/AGLint) + +A linter for adblock filter list syntax. Users can: + +- Install AGLint to check their projects for rule issues +- Contribute to lint rules + +### [Scriptlets](https://github.com/AdguardTeam/Scriptlets) + +JavaScript helpers used in filtering rules. Users can: + +- Explore available scriptlets +- Submit pull requests for new scriptlets + +### [tsurlfilter](https://github.com/AdguardTeam/tsurlfilter) + +TypeScript content blocker library for browser extensions. Users can: + +- Explore how filtering logic is implemented +- Contribute fixes and features + +## There’s more + +Above, we listed 27 main public AdGuard repositories out of 96 total. If you want to go down the rabbit hole, you can [find the rest on the AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse). + +We’ll be waiting for your feedback there! Stay safe online and offline. diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/general/how-to-install.md b/i18n/ru/docusaurus-plugin-content-docs/current/general/how-to-install.md index a6c4014b4d3..3a6f9237fcb 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/general/how-to-install.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/general/how-to-install.md @@ -1,6 +1,6 @@ --- title: Как установить AdGuard -sidebar_position: 9 +sidebar_position: 10 --- В зависимости от того, какое приложение или браузерное расширение AdGuard вы хотите установить, перейдите по одной из этих ссылок и найдите соответствующую инструкцию: diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md index 3953f47d26f..05642d350b0 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md @@ -43,6 +43,14 @@ Here you can choose which proxy AdGuard should use to download filter updates or ## Use SockFilter driver -Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. +Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. If this option is disabled, AdGuard will switch to the older WFP driver instead. -If this option is disabled, AdGuard will switch to the older WFP driver instead. +SockFilter was first introduced in v8.0 RC. It is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md index 251e49cf286..1ab588bb16c 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Because of this, TDI-based traffic visibility becomes increasingly unstable. In AdGuard already treats the TDI driver as deprecated, and its complete removal is planned as the product evolves. +## Permanent solution + +From v8.0 RC, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows-8/settings/app-settings/network-settings/). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Temporary solution Certain Windows registry changes can force the browser to stop using AppContainer, causing its processes to run in a non-sandboxed mode again. Network Service stops using the WSK stack and falls back to a network path that the TDI driver can see. AdGuard then regains the ability to filter browser traffic. @@ -123,7 +131,3 @@ You should see the following policies active: If available, click _Reload policies_. Done! - -## Permanent solution - -We’re planning to add support for the SockFilter driver in the upcoming versions. It will fix the issue by solving conflicts in the WFP stack. [More information](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index 5945618ea9c..f8074e9cfa1 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -17,23 +17,35 @@ In this module you can select the checkbox _Use AdGuard as an HTTP proxy_ to use At last, there is a section with proxy settings. There you can specify which proxy server AdGuard should use to update filters, get new versions, and so on. -### SockFilter and other network drivers +### Enable traffic filtering -In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. +Traffic filtering is the core mechanism that allows AdGuard to inspect and control the network traffic generated by applications on your computer. When it is enabled, AdGuard intercepts outgoing and incoming connections and checks them against its filtering rules. If a request matches a blocking rule, AdGuard can block it, modify it, or allow it depending on the configuration. In AdGuard for Windows, this interception is implemented through network drivers. -**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. +If HTTPS filtering is enabled, AdGuard performs a controlled local TLS interception: it decrypts the traffic using its local certificate, applies filtering rules, and then re-encrypts the traffic before sending it to the browser. The driver simply provides the system-level access needed for AdGuard to intercept these connections. -The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +#### SockFilter **SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. -Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: +SockFilter was first implemented in version 7.22.4, and it is still considered unstable — you may encounter bugs. Once fully tested and implemented, SockFilter has the potential to offer several advantages over other drivers: -- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. - **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. -- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. -When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. +#### WFP + +**WFP** (Windows Filtering Platform) is a Microsoft networking framework built into Windows that allows software to filter and monitor network packets at different layers of the system networking stack. AdGuard uses WFP to safely hook into the network flow of applications and apply filtering rules before the traffic reaches the browser or the Internet. [More information](https://learn.microsoft.com/en-us/windows/win32/fwp/windows-filtering-platform-architecture-overview). + +While it is a powerful driver, it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) and lower Internet speed for some users. + +#### TDI + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. ### AdGuard VPN diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index ab90a964b9f..5699b31b033 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -44,12 +44,8 @@ Before you start manually writing your own rules read our detailed [syntax guide Many websites gather information about their visitors, such as their IP addresses, browser and operating system details, screen resolution, and the webpage from which the user came or was redirected. Some websites use cookies to mark and identify your browser, save your personal settings and preferences. This allows them to “recognize” you on your next visit. Tracking protection safeguards your personal information from these data- and statistics-gathering systems. -![Tracking protection levels \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection1.png) - You can adjust the _Tracking Protection_ settings as needed. For example, you can prevent websites from receiving the search request that you used to find them on the Internet, automatically delete third- and first-party cookies, and disable location sharing in your browser, to prevent tracking of your whereabouts. -![Tracking protection custom features \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection2.png) - To learn everything about _Tracking protection_ and its many options, [read this article](/general/stealth-mode). ### Browsing security diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md index 62370bf3eb1..bec08d0c665 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Because of this, TDI-based traffic visibility becomes increasingly unstable. In AdGuard already treats the TDI driver as deprecated, and its complete removal is planned as the product evolves. +## Permanent solution + +From v7.22.4, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows/features/network/#sockfilter-and-other-network-drivers). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Temporary solution Certain Windows registry changes can force the browser to stop using AppContainer, causing its processes to run in a non-sandboxed mode again. Network Service stops using the WSK stack and falls back to a network path that the TDI driver can see. AdGuard then regains the ability to filter browser traffic. @@ -136,7 +144,3 @@ You should see the following policies active: If available, click _Reload policies_. Done! - -## Permanent solution - -We’re planning to add support for the SockFilter driver in the upcoming versions. It will fix the issue by solving conflicts in the WFP stack. [More information](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/general/github-repos.md b/i18n/sk/docusaurus-plugin-content-docs/current/general/github-repos.md new file mode 100644 index 00000000000..dfb164c44bc --- /dev/null +++ b/i18n/sk/docusaurus-plugin-content-docs/current/general/github-repos.md @@ -0,0 +1,238 @@ +--- +title: AdGuard’s GitHub repositories +sidebar_position: 9 +--- + +At AdGuard, our goal is to make the Internet safer, more comfortable, and more transparent. This commitment is reflected not only in our product features and strict privacy policies, but also in the fact that we keep our work as open as possible. That includes actively interacting with our community. + +This is why [all of our products have public repositories](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse) — online spaces where anybody can see what we are working on, report issues directly to AdGuard developers, and even contribute to our open-source projects. The repositories cover our ad-blocking apps, filters, browser extensions, DNS solutions, VPN tools, developer utilities, and more. There are different platforms that offer such functionality, but the most popular one by far is GitHub, and all AdGuard projects are stored there. + +This article lists the most important repositories by category, summarizes the purpose of each one, and gives a simple breakdown of what users can do there. + +:::tip + +Pro tip: Creating an issue on GitHub is the most effective way to bring the attention of AdGuard developers to a problem. Just make sure to check that a similar issue doesn’t already exist and describe the problem in a comprehensive but concise way. If it does exist, you can upvote it. + +::: + +## What is Github and its repositories + +Very simply put, you can think of GitHub as sort of Google Docs for code, where multiple people can work on the same project, track changes, and see who made which updates. It provides a central, cloud-based place to store your code so it’s accessible from anywhere. It also has teamwork tools for reviewing changes, fixing issues, and merging everyone’s work smoothly. + +GitHub is widely used for open-source projects, letting anyone view the code, suggest improvements, and contribute. + +A repository (often called “repo” for short) is the most basic element of GitHub. It’s a place where you can store your code, your files, and each file’s revision history. Repositories can have multiple collaborators and can be either public or private. + +## What can you do in AdGuard’s repositories + +You can find links to key repositories below in this article or visit the [general AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all) for a full list. In most repos, you can: + +- **View README file** on the main page: it gives you an introduction to the product and its repo + ![README file \*border](https://cdn.adtidy.org/content/blog/github-repos/see-readme.png) + +- **Check existing bug reports or feature requests**, comment and upvote + ![Check issues \*border](https://cdn.adtidy.org/content/blog/github-repos/check-issues.png) + +- **Create issues** to report bugs or request features + ![Create issues \*border](https://cdn.adtidy.org/content/blog/github-repos/create-issue.png) + +- **Check releases** for different versions and their changelogs (and install an older version if needed) + ![Check releases \*border](https://cdn.adtidy.org/content/blog/github-repos/check-releases.png) + +- **Install any older or beta version** if needed + ![Download builds \*border](https://cdn.adtidy.org/content/blog/github-repos/download-releases.png) + +:::note + +If you are new to GitHub, you’ll need to create a GitHub account in order to create new issues and comment on the existing ones. + +::: + +In open-source repos advanced users can also: + +- **Browse code** to understand product logic, what technologies are used and how they are implemented +- **Fork and contribute** via pull requests + +Whether you’re a casual user, technical expert, or a developer, AdGuard welcomes all community participation across its GitHub repos. + +## Legal documents + +### [LegalDocs](https://github.com/AdguardTeam/LegalDocs) + +As part of our commitment to transparency, we host all legal documents — such as End-User License Agreements, Privacy Policies, and Terms and Conditions — on GitHub. Our _LegalDocs_ repo lets anyone check the full history of changes to these documents. + +## AdGuard Ad Blocker products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdguardForAndroid](https://github.com/AdguardTeam/AdguardForAndroid) + +Repository of AdGuard for Android — an app that provides system-wide ad blocking. + +### [AdguardForiOS](https://github.com/AdguardTeam/AdguardForiOS) + +Repository of AdGuard for iOS — Safari content blocker with DNS and custom filters. Users can also check open-source code. + +### [AdguardForWindows](https://github.com/AdguardTeam/AdguardForWindows) + +Repository of AdGuard for Windows. Non-open-source; GitHub used as an open bug tracker. + +### [AdguardForMac](https://github.com/AdguardTeam/AdguardForMac) + +Repository of AdGuard for Mac — macOS standalone content blocker. Bug tracker only. + +### [AdguardBrowserExtension](https://github.com/AdguardTeam/AdguardBrowserExtension) + +Repository of AdGuard Browser Extension — extension that provides ad blocking with enhanced privacy for Chrome, Firefox, Opera, Edge. + +### [AdguardForSafari](https://github.com/AdguardTeam/AdGuardForSafari) + +Repository of AdGuard for Safari — Safari ad blocking extension for Mac. Users can also check open-sourced code. + +### [AdGuardCLI](https://github.com/AdguardTeam/AdGuardCLI) + +Repository of AdGuard for Linux — a command‑line interface for managing ad blocking. + +## AdGuard VPN products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdGuardVPNForiOS](https://github.com/AdguardTeam/AdGuardVPNForiOS) + +Repository of AdGuard VPN for iOS. Serves as an open bug tracker. + +### [AdGuardVPNForAndroid](https://github.com/AdguardTeam/AdGuardVPNForAndroid) + +Repository of AdGuard VPN for Android. Serves as an open bug tracker. + +### [AdGuardVPNForWindows](https://github.com/AdguardTeam/AdGuardVPNForWindows) + +Repository of AdGuard VPN for Windows. Serves as an open bug tracker. + +### [AdGuardVPNForMac](https://github.com/AdguardTeam/AdGuardVPNForMac) + +Repository of AdGuard VPN for Mac — app designed for macOS. + +### [AdGuardVPNExtension](https://github.com/AdguardTeam/AdGuardVPNExtension) + +Repository of AdGuard VPN Browser Extension. + +### [AdGuardVPNCLI](https://github.com/AdguardTeam/AdGuardVPNCLI) + +Repository of AdGuard VPN for Linux — a command‑line interface for managing VPN connection. The repo acts as a bug tracker. + +## DNS-based products + +### [AdGuardDNS](https://github.com/AdguardTeam/AdGuardDNS) + +Open-source repository that is also used for tracking bugs and issues related to AdGuard DNS service. Users can: + +- View and report DNS issues +- Suggest improvements + +### [AdGuardHome](https://github.com/AdguardTeam/AdGuardHome) + +Repository of AdGuard Home — free network-wide software for blocking ads and trackers via DNS. Users can: + +- Check and file bug reports or feature requests +- Review or contribute to code +- Download and install releases + +## Documentation and Knowledge bases + +Knowledge bases are aimed to help users better understand and use AdGuard. They describe each AdGuard product in detail: from feature overviews and problem-solving guides to advanced setting manuals and API documentations. In the repositories users can: + +- Suggest corrections or edits to knowledge base articles +- Propose new articles +- Test or run the local version + +### [KnowledgeBase](https://github.com/AdguardTeam/KnowledgeBase) + +Central documentation for AdGuard Ad Blocker and the technologies related to it. + +### [KnowledgeBaseDNS](https://github.com/AdguardTeam/KnowledgeBaseDNS) + +Detailed feature overview, troubleshooting guides and documentation for AdGuard DNS (both Public and Private), AdGuard Home, and everything related to them. + +### [KnowledgeBaseVPN](https://github.com/AdguardTeam/KnowledgeBaseVPN) + +Detailed feature overview and troubleshooting guides for AdGuard VPN. + +### [KnowledgeBaseMail](https://github.com/AdguardTeam/KnowledgeBaseMail) + +Detailed feature overview and troubleshooting guides of AdGuard Mail. + +## Core libraries + +### [CoreLibs](https://github.com/AdguardTeam/CoreLibs) + +AdGuard’s cross-platform core filtering engine. Used in Android, Windows, and Mac products. Users can: + +- Explore filtering logic and DNS handling +- Report bugs and suggest features via Issues + +### [DNSLibs](https://github.com/AdguardTeam/DNSLibs) + +A DNS library used by CoreLibs and AdGuardHome. Users can: + +- Review and contribute to low-level DNS implementation +- Suggest optimizations + +### [VPNLibs](https://github.com/AdguardTeam/VPNLibs) + +Shared codebase used in AdGuard VPN products across platforms for AdGuard VPN protocol implementation. Users can: + +- Contribute to VPN stack behavior +- Report or view performance issues and bugs + +## Core ad blocking and filtering technologies + +### [AdguardFilters](https://github.com/AdguardTeam/AdguardFilters) + +Contains AdGuard’s core filter lists. Users can: + +- View and download filter lists +- Create issues to report false positives or suggest new rules +- Monitor updates to filter logic + +### [AdGuardSDNSFilter](https://github.com/AdguardTeam/AdGuardSDNSFilter) + +Repository of AdGuard DNS filter — the main DNS-level blocking list used in AdGuard DNS and DNS filtering features. Users can: + +- Inspect the current rule set +- Propose changes or additions + +### [AGLint](https://github.com/AdguardTeam/AGLint) + +A linter for adblock filter list syntax. Users can: + +- Install AGLint to check their projects for rule issues +- Contribute to lint rules + +### [Scriptlets](https://github.com/AdguardTeam/Scriptlets) + +JavaScript helpers used in filtering rules. Users can: + +- Explore available scriptlets +- Submit pull requests for new scriptlets + +### [tsurlfilter](https://github.com/AdguardTeam/tsurlfilter) + +TypeScript content blocker library for browser extensions. Users can: + +- Explore how filtering logic is implemented +- Contribute fixes and features + +## There’s more + +Above, we listed 27 main public AdGuard repositories out of 96 total. If you want to go down the rabbit hole, you can [find the rest on the AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse). + +We’ll be waiting for your feedback there! Stay safe online and offline. diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/general/how-to-install.md b/i18n/sk/docusaurus-plugin-content-docs/current/general/how-to-install.md index 106a29529a8..4ba78d7a094 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/general/how-to-install.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/general/how-to-install.md @@ -1,6 +1,6 @@ --- title: How to install AdGuard -sidebar_position: 9 +sidebar_position: 10 --- Depending on which AdGuard app or browser extension you want to install, follow one of these links to find the relevant article: diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md index 3953f47d26f..05642d350b0 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md @@ -43,6 +43,14 @@ Here you can choose which proxy AdGuard should use to download filter updates or ## Use SockFilter driver -Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. +Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. If this option is disabled, AdGuard will switch to the older WFP driver instead. -If this option is disabled, AdGuard will switch to the older WFP driver instead. +SockFilter was first introduced in v8.0 RC. It is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md index 251e49cf286..1ab588bb16c 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Because of this, TDI-based traffic visibility becomes increasingly unstable. In AdGuard already treats the TDI driver as deprecated, and its complete removal is planned as the product evolves. +## Permanent solution + +From v8.0 RC, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows-8/settings/app-settings/network-settings/). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Temporary solution Certain Windows registry changes can force the browser to stop using AppContainer, causing its processes to run in a non-sandboxed mode again. Network Service stops using the WSK stack and falls back to a network path that the TDI driver can see. AdGuard then regains the ability to filter browser traffic. @@ -123,7 +131,3 @@ You should see the following policies active: If available, click _Reload policies_. Done! - -## Permanent solution - -We’re planning to add support for the SockFilter driver in the upcoming versions. It will fix the issue by solving conflicts in the WFP stack. [More information](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index 5945618ea9c..f8074e9cfa1 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -17,23 +17,35 @@ In this module you can select the checkbox _Use AdGuard as an HTTP proxy_ to use At last, there is a section with proxy settings. There you can specify which proxy server AdGuard should use to update filters, get new versions, and so on. -### SockFilter and other network drivers +### Enable traffic filtering -In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. +Traffic filtering is the core mechanism that allows AdGuard to inspect and control the network traffic generated by applications on your computer. When it is enabled, AdGuard intercepts outgoing and incoming connections and checks them against its filtering rules. If a request matches a blocking rule, AdGuard can block it, modify it, or allow it depending on the configuration. In AdGuard for Windows, this interception is implemented through network drivers. -**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. +If HTTPS filtering is enabled, AdGuard performs a controlled local TLS interception: it decrypts the traffic using its local certificate, applies filtering rules, and then re-encrypts the traffic before sending it to the browser. The driver simply provides the system-level access needed for AdGuard to intercept these connections. -The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +#### SockFilter **SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. -Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: +SockFilter was first implemented in version 7.22.4, and it is still considered unstable — you may encounter bugs. Once fully tested and implemented, SockFilter has the potential to offer several advantages over other drivers: -- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. - **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. -- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. -When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. +#### WFP + +**WFP** (Windows Filtering Platform) is a Microsoft networking framework built into Windows that allows software to filter and monitor network packets at different layers of the system networking stack. AdGuard uses WFP to safely hook into the network flow of applications and apply filtering rules before the traffic reaches the browser or the Internet. [More information](https://learn.microsoft.com/en-us/windows/win32/fwp/windows-filtering-platform-architecture-overview). + +While it is a powerful driver, it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) and lower Internet speed for some users. + +#### TDI + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. ### AdGuard VPN diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index ab90a964b9f..5699b31b033 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -44,12 +44,8 @@ Before you start manually writing your own rules read our detailed [syntax guide Many websites gather information about their visitors, such as their IP addresses, browser and operating system details, screen resolution, and the webpage from which the user came or was redirected. Some websites use cookies to mark and identify your browser, save your personal settings and preferences. This allows them to “recognize” you on your next visit. Tracking protection safeguards your personal information from these data- and statistics-gathering systems. -![Tracking protection levels \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection1.png) - You can adjust the _Tracking Protection_ settings as needed. For example, you can prevent websites from receiving the search request that you used to find them on the Internet, automatically delete third- and first-party cookies, and disable location sharing in your browser, to prevent tracking of your whereabouts. -![Tracking protection custom features \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection2.png) - To learn everything about _Tracking protection_ and its many options, [read this article](/general/stealth-mode). ### Browsing security diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md index 62370bf3eb1..bec08d0c665 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Because of this, TDI-based traffic visibility becomes increasingly unstable. In AdGuard already treats the TDI driver as deprecated, and its complete removal is planned as the product evolves. +## Permanent solution + +From v7.22.4, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows/features/network/#sockfilter-and-other-network-drivers). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Temporary solution Certain Windows registry changes can force the browser to stop using AppContainer, causing its processes to run in a non-sandboxed mode again. Network Service stops using the WSK stack and falls back to a network path that the TDI driver can see. AdGuard then regains the ability to filter browser traffic. @@ -136,7 +144,3 @@ You should see the following policies active: If available, click _Reload policies_. Done! - -## Permanent solution - -We’re planning to add support for the SockFilter driver in the upcoming versions. It will fix the issue by solving conflicts in the WFP stack. [More information](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/general/github-repos.md b/i18n/sl/docusaurus-plugin-content-docs/current/general/github-repos.md new file mode 100644 index 00000000000..dfb164c44bc --- /dev/null +++ b/i18n/sl/docusaurus-plugin-content-docs/current/general/github-repos.md @@ -0,0 +1,238 @@ +--- +title: AdGuard’s GitHub repositories +sidebar_position: 9 +--- + +At AdGuard, our goal is to make the Internet safer, more comfortable, and more transparent. This commitment is reflected not only in our product features and strict privacy policies, but also in the fact that we keep our work as open as possible. That includes actively interacting with our community. + +This is why [all of our products have public repositories](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse) — online spaces where anybody can see what we are working on, report issues directly to AdGuard developers, and even contribute to our open-source projects. The repositories cover our ad-blocking apps, filters, browser extensions, DNS solutions, VPN tools, developer utilities, and more. There are different platforms that offer such functionality, but the most popular one by far is GitHub, and all AdGuard projects are stored there. + +This article lists the most important repositories by category, summarizes the purpose of each one, and gives a simple breakdown of what users can do there. + +:::tip + +Pro tip: Creating an issue on GitHub is the most effective way to bring the attention of AdGuard developers to a problem. Just make sure to check that a similar issue doesn’t already exist and describe the problem in a comprehensive but concise way. If it does exist, you can upvote it. + +::: + +## What is Github and its repositories + +Very simply put, you can think of GitHub as sort of Google Docs for code, where multiple people can work on the same project, track changes, and see who made which updates. It provides a central, cloud-based place to store your code so it’s accessible from anywhere. It also has teamwork tools for reviewing changes, fixing issues, and merging everyone’s work smoothly. + +GitHub is widely used for open-source projects, letting anyone view the code, suggest improvements, and contribute. + +A repository (often called “repo” for short) is the most basic element of GitHub. It’s a place where you can store your code, your files, and each file’s revision history. Repositories can have multiple collaborators and can be either public or private. + +## What can you do in AdGuard’s repositories + +You can find links to key repositories below in this article or visit the [general AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all) for a full list. In most repos, you can: + +- **View README file** on the main page: it gives you an introduction to the product and its repo + ![README file \*border](https://cdn.adtidy.org/content/blog/github-repos/see-readme.png) + +- **Check existing bug reports or feature requests**, comment and upvote + ![Check issues \*border](https://cdn.adtidy.org/content/blog/github-repos/check-issues.png) + +- **Create issues** to report bugs or request features + ![Create issues \*border](https://cdn.adtidy.org/content/blog/github-repos/create-issue.png) + +- **Check releases** for different versions and their changelogs (and install an older version if needed) + ![Check releases \*border](https://cdn.adtidy.org/content/blog/github-repos/check-releases.png) + +- **Install any older or beta version** if needed + ![Download builds \*border](https://cdn.adtidy.org/content/blog/github-repos/download-releases.png) + +:::note + +If you are new to GitHub, you’ll need to create a GitHub account in order to create new issues and comment on the existing ones. + +::: + +In open-source repos advanced users can also: + +- **Browse code** to understand product logic, what technologies are used and how they are implemented +- **Fork and contribute** via pull requests + +Whether you’re a casual user, technical expert, or a developer, AdGuard welcomes all community participation across its GitHub repos. + +## Legal documents + +### [LegalDocs](https://github.com/AdguardTeam/LegalDocs) + +As part of our commitment to transparency, we host all legal documents — such as End-User License Agreements, Privacy Policies, and Terms and Conditions — on GitHub. Our _LegalDocs_ repo lets anyone check the full history of changes to these documents. + +## AdGuard Ad Blocker products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdguardForAndroid](https://github.com/AdguardTeam/AdguardForAndroid) + +Repository of AdGuard for Android — an app that provides system-wide ad blocking. + +### [AdguardForiOS](https://github.com/AdguardTeam/AdguardForiOS) + +Repository of AdGuard for iOS — Safari content blocker with DNS and custom filters. Users can also check open-source code. + +### [AdguardForWindows](https://github.com/AdguardTeam/AdguardForWindows) + +Repository of AdGuard for Windows. Non-open-source; GitHub used as an open bug tracker. + +### [AdguardForMac](https://github.com/AdguardTeam/AdguardForMac) + +Repository of AdGuard for Mac — macOS standalone content blocker. Bug tracker only. + +### [AdguardBrowserExtension](https://github.com/AdguardTeam/AdguardBrowserExtension) + +Repository of AdGuard Browser Extension — extension that provides ad blocking with enhanced privacy for Chrome, Firefox, Opera, Edge. + +### [AdguardForSafari](https://github.com/AdguardTeam/AdGuardForSafari) + +Repository of AdGuard for Safari — Safari ad blocking extension for Mac. Users can also check open-sourced code. + +### [AdGuardCLI](https://github.com/AdguardTeam/AdGuardCLI) + +Repository of AdGuard for Linux — a command‑line interface for managing ad blocking. + +## AdGuard VPN products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdGuardVPNForiOS](https://github.com/AdguardTeam/AdGuardVPNForiOS) + +Repository of AdGuard VPN for iOS. Serves as an open bug tracker. + +### [AdGuardVPNForAndroid](https://github.com/AdguardTeam/AdGuardVPNForAndroid) + +Repository of AdGuard VPN for Android. Serves as an open bug tracker. + +### [AdGuardVPNForWindows](https://github.com/AdguardTeam/AdGuardVPNForWindows) + +Repository of AdGuard VPN for Windows. Serves as an open bug tracker. + +### [AdGuardVPNForMac](https://github.com/AdguardTeam/AdGuardVPNForMac) + +Repository of AdGuard VPN for Mac — app designed for macOS. + +### [AdGuardVPNExtension](https://github.com/AdguardTeam/AdGuardVPNExtension) + +Repository of AdGuard VPN Browser Extension. + +### [AdGuardVPNCLI](https://github.com/AdguardTeam/AdGuardVPNCLI) + +Repository of AdGuard VPN for Linux — a command‑line interface for managing VPN connection. The repo acts as a bug tracker. + +## DNS-based products + +### [AdGuardDNS](https://github.com/AdguardTeam/AdGuardDNS) + +Open-source repository that is also used for tracking bugs and issues related to AdGuard DNS service. Users can: + +- View and report DNS issues +- Suggest improvements + +### [AdGuardHome](https://github.com/AdguardTeam/AdGuardHome) + +Repository of AdGuard Home — free network-wide software for blocking ads and trackers via DNS. Users can: + +- Check and file bug reports or feature requests +- Review or contribute to code +- Download and install releases + +## Documentation and Knowledge bases + +Knowledge bases are aimed to help users better understand and use AdGuard. They describe each AdGuard product in detail: from feature overviews and problem-solving guides to advanced setting manuals and API documentations. In the repositories users can: + +- Suggest corrections or edits to knowledge base articles +- Propose new articles +- Test or run the local version + +### [KnowledgeBase](https://github.com/AdguardTeam/KnowledgeBase) + +Central documentation for AdGuard Ad Blocker and the technologies related to it. + +### [KnowledgeBaseDNS](https://github.com/AdguardTeam/KnowledgeBaseDNS) + +Detailed feature overview, troubleshooting guides and documentation for AdGuard DNS (both Public and Private), AdGuard Home, and everything related to them. + +### [KnowledgeBaseVPN](https://github.com/AdguardTeam/KnowledgeBaseVPN) + +Detailed feature overview and troubleshooting guides for AdGuard VPN. + +### [KnowledgeBaseMail](https://github.com/AdguardTeam/KnowledgeBaseMail) + +Detailed feature overview and troubleshooting guides of AdGuard Mail. + +## Core libraries + +### [CoreLibs](https://github.com/AdguardTeam/CoreLibs) + +AdGuard’s cross-platform core filtering engine. Used in Android, Windows, and Mac products. Users can: + +- Explore filtering logic and DNS handling +- Report bugs and suggest features via Issues + +### [DNSLibs](https://github.com/AdguardTeam/DNSLibs) + +A DNS library used by CoreLibs and AdGuardHome. Users can: + +- Review and contribute to low-level DNS implementation +- Suggest optimizations + +### [VPNLibs](https://github.com/AdguardTeam/VPNLibs) + +Shared codebase used in AdGuard VPN products across platforms for AdGuard VPN protocol implementation. Users can: + +- Contribute to VPN stack behavior +- Report or view performance issues and bugs + +## Core ad blocking and filtering technologies + +### [AdguardFilters](https://github.com/AdguardTeam/AdguardFilters) + +Contains AdGuard’s core filter lists. Users can: + +- View and download filter lists +- Create issues to report false positives or suggest new rules +- Monitor updates to filter logic + +### [AdGuardSDNSFilter](https://github.com/AdguardTeam/AdGuardSDNSFilter) + +Repository of AdGuard DNS filter — the main DNS-level blocking list used in AdGuard DNS and DNS filtering features. Users can: + +- Inspect the current rule set +- Propose changes or additions + +### [AGLint](https://github.com/AdguardTeam/AGLint) + +A linter for adblock filter list syntax. Users can: + +- Install AGLint to check their projects for rule issues +- Contribute to lint rules + +### [Scriptlets](https://github.com/AdguardTeam/Scriptlets) + +JavaScript helpers used in filtering rules. Users can: + +- Explore available scriptlets +- Submit pull requests for new scriptlets + +### [tsurlfilter](https://github.com/AdguardTeam/tsurlfilter) + +TypeScript content blocker library for browser extensions. Users can: + +- Explore how filtering logic is implemented +- Contribute fixes and features + +## There’s more + +Above, we listed 27 main public AdGuard repositories out of 96 total. If you want to go down the rabbit hole, you can [find the rest on the AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse). + +We’ll be waiting for your feedback there! Stay safe online and offline. diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/general/how-to-install.md b/i18n/sl/docusaurus-plugin-content-docs/current/general/how-to-install.md index 106a29529a8..4ba78d7a094 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/general/how-to-install.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/general/how-to-install.md @@ -1,6 +1,6 @@ --- title: How to install AdGuard -sidebar_position: 9 +sidebar_position: 10 --- Depending on which AdGuard app or browser extension you want to install, follow one of these links to find the relevant article: diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md index 3953f47d26f..05642d350b0 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md @@ -43,6 +43,14 @@ Here you can choose which proxy AdGuard should use to download filter updates or ## Use SockFilter driver -Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. +Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. If this option is disabled, AdGuard will switch to the older WFP driver instead. -If this option is disabled, AdGuard will switch to the older WFP driver instead. +SockFilter was first introduced in v8.0 RC. It is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md index 251e49cf286..1ab588bb16c 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Because of this, TDI-based traffic visibility becomes increasingly unstable. In AdGuard already treats the TDI driver as deprecated, and its complete removal is planned as the product evolves. +## Permanent solution + +From v8.0 RC, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows-8/settings/app-settings/network-settings/). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Temporary solution Certain Windows registry changes can force the browser to stop using AppContainer, causing its processes to run in a non-sandboxed mode again. Network Service stops using the WSK stack and falls back to a network path that the TDI driver can see. AdGuard then regains the ability to filter browser traffic. @@ -123,7 +131,3 @@ You should see the following policies active: If available, click _Reload policies_. Done! - -## Permanent solution - -We’re planning to add support for the SockFilter driver in the upcoming versions. It will fix the issue by solving conflicts in the WFP stack. [More information](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index 5945618ea9c..f8074e9cfa1 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -17,23 +17,35 @@ In this module you can select the checkbox _Use AdGuard as an HTTP proxy_ to use At last, there is a section with proxy settings. There you can specify which proxy server AdGuard should use to update filters, get new versions, and so on. -### SockFilter and other network drivers +### Enable traffic filtering -In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. +Traffic filtering is the core mechanism that allows AdGuard to inspect and control the network traffic generated by applications on your computer. When it is enabled, AdGuard intercepts outgoing and incoming connections and checks them against its filtering rules. If a request matches a blocking rule, AdGuard can block it, modify it, or allow it depending on the configuration. In AdGuard for Windows, this interception is implemented through network drivers. -**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. +If HTTPS filtering is enabled, AdGuard performs a controlled local TLS interception: it decrypts the traffic using its local certificate, applies filtering rules, and then re-encrypts the traffic before sending it to the browser. The driver simply provides the system-level access needed for AdGuard to intercept these connections. -The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +#### SockFilter **SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. -Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: +SockFilter was first implemented in version 7.22.4, and it is still considered unstable — you may encounter bugs. Once fully tested and implemented, SockFilter has the potential to offer several advantages over other drivers: -- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. - **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. -- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. -When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. +#### WFP + +**WFP** (Windows Filtering Platform) is a Microsoft networking framework built into Windows that allows software to filter and monitor network packets at different layers of the system networking stack. AdGuard uses WFP to safely hook into the network flow of applications and apply filtering rules before the traffic reaches the browser or the Internet. [More information](https://learn.microsoft.com/en-us/windows/win32/fwp/windows-filtering-platform-architecture-overview). + +While it is a powerful driver, it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) and lower Internet speed for some users. + +#### TDI + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. ### AdGuard VPN diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index ab90a964b9f..5699b31b033 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -44,12 +44,8 @@ Before you start manually writing your own rules read our detailed [syntax guide Many websites gather information about their visitors, such as their IP addresses, browser and operating system details, screen resolution, and the webpage from which the user came or was redirected. Some websites use cookies to mark and identify your browser, save your personal settings and preferences. This allows them to “recognize” you on your next visit. Tracking protection safeguards your personal information from these data- and statistics-gathering systems. -![Tracking protection levels \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection1.png) - You can adjust the _Tracking Protection_ settings as needed. For example, you can prevent websites from receiving the search request that you used to find them on the Internet, automatically delete third- and first-party cookies, and disable location sharing in your browser, to prevent tracking of your whereabouts. -![Tracking protection custom features \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection2.png) - To learn everything about _Tracking protection_ and its many options, [read this article](/general/stealth-mode). ### Browsing security diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md index 62370bf3eb1..bec08d0c665 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Because of this, TDI-based traffic visibility becomes increasingly unstable. In AdGuard already treats the TDI driver as deprecated, and its complete removal is planned as the product evolves. +## Permanent solution + +From v7.22.4, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows/features/network/#sockfilter-and-other-network-drivers). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Temporary solution Certain Windows registry changes can force the browser to stop using AppContainer, causing its processes to run in a non-sandboxed mode again. Network Service stops using the WSK stack and falls back to a network path that the TDI driver can see. AdGuard then regains the ability to filter browser traffic. @@ -136,7 +144,3 @@ You should see the following policies active: If available, click _Reload policies_. Done! - -## Permanent solution - -We’re planning to add support for the SockFilter driver in the upcoming versions. It will fix the issue by solving conflicts in the WFP stack. [More information](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/general/github-repos.md b/i18n/sv/docusaurus-plugin-content-docs/current/general/github-repos.md new file mode 100644 index 00000000000..dfb164c44bc --- /dev/null +++ b/i18n/sv/docusaurus-plugin-content-docs/current/general/github-repos.md @@ -0,0 +1,238 @@ +--- +title: AdGuard’s GitHub repositories +sidebar_position: 9 +--- + +At AdGuard, our goal is to make the Internet safer, more comfortable, and more transparent. This commitment is reflected not only in our product features and strict privacy policies, but also in the fact that we keep our work as open as possible. That includes actively interacting with our community. + +This is why [all of our products have public repositories](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse) — online spaces where anybody can see what we are working on, report issues directly to AdGuard developers, and even contribute to our open-source projects. The repositories cover our ad-blocking apps, filters, browser extensions, DNS solutions, VPN tools, developer utilities, and more. There are different platforms that offer such functionality, but the most popular one by far is GitHub, and all AdGuard projects are stored there. + +This article lists the most important repositories by category, summarizes the purpose of each one, and gives a simple breakdown of what users can do there. + +:::tip + +Pro tip: Creating an issue on GitHub is the most effective way to bring the attention of AdGuard developers to a problem. Just make sure to check that a similar issue doesn’t already exist and describe the problem in a comprehensive but concise way. If it does exist, you can upvote it. + +::: + +## What is Github and its repositories + +Very simply put, you can think of GitHub as sort of Google Docs for code, where multiple people can work on the same project, track changes, and see who made which updates. It provides a central, cloud-based place to store your code so it’s accessible from anywhere. It also has teamwork tools for reviewing changes, fixing issues, and merging everyone’s work smoothly. + +GitHub is widely used for open-source projects, letting anyone view the code, suggest improvements, and contribute. + +A repository (often called “repo” for short) is the most basic element of GitHub. It’s a place where you can store your code, your files, and each file’s revision history. Repositories can have multiple collaborators and can be either public or private. + +## What can you do in AdGuard’s repositories + +You can find links to key repositories below in this article or visit the [general AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all) for a full list. In most repos, you can: + +- **View README file** on the main page: it gives you an introduction to the product and its repo + ![README file \*border](https://cdn.adtidy.org/content/blog/github-repos/see-readme.png) + +- **Check existing bug reports or feature requests**, comment and upvote + ![Check issues \*border](https://cdn.adtidy.org/content/blog/github-repos/check-issues.png) + +- **Create issues** to report bugs or request features + ![Create issues \*border](https://cdn.adtidy.org/content/blog/github-repos/create-issue.png) + +- **Check releases** for different versions and their changelogs (and install an older version if needed) + ![Check releases \*border](https://cdn.adtidy.org/content/blog/github-repos/check-releases.png) + +- **Install any older or beta version** if needed + ![Download builds \*border](https://cdn.adtidy.org/content/blog/github-repos/download-releases.png) + +:::note + +If you are new to GitHub, you’ll need to create a GitHub account in order to create new issues and comment on the existing ones. + +::: + +In open-source repos advanced users can also: + +- **Browse code** to understand product logic, what technologies are used and how they are implemented +- **Fork and contribute** via pull requests + +Whether you’re a casual user, technical expert, or a developer, AdGuard welcomes all community participation across its GitHub repos. + +## Legal documents + +### [LegalDocs](https://github.com/AdguardTeam/LegalDocs) + +As part of our commitment to transparency, we host all legal documents — such as End-User License Agreements, Privacy Policies, and Terms and Conditions — on GitHub. Our _LegalDocs_ repo lets anyone check the full history of changes to these documents. + +## AdGuard Ad Blocker products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdguardForAndroid](https://github.com/AdguardTeam/AdguardForAndroid) + +Repository of AdGuard for Android — an app that provides system-wide ad blocking. + +### [AdguardForiOS](https://github.com/AdguardTeam/AdguardForiOS) + +Repository of AdGuard for iOS — Safari content blocker with DNS and custom filters. Users can also check open-source code. + +### [AdguardForWindows](https://github.com/AdguardTeam/AdguardForWindows) + +Repository of AdGuard for Windows. Non-open-source; GitHub used as an open bug tracker. + +### [AdguardForMac](https://github.com/AdguardTeam/AdguardForMac) + +Repository of AdGuard for Mac — macOS standalone content blocker. Bug tracker only. + +### [AdguardBrowserExtension](https://github.com/AdguardTeam/AdguardBrowserExtension) + +Repository of AdGuard Browser Extension — extension that provides ad blocking with enhanced privacy for Chrome, Firefox, Opera, Edge. + +### [AdguardForSafari](https://github.com/AdguardTeam/AdGuardForSafari) + +Repository of AdGuard for Safari — Safari ad blocking extension for Mac. Users can also check open-sourced code. + +### [AdGuardCLI](https://github.com/AdguardTeam/AdGuardCLI) + +Repository of AdGuard for Linux — a command‑line interface for managing ad blocking. + +## AdGuard VPN products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdGuardVPNForiOS](https://github.com/AdguardTeam/AdGuardVPNForiOS) + +Repository of AdGuard VPN for iOS. Serves as an open bug tracker. + +### [AdGuardVPNForAndroid](https://github.com/AdguardTeam/AdGuardVPNForAndroid) + +Repository of AdGuard VPN for Android. Serves as an open bug tracker. + +### [AdGuardVPNForWindows](https://github.com/AdguardTeam/AdGuardVPNForWindows) + +Repository of AdGuard VPN for Windows. Serves as an open bug tracker. + +### [AdGuardVPNForMac](https://github.com/AdguardTeam/AdGuardVPNForMac) + +Repository of AdGuard VPN for Mac — app designed for macOS. + +### [AdGuardVPNExtension](https://github.com/AdguardTeam/AdGuardVPNExtension) + +Repository of AdGuard VPN Browser Extension. + +### [AdGuardVPNCLI](https://github.com/AdguardTeam/AdGuardVPNCLI) + +Repository of AdGuard VPN for Linux — a command‑line interface for managing VPN connection. The repo acts as a bug tracker. + +## DNS-based products + +### [AdGuardDNS](https://github.com/AdguardTeam/AdGuardDNS) + +Open-source repository that is also used for tracking bugs and issues related to AdGuard DNS service. Users can: + +- View and report DNS issues +- Suggest improvements + +### [AdGuardHome](https://github.com/AdguardTeam/AdGuardHome) + +Repository of AdGuard Home — free network-wide software for blocking ads and trackers via DNS. Users can: + +- Check and file bug reports or feature requests +- Review or contribute to code +- Download and install releases + +## Documentation and Knowledge bases + +Knowledge bases are aimed to help users better understand and use AdGuard. They describe each AdGuard product in detail: from feature overviews and problem-solving guides to advanced setting manuals and API documentations. In the repositories users can: + +- Suggest corrections or edits to knowledge base articles +- Propose new articles +- Test or run the local version + +### [KnowledgeBase](https://github.com/AdguardTeam/KnowledgeBase) + +Central documentation for AdGuard Ad Blocker and the technologies related to it. + +### [KnowledgeBaseDNS](https://github.com/AdguardTeam/KnowledgeBaseDNS) + +Detailed feature overview, troubleshooting guides and documentation for AdGuard DNS (both Public and Private), AdGuard Home, and everything related to them. + +### [KnowledgeBaseVPN](https://github.com/AdguardTeam/KnowledgeBaseVPN) + +Detailed feature overview and troubleshooting guides for AdGuard VPN. + +### [KnowledgeBaseMail](https://github.com/AdguardTeam/KnowledgeBaseMail) + +Detailed feature overview and troubleshooting guides of AdGuard Mail. + +## Core libraries + +### [CoreLibs](https://github.com/AdguardTeam/CoreLibs) + +AdGuard’s cross-platform core filtering engine. Used in Android, Windows, and Mac products. Users can: + +- Explore filtering logic and DNS handling +- Report bugs and suggest features via Issues + +### [DNSLibs](https://github.com/AdguardTeam/DNSLibs) + +A DNS library used by CoreLibs and AdGuardHome. Users can: + +- Review and contribute to low-level DNS implementation +- Suggest optimizations + +### [VPNLibs](https://github.com/AdguardTeam/VPNLibs) + +Shared codebase used in AdGuard VPN products across platforms for AdGuard VPN protocol implementation. Users can: + +- Contribute to VPN stack behavior +- Report or view performance issues and bugs + +## Core ad blocking and filtering technologies + +### [AdguardFilters](https://github.com/AdguardTeam/AdguardFilters) + +Contains AdGuard’s core filter lists. Users can: + +- View and download filter lists +- Create issues to report false positives or suggest new rules +- Monitor updates to filter logic + +### [AdGuardSDNSFilter](https://github.com/AdguardTeam/AdGuardSDNSFilter) + +Repository of AdGuard DNS filter — the main DNS-level blocking list used in AdGuard DNS and DNS filtering features. Users can: + +- Inspect the current rule set +- Propose changes or additions + +### [AGLint](https://github.com/AdguardTeam/AGLint) + +A linter for adblock filter list syntax. Users can: + +- Install AGLint to check their projects for rule issues +- Contribute to lint rules + +### [Scriptlets](https://github.com/AdguardTeam/Scriptlets) + +JavaScript helpers used in filtering rules. Users can: + +- Explore available scriptlets +- Submit pull requests for new scriptlets + +### [tsurlfilter](https://github.com/AdguardTeam/tsurlfilter) + +TypeScript content blocker library for browser extensions. Users can: + +- Explore how filtering logic is implemented +- Contribute fixes and features + +## There’s more + +Above, we listed 27 main public AdGuard repositories out of 96 total. If you want to go down the rabbit hole, you can [find the rest on the AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse). + +We’ll be waiting for your feedback there! Stay safe online and offline. diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/general/how-to-install.md b/i18n/sv/docusaurus-plugin-content-docs/current/general/how-to-install.md index 106a29529a8..4ba78d7a094 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/general/how-to-install.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/general/how-to-install.md @@ -1,6 +1,6 @@ --- title: How to install AdGuard -sidebar_position: 9 +sidebar_position: 10 --- Depending on which AdGuard app or browser extension you want to install, follow one of these links to find the relevant article: diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md index 3953f47d26f..05642d350b0 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md @@ -43,6 +43,14 @@ Here you can choose which proxy AdGuard should use to download filter updates or ## Use SockFilter driver -Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. +Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. If this option is disabled, AdGuard will switch to the older WFP driver instead. -If this option is disabled, AdGuard will switch to the older WFP driver instead. +SockFilter was first introduced in v8.0 RC. It is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md index 251e49cf286..1ab588bb16c 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Because of this, TDI-based traffic visibility becomes increasingly unstable. In AdGuard already treats the TDI driver as deprecated, and its complete removal is planned as the product evolves. +## Permanent solution + +From v8.0 RC, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows-8/settings/app-settings/network-settings/). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Temporary solution Certain Windows registry changes can force the browser to stop using AppContainer, causing its processes to run in a non-sandboxed mode again. Network Service stops using the WSK stack and falls back to a network path that the TDI driver can see. AdGuard then regains the ability to filter browser traffic. @@ -123,7 +131,3 @@ You should see the following policies active: If available, click _Reload policies_. Done! - -## Permanent solution - -We’re planning to add support for the SockFilter driver in the upcoming versions. It will fix the issue by solving conflicts in the WFP stack. [More information](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index 5945618ea9c..f8074e9cfa1 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -17,23 +17,35 @@ In this module you can select the checkbox _Use AdGuard as an HTTP proxy_ to use At last, there is a section with proxy settings. There you can specify which proxy server AdGuard should use to update filters, get new versions, and so on. -### SockFilter and other network drivers +### Enable traffic filtering -In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. +Traffic filtering is the core mechanism that allows AdGuard to inspect and control the network traffic generated by applications on your computer. When it is enabled, AdGuard intercepts outgoing and incoming connections and checks them against its filtering rules. If a request matches a blocking rule, AdGuard can block it, modify it, or allow it depending on the configuration. In AdGuard for Windows, this interception is implemented through network drivers. -**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. +If HTTPS filtering is enabled, AdGuard performs a controlled local TLS interception: it decrypts the traffic using its local certificate, applies filtering rules, and then re-encrypts the traffic before sending it to the browser. The driver simply provides the system-level access needed for AdGuard to intercept these connections. -The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +#### SockFilter **SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. -Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: +SockFilter was first implemented in version 7.22.4, and it is still considered unstable — you may encounter bugs. Once fully tested and implemented, SockFilter has the potential to offer several advantages over other drivers: -- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. - **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. -- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. -When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. +#### WFP + +**WFP** (Windows Filtering Platform) is a Microsoft networking framework built into Windows that allows software to filter and monitor network packets at different layers of the system networking stack. AdGuard uses WFP to safely hook into the network flow of applications and apply filtering rules before the traffic reaches the browser or the Internet. [More information](https://learn.microsoft.com/en-us/windows/win32/fwp/windows-filtering-platform-architecture-overview). + +While it is a powerful driver, it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) and lower Internet speed for some users. + +#### TDI + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. ### AdGuard VPN diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index ab90a964b9f..5699b31b033 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -44,12 +44,8 @@ Before you start manually writing your own rules read our detailed [syntax guide Many websites gather information about their visitors, such as their IP addresses, browser and operating system details, screen resolution, and the webpage from which the user came or was redirected. Some websites use cookies to mark and identify your browser, save your personal settings and preferences. This allows them to “recognize” you on your next visit. Tracking protection safeguards your personal information from these data- and statistics-gathering systems. -![Tracking protection levels \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection1.png) - You can adjust the _Tracking Protection_ settings as needed. For example, you can prevent websites from receiving the search request that you used to find them on the Internet, automatically delete third- and first-party cookies, and disable location sharing in your browser, to prevent tracking of your whereabouts. -![Tracking protection custom features \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection2.png) - To learn everything about _Tracking protection_ and its many options, [read this article](/general/stealth-mode). ### Browsing security diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md index 62370bf3eb1..bec08d0c665 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Because of this, TDI-based traffic visibility becomes increasingly unstable. In AdGuard already treats the TDI driver as deprecated, and its complete removal is planned as the product evolves. +## Permanent solution + +From v7.22.4, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows/features/network/#sockfilter-and-other-network-drivers). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Temporary solution Certain Windows registry changes can force the browser to stop using AppContainer, causing its processes to run in a non-sandboxed mode again. Network Service stops using the WSK stack and falls back to a network path that the TDI driver can see. AdGuard then regains the ability to filter browser traffic. @@ -136,7 +144,3 @@ You should see the following policies active: If available, click _Reload policies_. Done! - -## Permanent solution - -We’re planning to add support for the SockFilter driver in the upcoming versions. It will fix the issue by solving conflicts in the WFP stack. [More information](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/general/github-repos.md b/i18n/ta/docusaurus-plugin-content-docs/current/general/github-repos.md new file mode 100644 index 00000000000..dfb164c44bc --- /dev/null +++ b/i18n/ta/docusaurus-plugin-content-docs/current/general/github-repos.md @@ -0,0 +1,238 @@ +--- +title: AdGuard’s GitHub repositories +sidebar_position: 9 +--- + +At AdGuard, our goal is to make the Internet safer, more comfortable, and more transparent. This commitment is reflected not only in our product features and strict privacy policies, but also in the fact that we keep our work as open as possible. That includes actively interacting with our community. + +This is why [all of our products have public repositories](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse) — online spaces where anybody can see what we are working on, report issues directly to AdGuard developers, and even contribute to our open-source projects. The repositories cover our ad-blocking apps, filters, browser extensions, DNS solutions, VPN tools, developer utilities, and more. There are different platforms that offer such functionality, but the most popular one by far is GitHub, and all AdGuard projects are stored there. + +This article lists the most important repositories by category, summarizes the purpose of each one, and gives a simple breakdown of what users can do there. + +:::tip + +Pro tip: Creating an issue on GitHub is the most effective way to bring the attention of AdGuard developers to a problem. Just make sure to check that a similar issue doesn’t already exist and describe the problem in a comprehensive but concise way. If it does exist, you can upvote it. + +::: + +## What is Github and its repositories + +Very simply put, you can think of GitHub as sort of Google Docs for code, where multiple people can work on the same project, track changes, and see who made which updates. It provides a central, cloud-based place to store your code so it’s accessible from anywhere. It also has teamwork tools for reviewing changes, fixing issues, and merging everyone’s work smoothly. + +GitHub is widely used for open-source projects, letting anyone view the code, suggest improvements, and contribute. + +A repository (often called “repo” for short) is the most basic element of GitHub. It’s a place where you can store your code, your files, and each file’s revision history. Repositories can have multiple collaborators and can be either public or private. + +## What can you do in AdGuard’s repositories + +You can find links to key repositories below in this article or visit the [general AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all) for a full list. In most repos, you can: + +- **View README file** on the main page: it gives you an introduction to the product and its repo + ![README file \*border](https://cdn.adtidy.org/content/blog/github-repos/see-readme.png) + +- **Check existing bug reports or feature requests**, comment and upvote + ![Check issues \*border](https://cdn.adtidy.org/content/blog/github-repos/check-issues.png) + +- **Create issues** to report bugs or request features + ![Create issues \*border](https://cdn.adtidy.org/content/blog/github-repos/create-issue.png) + +- **Check releases** for different versions and their changelogs (and install an older version if needed) + ![Check releases \*border](https://cdn.adtidy.org/content/blog/github-repos/check-releases.png) + +- **Install any older or beta version** if needed + ![Download builds \*border](https://cdn.adtidy.org/content/blog/github-repos/download-releases.png) + +:::note + +If you are new to GitHub, you’ll need to create a GitHub account in order to create new issues and comment on the existing ones. + +::: + +In open-source repos advanced users can also: + +- **Browse code** to understand product logic, what technologies are used and how they are implemented +- **Fork and contribute** via pull requests + +Whether you’re a casual user, technical expert, or a developer, AdGuard welcomes all community participation across its GitHub repos. + +## Legal documents + +### [LegalDocs](https://github.com/AdguardTeam/LegalDocs) + +As part of our commitment to transparency, we host all legal documents — such as End-User License Agreements, Privacy Policies, and Terms and Conditions — on GitHub. Our _LegalDocs_ repo lets anyone check the full history of changes to these documents. + +## AdGuard Ad Blocker products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdguardForAndroid](https://github.com/AdguardTeam/AdguardForAndroid) + +Repository of AdGuard for Android — an app that provides system-wide ad blocking. + +### [AdguardForiOS](https://github.com/AdguardTeam/AdguardForiOS) + +Repository of AdGuard for iOS — Safari content blocker with DNS and custom filters. Users can also check open-source code. + +### [AdguardForWindows](https://github.com/AdguardTeam/AdguardForWindows) + +Repository of AdGuard for Windows. Non-open-source; GitHub used as an open bug tracker. + +### [AdguardForMac](https://github.com/AdguardTeam/AdguardForMac) + +Repository of AdGuard for Mac — macOS standalone content blocker. Bug tracker only. + +### [AdguardBrowserExtension](https://github.com/AdguardTeam/AdguardBrowserExtension) + +Repository of AdGuard Browser Extension — extension that provides ad blocking with enhanced privacy for Chrome, Firefox, Opera, Edge. + +### [AdguardForSafari](https://github.com/AdguardTeam/AdGuardForSafari) + +Repository of AdGuard for Safari — Safari ad blocking extension for Mac. Users can also check open-sourced code. + +### [AdGuardCLI](https://github.com/AdguardTeam/AdGuardCLI) + +Repository of AdGuard for Linux — a command‑line interface for managing ad blocking. + +## AdGuard VPN products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdGuardVPNForiOS](https://github.com/AdguardTeam/AdGuardVPNForiOS) + +Repository of AdGuard VPN for iOS. Serves as an open bug tracker. + +### [AdGuardVPNForAndroid](https://github.com/AdguardTeam/AdGuardVPNForAndroid) + +Repository of AdGuard VPN for Android. Serves as an open bug tracker. + +### [AdGuardVPNForWindows](https://github.com/AdguardTeam/AdGuardVPNForWindows) + +Repository of AdGuard VPN for Windows. Serves as an open bug tracker. + +### [AdGuardVPNForMac](https://github.com/AdguardTeam/AdGuardVPNForMac) + +Repository of AdGuard VPN for Mac — app designed for macOS. + +### [AdGuardVPNExtension](https://github.com/AdguardTeam/AdGuardVPNExtension) + +Repository of AdGuard VPN Browser Extension. + +### [AdGuardVPNCLI](https://github.com/AdguardTeam/AdGuardVPNCLI) + +Repository of AdGuard VPN for Linux — a command‑line interface for managing VPN connection. The repo acts as a bug tracker. + +## DNS-based products + +### [AdGuardDNS](https://github.com/AdguardTeam/AdGuardDNS) + +Open-source repository that is also used for tracking bugs and issues related to AdGuard DNS service. Users can: + +- View and report DNS issues +- Suggest improvements + +### [AdGuardHome](https://github.com/AdguardTeam/AdGuardHome) + +Repository of AdGuard Home — free network-wide software for blocking ads and trackers via DNS. Users can: + +- Check and file bug reports or feature requests +- Review or contribute to code +- Download and install releases + +## Documentation and Knowledge bases + +Knowledge bases are aimed to help users better understand and use AdGuard. They describe each AdGuard product in detail: from feature overviews and problem-solving guides to advanced setting manuals and API documentations. In the repositories users can: + +- Suggest corrections or edits to knowledge base articles +- Propose new articles +- Test or run the local version + +### [KnowledgeBase](https://github.com/AdguardTeam/KnowledgeBase) + +Central documentation for AdGuard Ad Blocker and the technologies related to it. + +### [KnowledgeBaseDNS](https://github.com/AdguardTeam/KnowledgeBaseDNS) + +Detailed feature overview, troubleshooting guides and documentation for AdGuard DNS (both Public and Private), AdGuard Home, and everything related to them. + +### [KnowledgeBaseVPN](https://github.com/AdguardTeam/KnowledgeBaseVPN) + +Detailed feature overview and troubleshooting guides for AdGuard VPN. + +### [KnowledgeBaseMail](https://github.com/AdguardTeam/KnowledgeBaseMail) + +Detailed feature overview and troubleshooting guides of AdGuard Mail. + +## Core libraries + +### [CoreLibs](https://github.com/AdguardTeam/CoreLibs) + +AdGuard’s cross-platform core filtering engine. Used in Android, Windows, and Mac products. Users can: + +- Explore filtering logic and DNS handling +- Report bugs and suggest features via Issues + +### [DNSLibs](https://github.com/AdguardTeam/DNSLibs) + +A DNS library used by CoreLibs and AdGuardHome. Users can: + +- Review and contribute to low-level DNS implementation +- Suggest optimizations + +### [VPNLibs](https://github.com/AdguardTeam/VPNLibs) + +Shared codebase used in AdGuard VPN products across platforms for AdGuard VPN protocol implementation. Users can: + +- Contribute to VPN stack behavior +- Report or view performance issues and bugs + +## Core ad blocking and filtering technologies + +### [AdguardFilters](https://github.com/AdguardTeam/AdguardFilters) + +Contains AdGuard’s core filter lists. Users can: + +- View and download filter lists +- Create issues to report false positives or suggest new rules +- Monitor updates to filter logic + +### [AdGuardSDNSFilter](https://github.com/AdguardTeam/AdGuardSDNSFilter) + +Repository of AdGuard DNS filter — the main DNS-level blocking list used in AdGuard DNS and DNS filtering features. Users can: + +- Inspect the current rule set +- Propose changes or additions + +### [AGLint](https://github.com/AdguardTeam/AGLint) + +A linter for adblock filter list syntax. Users can: + +- Install AGLint to check their projects for rule issues +- Contribute to lint rules + +### [Scriptlets](https://github.com/AdguardTeam/Scriptlets) + +JavaScript helpers used in filtering rules. Users can: + +- Explore available scriptlets +- Submit pull requests for new scriptlets + +### [tsurlfilter](https://github.com/AdguardTeam/tsurlfilter) + +TypeScript content blocker library for browser extensions. Users can: + +- Explore how filtering logic is implemented +- Contribute fixes and features + +## There’s more + +Above, we listed 27 main public AdGuard repositories out of 96 total. If you want to go down the rabbit hole, you can [find the rest on the AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse). + +We’ll be waiting for your feedback there! Stay safe online and offline. diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/general/how-to-install.md b/i18n/ta/docusaurus-plugin-content-docs/current/general/how-to-install.md index 106a29529a8..4ba78d7a094 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/general/how-to-install.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/general/how-to-install.md @@ -1,6 +1,6 @@ --- title: How to install AdGuard -sidebar_position: 9 +sidebar_position: 10 --- Depending on which AdGuard app or browser extension you want to install, follow one of these links to find the relevant article: diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md index a01a297324a..84e267a2473 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md @@ -43,6 +43,14 @@ Here you can choose which proxy AdGuard should use to download filter updates or ## Use SockFilter driver -Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. +Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. If this option is disabled, AdGuard will switch to the older WFP driver instead. -If this option is disabled, AdGuard will switch to the older WFP driver instead. +SockFilter was first introduced in v8.0 RC. It is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md index 5aca7a4ad0c..802eacd51bb 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Bu sebeple, TDI tabanlı trafik görünürlüğü giderek daha istikrarsız hâl AdGuard already treats the TDI driver as deprecated, and its complete removal is planned as the product evolves. +## Permanent solution + +From v8.0 RC, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows-8/settings/app-settings/network-settings/). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Geçici çözüm Certain Windows registry changes can force the browser to stop using AppContainer, causing its processes to run in a non-sandboxed mode again. Network Service stops using the WSK stack and falls back to a network path that the TDI driver can see. AdGuard then regains the ability to filter browser traffic. @@ -123,7 +131,3 @@ You should see the following policies active: If available, click _Reload policies_. Tamamlandı! - -## Permanent solution - -We’re planning to add support for the SockFilter driver in the upcoming versions. It will fix the issue by solving conflicts in the WFP stack. [More information](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index d7168b75558..f04f81f8914 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -17,23 +17,35 @@ In this module you can select the checkbox _Use AdGuard as an HTTP proxy_ to use Son olarak, proxy ayarlarının bulunduğu bir bölüm vardır. Burada, filtreleri güncellemek, yeni sürümleri edinmek, vb. için AdGuard'ın hangi proxy sunucusunu kullanması gerektiğini belirleyebilirsiniz. -### SockFilter and other network drivers +### Enable traffic filtering -In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. +Traffic filtering is the core mechanism that allows AdGuard to inspect and control the network traffic generated by applications on your computer. When it is enabled, AdGuard intercepts outgoing and incoming connections and checks them against its filtering rules. If a request matches a blocking rule, AdGuard can block it, modify it, or allow it depending on the configuration. In AdGuard for Windows, this interception is implemented through network drivers. -**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. +If HTTPS filtering is enabled, AdGuard performs a controlled local TLS interception: it decrypts the traffic using its local certificate, applies filtering rules, and then re-encrypts the traffic before sending it to the browser. The driver simply provides the system-level access needed for AdGuard to intercept these connections. -The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +#### SockFilter **SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. -Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: +SockFilter was first implemented in version 7.22.4, and it is still considered unstable — you may encounter bugs. Once fully tested and implemented, SockFilter has the potential to offer several advantages over other drivers: -- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. - **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. -- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. -When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. +#### WFP + +**WFP** (Windows Filtering Platform) is a Microsoft networking framework built into Windows that allows software to filter and monitor network packets at different layers of the system networking stack. AdGuard uses WFP to safely hook into the network flow of applications and apply filtering rules before the traffic reaches the browser or the Internet. [More information](https://learn.microsoft.com/en-us/windows/win32/fwp/windows-filtering-platform-architecture-overview). + +While it is a powerful driver, it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) and lower Internet speed for some users. + +#### TDI + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. ### AdGuard VPN diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index c1fa9ff38a6..5c46c8bcfb5 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -44,12 +44,8 @@ Before you start manually writing your own rules read our detailed [syntax guide Many websites gather information about their visitors, such as their IP addresses, browser and operating system details, screen resolution, and the webpage from which the user came or was redirected. Some websites use cookies to mark and identify your browser, save your personal settings and preferences. This allows them to “recognize” you on your next visit. Tracking protection safeguards your personal information from these data- and statistics-gathering systems. -![Tracking protection levels \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection1.png) - _İzleme Koruması_ ayarlarını ihtiyacınıza göre düzenleyebilirsiniz. For example, you can prevent websites from receiving the search request that you used to find them on the Internet, automatically delete third- and first-party cookies, and disable location sharing in your browser, to prevent tracking of your whereabouts. -![İzleme koruması özel özellikler \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection2.png) - To learn everything about _Tracking protection_ and its many options, [read this article](/general/stealth-mode). ### Gezinti koruması diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md index 9f2d7334ca1..8b2b717bf46 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Bu sebeple, TDI tabanlı trafik görünürlüğü giderek daha istikrarsız hâl AdGuard already treats the TDI driver as deprecated, and its complete removal is planned as the product evolves. +## Permanent solution + +From v7.22.4, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows/features/network/#sockfilter-and-other-network-drivers). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Geçici çözüm Certain Windows registry changes can force the browser to stop using AppContainer, causing its processes to run in a non-sandboxed mode again. Network Service stops using the WSK stack and falls back to a network path that the TDI driver can see. AdGuard then regains the ability to filter browser traffic. @@ -136,7 +144,3 @@ You should see the following policies active: If available, click _Reload policies_. Tamamlandı! - -## Permanent solution - -We’re planning to add support for the SockFilter driver in the upcoming versions. It will fix the issue by solving conflicts in the WFP stack. [More information](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/general/github-repos.md b/i18n/tr/docusaurus-plugin-content-docs/current/general/github-repos.md new file mode 100644 index 00000000000..dfb164c44bc --- /dev/null +++ b/i18n/tr/docusaurus-plugin-content-docs/current/general/github-repos.md @@ -0,0 +1,238 @@ +--- +title: AdGuard’s GitHub repositories +sidebar_position: 9 +--- + +At AdGuard, our goal is to make the Internet safer, more comfortable, and more transparent. This commitment is reflected not only in our product features and strict privacy policies, but also in the fact that we keep our work as open as possible. That includes actively interacting with our community. + +This is why [all of our products have public repositories](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse) — online spaces where anybody can see what we are working on, report issues directly to AdGuard developers, and even contribute to our open-source projects. The repositories cover our ad-blocking apps, filters, browser extensions, DNS solutions, VPN tools, developer utilities, and more. There are different platforms that offer such functionality, but the most popular one by far is GitHub, and all AdGuard projects are stored there. + +This article lists the most important repositories by category, summarizes the purpose of each one, and gives a simple breakdown of what users can do there. + +:::tip + +Pro tip: Creating an issue on GitHub is the most effective way to bring the attention of AdGuard developers to a problem. Just make sure to check that a similar issue doesn’t already exist and describe the problem in a comprehensive but concise way. If it does exist, you can upvote it. + +::: + +## What is Github and its repositories + +Very simply put, you can think of GitHub as sort of Google Docs for code, where multiple people can work on the same project, track changes, and see who made which updates. It provides a central, cloud-based place to store your code so it’s accessible from anywhere. It also has teamwork tools for reviewing changes, fixing issues, and merging everyone’s work smoothly. + +GitHub is widely used for open-source projects, letting anyone view the code, suggest improvements, and contribute. + +A repository (often called “repo” for short) is the most basic element of GitHub. It’s a place where you can store your code, your files, and each file’s revision history. Repositories can have multiple collaborators and can be either public or private. + +## What can you do in AdGuard’s repositories + +You can find links to key repositories below in this article or visit the [general AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all) for a full list. In most repos, you can: + +- **View README file** on the main page: it gives you an introduction to the product and its repo + ![README file \*border](https://cdn.adtidy.org/content/blog/github-repos/see-readme.png) + +- **Check existing bug reports or feature requests**, comment and upvote + ![Check issues \*border](https://cdn.adtidy.org/content/blog/github-repos/check-issues.png) + +- **Create issues** to report bugs or request features + ![Create issues \*border](https://cdn.adtidy.org/content/blog/github-repos/create-issue.png) + +- **Check releases** for different versions and their changelogs (and install an older version if needed) + ![Check releases \*border](https://cdn.adtidy.org/content/blog/github-repos/check-releases.png) + +- **Install any older or beta version** if needed + ![Download builds \*border](https://cdn.adtidy.org/content/blog/github-repos/download-releases.png) + +:::note + +If you are new to GitHub, you’ll need to create a GitHub account in order to create new issues and comment on the existing ones. + +::: + +In open-source repos advanced users can also: + +- **Browse code** to understand product logic, what technologies are used and how they are implemented +- **Fork and contribute** via pull requests + +Whether you’re a casual user, technical expert, or a developer, AdGuard welcomes all community participation across its GitHub repos. + +## Legal documents + +### [LegalDocs](https://github.com/AdguardTeam/LegalDocs) + +As part of our commitment to transparency, we host all legal documents — such as End-User License Agreements, Privacy Policies, and Terms and Conditions — on GitHub. Our _LegalDocs_ repo lets anyone check the full history of changes to these documents. + +## AdGuard Ad Blocker products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdguardForAndroid](https://github.com/AdguardTeam/AdguardForAndroid) + +Repository of AdGuard for Android — an app that provides system-wide ad blocking. + +### [AdguardForiOS](https://github.com/AdguardTeam/AdguardForiOS) + +Repository of AdGuard for iOS — Safari content blocker with DNS and custom filters. Users can also check open-source code. + +### [AdguardForWindows](https://github.com/AdguardTeam/AdguardForWindows) + +Repository of AdGuard for Windows. Non-open-source; GitHub used as an open bug tracker. + +### [AdguardForMac](https://github.com/AdguardTeam/AdguardForMac) + +Repository of AdGuard for Mac — macOS standalone content blocker. Bug tracker only. + +### [AdguardBrowserExtension](https://github.com/AdguardTeam/AdguardBrowserExtension) + +Repository of AdGuard Browser Extension — extension that provides ad blocking with enhanced privacy for Chrome, Firefox, Opera, Edge. + +### [AdguardForSafari](https://github.com/AdguardTeam/AdGuardForSafari) + +Repository of AdGuard for Safari — Safari ad blocking extension for Mac. Users can also check open-sourced code. + +### [AdGuardCLI](https://github.com/AdguardTeam/AdGuardCLI) + +Repository of AdGuard for Linux — a command‑line interface for managing ad blocking. + +## AdGuard VPN products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdGuardVPNForiOS](https://github.com/AdguardTeam/AdGuardVPNForiOS) + +Repository of AdGuard VPN for iOS. Serves as an open bug tracker. + +### [AdGuardVPNForAndroid](https://github.com/AdguardTeam/AdGuardVPNForAndroid) + +Repository of AdGuard VPN for Android. Serves as an open bug tracker. + +### [AdGuardVPNForWindows](https://github.com/AdguardTeam/AdGuardVPNForWindows) + +Repository of AdGuard VPN for Windows. Serves as an open bug tracker. + +### [AdGuardVPNForMac](https://github.com/AdguardTeam/AdGuardVPNForMac) + +Repository of AdGuard VPN for Mac — app designed for macOS. + +### [AdGuardVPNExtension](https://github.com/AdguardTeam/AdGuardVPNExtension) + +Repository of AdGuard VPN Browser Extension. + +### [AdGuardVPNCLI](https://github.com/AdguardTeam/AdGuardVPNCLI) + +Repository of AdGuard VPN for Linux — a command‑line interface for managing VPN connection. The repo acts as a bug tracker. + +## DNS-based products + +### [AdGuardDNS](https://github.com/AdguardTeam/AdGuardDNS) + +Open-source repository that is also used for tracking bugs and issues related to AdGuard DNS service. Users can: + +- View and report DNS issues +- Suggest improvements + +### [AdGuardHome](https://github.com/AdguardTeam/AdGuardHome) + +Repository of AdGuard Home — free network-wide software for blocking ads and trackers via DNS. Users can: + +- Check and file bug reports or feature requests +- Review or contribute to code +- Download and install releases + +## Documentation and Knowledge bases + +Knowledge bases are aimed to help users better understand and use AdGuard. They describe each AdGuard product in detail: from feature overviews and problem-solving guides to advanced setting manuals and API documentations. In the repositories users can: + +- Suggest corrections or edits to knowledge base articles +- Propose new articles +- Test or run the local version + +### [KnowledgeBase](https://github.com/AdguardTeam/KnowledgeBase) + +Central documentation for AdGuard Ad Blocker and the technologies related to it. + +### [KnowledgeBaseDNS](https://github.com/AdguardTeam/KnowledgeBaseDNS) + +Detailed feature overview, troubleshooting guides and documentation for AdGuard DNS (both Public and Private), AdGuard Home, and everything related to them. + +### [KnowledgeBaseVPN](https://github.com/AdguardTeam/KnowledgeBaseVPN) + +Detailed feature overview and troubleshooting guides for AdGuard VPN. + +### [KnowledgeBaseMail](https://github.com/AdguardTeam/KnowledgeBaseMail) + +Detailed feature overview and troubleshooting guides of AdGuard Mail. + +## Core libraries + +### [CoreLibs](https://github.com/AdguardTeam/CoreLibs) + +AdGuard’s cross-platform core filtering engine. Used in Android, Windows, and Mac products. Users can: + +- Explore filtering logic and DNS handling +- Report bugs and suggest features via Issues + +### [DNSLibs](https://github.com/AdguardTeam/DNSLibs) + +A DNS library used by CoreLibs and AdGuardHome. Users can: + +- Review and contribute to low-level DNS implementation +- Suggest optimizations + +### [VPNLibs](https://github.com/AdguardTeam/VPNLibs) + +Shared codebase used in AdGuard VPN products across platforms for AdGuard VPN protocol implementation. Users can: + +- Contribute to VPN stack behavior +- Report or view performance issues and bugs + +## Core ad blocking and filtering technologies + +### [AdguardFilters](https://github.com/AdguardTeam/AdguardFilters) + +Contains AdGuard’s core filter lists. Users can: + +- View and download filter lists +- Create issues to report false positives or suggest new rules +- Monitor updates to filter logic + +### [AdGuardSDNSFilter](https://github.com/AdguardTeam/AdGuardSDNSFilter) + +Repository of AdGuard DNS filter — the main DNS-level blocking list used in AdGuard DNS and DNS filtering features. Users can: + +- Inspect the current rule set +- Propose changes or additions + +### [AGLint](https://github.com/AdguardTeam/AGLint) + +A linter for adblock filter list syntax. Users can: + +- Install AGLint to check their projects for rule issues +- Contribute to lint rules + +### [Scriptlets](https://github.com/AdguardTeam/Scriptlets) + +JavaScript helpers used in filtering rules. Users can: + +- Explore available scriptlets +- Submit pull requests for new scriptlets + +### [tsurlfilter](https://github.com/AdguardTeam/tsurlfilter) + +TypeScript content blocker library for browser extensions. Users can: + +- Explore how filtering logic is implemented +- Contribute fixes and features + +## There’s more + +Above, we listed 27 main public AdGuard repositories out of 96 total. If you want to go down the rabbit hole, you can [find the rest on the AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse). + +We’ll be waiting for your feedback there! Stay safe online and offline. diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/general/how-to-install.md b/i18n/tr/docusaurus-plugin-content-docs/current/general/how-to-install.md index 2a54efde143..26ff4e18315 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/general/how-to-install.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/general/how-to-install.md @@ -1,6 +1,6 @@ --- title: How to install AdGuard -sidebar_position: 9 +sidebar_position: 10 --- Depending on which AdGuard app or browser extension you want to install, follow one of these links to find the relevant article: diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md index 3953f47d26f..05642d350b0 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md @@ -43,6 +43,14 @@ Here you can choose which proxy AdGuard should use to download filter updates or ## Use SockFilter driver -Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. +Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. If this option is disabled, AdGuard will switch to the older WFP driver instead. -If this option is disabled, AdGuard will switch to the older WFP driver instead. +SockFilter was first introduced in v8.0 RC. It is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md index 251e49cf286..1ab588bb16c 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Because of this, TDI-based traffic visibility becomes increasingly unstable. In AdGuard already treats the TDI driver as deprecated, and its complete removal is planned as the product evolves. +## Permanent solution + +From v8.0 RC, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows-8/settings/app-settings/network-settings/). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Temporary solution Certain Windows registry changes can force the browser to stop using AppContainer, causing its processes to run in a non-sandboxed mode again. Network Service stops using the WSK stack and falls back to a network path that the TDI driver can see. AdGuard then regains the ability to filter browser traffic. @@ -123,7 +131,3 @@ You should see the following policies active: If available, click _Reload policies_. Done! - -## Permanent solution - -We’re planning to add support for the SockFilter driver in the upcoming versions. It will fix the issue by solving conflicts in the WFP stack. [More information](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index 5945618ea9c..f8074e9cfa1 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -17,23 +17,35 @@ In this module you can select the checkbox _Use AdGuard as an HTTP proxy_ to use At last, there is a section with proxy settings. There you can specify which proxy server AdGuard should use to update filters, get new versions, and so on. -### SockFilter and other network drivers +### Enable traffic filtering -In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. +Traffic filtering is the core mechanism that allows AdGuard to inspect and control the network traffic generated by applications on your computer. When it is enabled, AdGuard intercepts outgoing and incoming connections and checks them against its filtering rules. If a request matches a blocking rule, AdGuard can block it, modify it, or allow it depending on the configuration. In AdGuard for Windows, this interception is implemented through network drivers. -**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. +If HTTPS filtering is enabled, AdGuard performs a controlled local TLS interception: it decrypts the traffic using its local certificate, applies filtering rules, and then re-encrypts the traffic before sending it to the browser. The driver simply provides the system-level access needed for AdGuard to intercept these connections. -The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +#### SockFilter **SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. -Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: +SockFilter was first implemented in version 7.22.4, and it is still considered unstable — you may encounter bugs. Once fully tested and implemented, SockFilter has the potential to offer several advantages over other drivers: -- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. - **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. -- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. -When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. +#### WFP + +**WFP** (Windows Filtering Platform) is a Microsoft networking framework built into Windows that allows software to filter and monitor network packets at different layers of the system networking stack. AdGuard uses WFP to safely hook into the network flow of applications and apply filtering rules before the traffic reaches the browser or the Internet. [More information](https://learn.microsoft.com/en-us/windows/win32/fwp/windows-filtering-platform-architecture-overview). + +While it is a powerful driver, it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) and lower Internet speed for some users. + +#### TDI + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. ### AdGuard VPN diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index ab90a964b9f..5699b31b033 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -44,12 +44,8 @@ Before you start manually writing your own rules read our detailed [syntax guide Many websites gather information about their visitors, such as their IP addresses, browser and operating system details, screen resolution, and the webpage from which the user came or was redirected. Some websites use cookies to mark and identify your browser, save your personal settings and preferences. This allows them to “recognize” you on your next visit. Tracking protection safeguards your personal information from these data- and statistics-gathering systems. -![Tracking protection levels \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection1.png) - You can adjust the _Tracking Protection_ settings as needed. For example, you can prevent websites from receiving the search request that you used to find them on the Internet, automatically delete third- and first-party cookies, and disable location sharing in your browser, to prevent tracking of your whereabouts. -![Tracking protection custom features \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection2.png) - To learn everything about _Tracking protection_ and its many options, [read this article](/general/stealth-mode). ### Browsing security diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md index 62370bf3eb1..bec08d0c665 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Because of this, TDI-based traffic visibility becomes increasingly unstable. In AdGuard already treats the TDI driver as deprecated, and its complete removal is planned as the product evolves. +## Permanent solution + +From v7.22.4, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows/features/network/#sockfilter-and-other-network-drivers). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Temporary solution Certain Windows registry changes can force the browser to stop using AppContainer, causing its processes to run in a non-sandboxed mode again. Network Service stops using the WSK stack and falls back to a network path that the TDI driver can see. AdGuard then regains the ability to filter browser traffic. @@ -136,7 +144,3 @@ You should see the following policies active: If available, click _Reload policies_. Done! - -## Permanent solution - -We’re planning to add support for the SockFilter driver in the upcoming versions. It will fix the issue by solving conflicts in the WFP stack. [More information](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/general/github-repos.md b/i18n/uk/docusaurus-plugin-content-docs/current/general/github-repos.md new file mode 100644 index 00000000000..dfb164c44bc --- /dev/null +++ b/i18n/uk/docusaurus-plugin-content-docs/current/general/github-repos.md @@ -0,0 +1,238 @@ +--- +title: AdGuard’s GitHub repositories +sidebar_position: 9 +--- + +At AdGuard, our goal is to make the Internet safer, more comfortable, and more transparent. This commitment is reflected not only in our product features and strict privacy policies, but also in the fact that we keep our work as open as possible. That includes actively interacting with our community. + +This is why [all of our products have public repositories](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse) — online spaces where anybody can see what we are working on, report issues directly to AdGuard developers, and even contribute to our open-source projects. The repositories cover our ad-blocking apps, filters, browser extensions, DNS solutions, VPN tools, developer utilities, and more. There are different platforms that offer such functionality, but the most popular one by far is GitHub, and all AdGuard projects are stored there. + +This article lists the most important repositories by category, summarizes the purpose of each one, and gives a simple breakdown of what users can do there. + +:::tip + +Pro tip: Creating an issue on GitHub is the most effective way to bring the attention of AdGuard developers to a problem. Just make sure to check that a similar issue doesn’t already exist and describe the problem in a comprehensive but concise way. If it does exist, you can upvote it. + +::: + +## What is Github and its repositories + +Very simply put, you can think of GitHub as sort of Google Docs for code, where multiple people can work on the same project, track changes, and see who made which updates. It provides a central, cloud-based place to store your code so it’s accessible from anywhere. It also has teamwork tools for reviewing changes, fixing issues, and merging everyone’s work smoothly. + +GitHub is widely used for open-source projects, letting anyone view the code, suggest improvements, and contribute. + +A repository (often called “repo” for short) is the most basic element of GitHub. It’s a place where you can store your code, your files, and each file’s revision history. Repositories can have multiple collaborators and can be either public or private. + +## What can you do in AdGuard’s repositories + +You can find links to key repositories below in this article or visit the [general AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all) for a full list. In most repos, you can: + +- **View README file** on the main page: it gives you an introduction to the product and its repo + ![README file \*border](https://cdn.adtidy.org/content/blog/github-repos/see-readme.png) + +- **Check existing bug reports or feature requests**, comment and upvote + ![Check issues \*border](https://cdn.adtidy.org/content/blog/github-repos/check-issues.png) + +- **Create issues** to report bugs or request features + ![Create issues \*border](https://cdn.adtidy.org/content/blog/github-repos/create-issue.png) + +- **Check releases** for different versions and their changelogs (and install an older version if needed) + ![Check releases \*border](https://cdn.adtidy.org/content/blog/github-repos/check-releases.png) + +- **Install any older or beta version** if needed + ![Download builds \*border](https://cdn.adtidy.org/content/blog/github-repos/download-releases.png) + +:::note + +If you are new to GitHub, you’ll need to create a GitHub account in order to create new issues and comment on the existing ones. + +::: + +In open-source repos advanced users can also: + +- **Browse code** to understand product logic, what technologies are used and how they are implemented +- **Fork and contribute** via pull requests + +Whether you’re a casual user, technical expert, or a developer, AdGuard welcomes all community participation across its GitHub repos. + +## Legal documents + +### [LegalDocs](https://github.com/AdguardTeam/LegalDocs) + +As part of our commitment to transparency, we host all legal documents — such as End-User License Agreements, Privacy Policies, and Terms and Conditions — on GitHub. Our _LegalDocs_ repo lets anyone check the full history of changes to these documents. + +## AdGuard Ad Blocker products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdguardForAndroid](https://github.com/AdguardTeam/AdguardForAndroid) + +Repository of AdGuard for Android — an app that provides system-wide ad blocking. + +### [AdguardForiOS](https://github.com/AdguardTeam/AdguardForiOS) + +Repository of AdGuard for iOS — Safari content blocker with DNS and custom filters. Users can also check open-source code. + +### [AdguardForWindows](https://github.com/AdguardTeam/AdguardForWindows) + +Repository of AdGuard for Windows. Non-open-source; GitHub used as an open bug tracker. + +### [AdguardForMac](https://github.com/AdguardTeam/AdguardForMac) + +Repository of AdGuard for Mac — macOS standalone content blocker. Bug tracker only. + +### [AdguardBrowserExtension](https://github.com/AdguardTeam/AdguardBrowserExtension) + +Repository of AdGuard Browser Extension — extension that provides ad blocking with enhanced privacy for Chrome, Firefox, Opera, Edge. + +### [AdguardForSafari](https://github.com/AdguardTeam/AdGuardForSafari) + +Repository of AdGuard for Safari — Safari ad blocking extension for Mac. Users can also check open-sourced code. + +### [AdGuardCLI](https://github.com/AdguardTeam/AdGuardCLI) + +Repository of AdGuard for Linux — a command‑line interface for managing ad blocking. + +## AdGuard VPN products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdGuardVPNForiOS](https://github.com/AdguardTeam/AdGuardVPNForiOS) + +Repository of AdGuard VPN for iOS. Serves as an open bug tracker. + +### [AdGuardVPNForAndroid](https://github.com/AdguardTeam/AdGuardVPNForAndroid) + +Repository of AdGuard VPN for Android. Serves as an open bug tracker. + +### [AdGuardVPNForWindows](https://github.com/AdguardTeam/AdGuardVPNForWindows) + +Repository of AdGuard VPN for Windows. Serves as an open bug tracker. + +### [AdGuardVPNForMac](https://github.com/AdguardTeam/AdGuardVPNForMac) + +Repository of AdGuard VPN for Mac — app designed for macOS. + +### [AdGuardVPNExtension](https://github.com/AdguardTeam/AdGuardVPNExtension) + +Repository of AdGuard VPN Browser Extension. + +### [AdGuardVPNCLI](https://github.com/AdguardTeam/AdGuardVPNCLI) + +Repository of AdGuard VPN for Linux — a command‑line interface for managing VPN connection. The repo acts as a bug tracker. + +## DNS-based products + +### [AdGuardDNS](https://github.com/AdguardTeam/AdGuardDNS) + +Open-source repository that is also used for tracking bugs and issues related to AdGuard DNS service. Users can: + +- View and report DNS issues +- Suggest improvements + +### [AdGuardHome](https://github.com/AdguardTeam/AdGuardHome) + +Repository of AdGuard Home — free network-wide software for blocking ads and trackers via DNS. Users can: + +- Check and file bug reports or feature requests +- Review or contribute to code +- Download and install releases + +## Documentation and Knowledge bases + +Knowledge bases are aimed to help users better understand and use AdGuard. They describe each AdGuard product in detail: from feature overviews and problem-solving guides to advanced setting manuals and API documentations. In the repositories users can: + +- Suggest corrections or edits to knowledge base articles +- Propose new articles +- Test or run the local version + +### [KnowledgeBase](https://github.com/AdguardTeam/KnowledgeBase) + +Central documentation for AdGuard Ad Blocker and the technologies related to it. + +### [KnowledgeBaseDNS](https://github.com/AdguardTeam/KnowledgeBaseDNS) + +Detailed feature overview, troubleshooting guides and documentation for AdGuard DNS (both Public and Private), AdGuard Home, and everything related to them. + +### [KnowledgeBaseVPN](https://github.com/AdguardTeam/KnowledgeBaseVPN) + +Detailed feature overview and troubleshooting guides for AdGuard VPN. + +### [KnowledgeBaseMail](https://github.com/AdguardTeam/KnowledgeBaseMail) + +Detailed feature overview and troubleshooting guides of AdGuard Mail. + +## Core libraries + +### [CoreLibs](https://github.com/AdguardTeam/CoreLibs) + +AdGuard’s cross-platform core filtering engine. Used in Android, Windows, and Mac products. Users can: + +- Explore filtering logic and DNS handling +- Report bugs and suggest features via Issues + +### [DNSLibs](https://github.com/AdguardTeam/DNSLibs) + +A DNS library used by CoreLibs and AdGuardHome. Users can: + +- Review and contribute to low-level DNS implementation +- Suggest optimizations + +### [VPNLibs](https://github.com/AdguardTeam/VPNLibs) + +Shared codebase used in AdGuard VPN products across platforms for AdGuard VPN protocol implementation. Users can: + +- Contribute to VPN stack behavior +- Report or view performance issues and bugs + +## Core ad blocking and filtering technologies + +### [AdguardFilters](https://github.com/AdguardTeam/AdguardFilters) + +Contains AdGuard’s core filter lists. Users can: + +- View and download filter lists +- Create issues to report false positives or suggest new rules +- Monitor updates to filter logic + +### [AdGuardSDNSFilter](https://github.com/AdguardTeam/AdGuardSDNSFilter) + +Repository of AdGuard DNS filter — the main DNS-level blocking list used in AdGuard DNS and DNS filtering features. Users can: + +- Inspect the current rule set +- Propose changes or additions + +### [AGLint](https://github.com/AdguardTeam/AGLint) + +A linter for adblock filter list syntax. Users can: + +- Install AGLint to check their projects for rule issues +- Contribute to lint rules + +### [Scriptlets](https://github.com/AdguardTeam/Scriptlets) + +JavaScript helpers used in filtering rules. Users can: + +- Explore available scriptlets +- Submit pull requests for new scriptlets + +### [tsurlfilter](https://github.com/AdguardTeam/tsurlfilter) + +TypeScript content blocker library for browser extensions. Users can: + +- Explore how filtering logic is implemented +- Contribute fixes and features + +## There’s more + +Above, we listed 27 main public AdGuard repositories out of 96 total. If you want to go down the rabbit hole, you can [find the rest on the AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse). + +We’ll be waiting for your feedback there! Stay safe online and offline. diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/general/how-to-install.md b/i18n/uk/docusaurus-plugin-content-docs/current/general/how-to-install.md index 106a29529a8..4ba78d7a094 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/general/how-to-install.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/general/how-to-install.md @@ -1,6 +1,6 @@ --- title: How to install AdGuard -sidebar_position: 9 +sidebar_position: 10 --- Depending on which AdGuard app or browser extension you want to install, follow one of these links to find the relevant article: diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md index 3953f47d26f..05642d350b0 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md @@ -43,6 +43,14 @@ Here you can choose which proxy AdGuard should use to download filter updates or ## Use SockFilter driver -Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. +Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. If this option is disabled, AdGuard will switch to the older WFP driver instead. -If this option is disabled, AdGuard will switch to the older WFP driver instead. +SockFilter was first introduced in v8.0 RC. It is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md index 251e49cf286..1ab588bb16c 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Because of this, TDI-based traffic visibility becomes increasingly unstable. In AdGuard already treats the TDI driver as deprecated, and its complete removal is planned as the product evolves. +## Permanent solution + +From v8.0 RC, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows-8/settings/app-settings/network-settings/). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Temporary solution Certain Windows registry changes can force the browser to stop using AppContainer, causing its processes to run in a non-sandboxed mode again. Network Service stops using the WSK stack and falls back to a network path that the TDI driver can see. AdGuard then regains the ability to filter browser traffic. @@ -123,7 +131,3 @@ You should see the following policies active: If available, click _Reload policies_. Done! - -## Permanent solution - -We’re planning to add support for the SockFilter driver in the upcoming versions. It will fix the issue by solving conflicts in the WFP stack. [More information](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index 5945618ea9c..f8074e9cfa1 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -17,23 +17,35 @@ In this module you can select the checkbox _Use AdGuard as an HTTP proxy_ to use At last, there is a section with proxy settings. There you can specify which proxy server AdGuard should use to update filters, get new versions, and so on. -### SockFilter and other network drivers +### Enable traffic filtering -In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. +Traffic filtering is the core mechanism that allows AdGuard to inspect and control the network traffic generated by applications on your computer. When it is enabled, AdGuard intercepts outgoing and incoming connections and checks them against its filtering rules. If a request matches a blocking rule, AdGuard can block it, modify it, or allow it depending on the configuration. In AdGuard for Windows, this interception is implemented through network drivers. -**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. +If HTTPS filtering is enabled, AdGuard performs a controlled local TLS interception: it decrypts the traffic using its local certificate, applies filtering rules, and then re-encrypts the traffic before sending it to the browser. The driver simply provides the system-level access needed for AdGuard to intercept these connections. -The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +#### SockFilter **SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. -Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: +SockFilter was first implemented in version 7.22.4, and it is still considered unstable — you may encounter bugs. Once fully tested and implemented, SockFilter has the potential to offer several advantages over other drivers: -- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. - **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. -- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. -When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. +#### WFP + +**WFP** (Windows Filtering Platform) is a Microsoft networking framework built into Windows that allows software to filter and monitor network packets at different layers of the system networking stack. AdGuard uses WFP to safely hook into the network flow of applications and apply filtering rules before the traffic reaches the browser or the Internet. [More information](https://learn.microsoft.com/en-us/windows/win32/fwp/windows-filtering-platform-architecture-overview). + +While it is a powerful driver, it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) and lower Internet speed for some users. + +#### TDI + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. ### AdGuard VPN diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index ab90a964b9f..5699b31b033 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -44,12 +44,8 @@ Before you start manually writing your own rules read our detailed [syntax guide Many websites gather information about their visitors, such as their IP addresses, browser and operating system details, screen resolution, and the webpage from which the user came or was redirected. Some websites use cookies to mark and identify your browser, save your personal settings and preferences. This allows them to “recognize” you on your next visit. Tracking protection safeguards your personal information from these data- and statistics-gathering systems. -![Tracking protection levels \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection1.png) - You can adjust the _Tracking Protection_ settings as needed. For example, you can prevent websites from receiving the search request that you used to find them on the Internet, automatically delete third- and first-party cookies, and disable location sharing in your browser, to prevent tracking of your whereabouts. -![Tracking protection custom features \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection2.png) - To learn everything about _Tracking protection_ and its many options, [read this article](/general/stealth-mode). ### Browsing security diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md index 62370bf3eb1..bec08d0c665 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Because of this, TDI-based traffic visibility becomes increasingly unstable. In AdGuard already treats the TDI driver as deprecated, and its complete removal is planned as the product evolves. +## Permanent solution + +From v7.22.4, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows/features/network/#sockfilter-and-other-network-drivers). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Temporary solution Certain Windows registry changes can force the browser to stop using AppContainer, causing its processes to run in a non-sandboxed mode again. Network Service stops using the WSK stack and falls back to a network path that the TDI driver can see. AdGuard then regains the ability to filter browser traffic. @@ -136,7 +144,3 @@ You should see the following policies active: If available, click _Reload policies_. Done! - -## Permanent solution - -We’re planning to add support for the SockFilter driver in the upcoming versions. It will fix the issue by solving conflicts in the WFP stack. [More information](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/general/github-repos.md b/i18n/vi/docusaurus-plugin-content-docs/current/general/github-repos.md new file mode 100644 index 00000000000..dfb164c44bc --- /dev/null +++ b/i18n/vi/docusaurus-plugin-content-docs/current/general/github-repos.md @@ -0,0 +1,238 @@ +--- +title: AdGuard’s GitHub repositories +sidebar_position: 9 +--- + +At AdGuard, our goal is to make the Internet safer, more comfortable, and more transparent. This commitment is reflected not only in our product features and strict privacy policies, but also in the fact that we keep our work as open as possible. That includes actively interacting with our community. + +This is why [all of our products have public repositories](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse) — online spaces where anybody can see what we are working on, report issues directly to AdGuard developers, and even contribute to our open-source projects. The repositories cover our ad-blocking apps, filters, browser extensions, DNS solutions, VPN tools, developer utilities, and more. There are different platforms that offer such functionality, but the most popular one by far is GitHub, and all AdGuard projects are stored there. + +This article lists the most important repositories by category, summarizes the purpose of each one, and gives a simple breakdown of what users can do there. + +:::tip + +Pro tip: Creating an issue on GitHub is the most effective way to bring the attention of AdGuard developers to a problem. Just make sure to check that a similar issue doesn’t already exist and describe the problem in a comprehensive but concise way. If it does exist, you can upvote it. + +::: + +## What is Github and its repositories + +Very simply put, you can think of GitHub as sort of Google Docs for code, where multiple people can work on the same project, track changes, and see who made which updates. It provides a central, cloud-based place to store your code so it’s accessible from anywhere. It also has teamwork tools for reviewing changes, fixing issues, and merging everyone’s work smoothly. + +GitHub is widely used for open-source projects, letting anyone view the code, suggest improvements, and contribute. + +A repository (often called “repo” for short) is the most basic element of GitHub. It’s a place where you can store your code, your files, and each file’s revision history. Repositories can have multiple collaborators and can be either public or private. + +## What can you do in AdGuard’s repositories + +You can find links to key repositories below in this article or visit the [general AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all) for a full list. In most repos, you can: + +- **View README file** on the main page: it gives you an introduction to the product and its repo + ![README file \*border](https://cdn.adtidy.org/content/blog/github-repos/see-readme.png) + +- **Check existing bug reports or feature requests**, comment and upvote + ![Check issues \*border](https://cdn.adtidy.org/content/blog/github-repos/check-issues.png) + +- **Create issues** to report bugs or request features + ![Create issues \*border](https://cdn.adtidy.org/content/blog/github-repos/create-issue.png) + +- **Check releases** for different versions and their changelogs (and install an older version if needed) + ![Check releases \*border](https://cdn.adtidy.org/content/blog/github-repos/check-releases.png) + +- **Install any older or beta version** if needed + ![Download builds \*border](https://cdn.adtidy.org/content/blog/github-repos/download-releases.png) + +:::note + +If you are new to GitHub, you’ll need to create a GitHub account in order to create new issues and comment on the existing ones. + +::: + +In open-source repos advanced users can also: + +- **Browse code** to understand product logic, what technologies are used and how they are implemented +- **Fork and contribute** via pull requests + +Whether you’re a casual user, technical expert, or a developer, AdGuard welcomes all community participation across its GitHub repos. + +## Legal documents + +### [LegalDocs](https://github.com/AdguardTeam/LegalDocs) + +As part of our commitment to transparency, we host all legal documents — such as End-User License Agreements, Privacy Policies, and Terms and Conditions — on GitHub. Our _LegalDocs_ repo lets anyone check the full history of changes to these documents. + +## AdGuard Ad Blocker products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdguardForAndroid](https://github.com/AdguardTeam/AdguardForAndroid) + +Repository of AdGuard for Android — an app that provides system-wide ad blocking. + +### [AdguardForiOS](https://github.com/AdguardTeam/AdguardForiOS) + +Repository of AdGuard for iOS — Safari content blocker with DNS and custom filters. Users can also check open-source code. + +### [AdguardForWindows](https://github.com/AdguardTeam/AdguardForWindows) + +Repository of AdGuard for Windows. Non-open-source; GitHub used as an open bug tracker. + +### [AdguardForMac](https://github.com/AdguardTeam/AdguardForMac) + +Repository of AdGuard for Mac — macOS standalone content blocker. Bug tracker only. + +### [AdguardBrowserExtension](https://github.com/AdguardTeam/AdguardBrowserExtension) + +Repository of AdGuard Browser Extension — extension that provides ad blocking with enhanced privacy for Chrome, Firefox, Opera, Edge. + +### [AdguardForSafari](https://github.com/AdguardTeam/AdGuardForSafari) + +Repository of AdGuard for Safari — Safari ad blocking extension for Mac. Users can also check open-sourced code. + +### [AdGuardCLI](https://github.com/AdguardTeam/AdGuardCLI) + +Repository of AdGuard for Linux — a command‑line interface for managing ad blocking. + +## AdGuard VPN products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdGuardVPNForiOS](https://github.com/AdguardTeam/AdGuardVPNForiOS) + +Repository of AdGuard VPN for iOS. Serves as an open bug tracker. + +### [AdGuardVPNForAndroid](https://github.com/AdguardTeam/AdGuardVPNForAndroid) + +Repository of AdGuard VPN for Android. Serves as an open bug tracker. + +### [AdGuardVPNForWindows](https://github.com/AdguardTeam/AdGuardVPNForWindows) + +Repository of AdGuard VPN for Windows. Serves as an open bug tracker. + +### [AdGuardVPNForMac](https://github.com/AdguardTeam/AdGuardVPNForMac) + +Repository of AdGuard VPN for Mac — app designed for macOS. + +### [AdGuardVPNExtension](https://github.com/AdguardTeam/AdGuardVPNExtension) + +Repository of AdGuard VPN Browser Extension. + +### [AdGuardVPNCLI](https://github.com/AdguardTeam/AdGuardVPNCLI) + +Repository of AdGuard VPN for Linux — a command‑line interface for managing VPN connection. The repo acts as a bug tracker. + +## DNS-based products + +### [AdGuardDNS](https://github.com/AdguardTeam/AdGuardDNS) + +Open-source repository that is also used for tracking bugs and issues related to AdGuard DNS service. Users can: + +- View and report DNS issues +- Suggest improvements + +### [AdGuardHome](https://github.com/AdguardTeam/AdGuardHome) + +Repository of AdGuard Home — free network-wide software for blocking ads and trackers via DNS. Users can: + +- Check and file bug reports or feature requests +- Review or contribute to code +- Download and install releases + +## Documentation and Knowledge bases + +Knowledge bases are aimed to help users better understand and use AdGuard. They describe each AdGuard product in detail: from feature overviews and problem-solving guides to advanced setting manuals and API documentations. In the repositories users can: + +- Suggest corrections or edits to knowledge base articles +- Propose new articles +- Test or run the local version + +### [KnowledgeBase](https://github.com/AdguardTeam/KnowledgeBase) + +Central documentation for AdGuard Ad Blocker and the technologies related to it. + +### [KnowledgeBaseDNS](https://github.com/AdguardTeam/KnowledgeBaseDNS) + +Detailed feature overview, troubleshooting guides and documentation for AdGuard DNS (both Public and Private), AdGuard Home, and everything related to them. + +### [KnowledgeBaseVPN](https://github.com/AdguardTeam/KnowledgeBaseVPN) + +Detailed feature overview and troubleshooting guides for AdGuard VPN. + +### [KnowledgeBaseMail](https://github.com/AdguardTeam/KnowledgeBaseMail) + +Detailed feature overview and troubleshooting guides of AdGuard Mail. + +## Core libraries + +### [CoreLibs](https://github.com/AdguardTeam/CoreLibs) + +AdGuard’s cross-platform core filtering engine. Used in Android, Windows, and Mac products. Users can: + +- Explore filtering logic and DNS handling +- Report bugs and suggest features via Issues + +### [DNSLibs](https://github.com/AdguardTeam/DNSLibs) + +A DNS library used by CoreLibs and AdGuardHome. Users can: + +- Review and contribute to low-level DNS implementation +- Suggest optimizations + +### [VPNLibs](https://github.com/AdguardTeam/VPNLibs) + +Shared codebase used in AdGuard VPN products across platforms for AdGuard VPN protocol implementation. Users can: + +- Contribute to VPN stack behavior +- Report or view performance issues and bugs + +## Core ad blocking and filtering technologies + +### [AdguardFilters](https://github.com/AdguardTeam/AdguardFilters) + +Contains AdGuard’s core filter lists. Users can: + +- View and download filter lists +- Create issues to report false positives or suggest new rules +- Monitor updates to filter logic + +### [AdGuardSDNSFilter](https://github.com/AdguardTeam/AdGuardSDNSFilter) + +Repository of AdGuard DNS filter — the main DNS-level blocking list used in AdGuard DNS and DNS filtering features. Users can: + +- Inspect the current rule set +- Propose changes or additions + +### [AGLint](https://github.com/AdguardTeam/AGLint) + +A linter for adblock filter list syntax. Users can: + +- Install AGLint to check their projects for rule issues +- Contribute to lint rules + +### [Scriptlets](https://github.com/AdguardTeam/Scriptlets) + +JavaScript helpers used in filtering rules. Users can: + +- Explore available scriptlets +- Submit pull requests for new scriptlets + +### [tsurlfilter](https://github.com/AdguardTeam/tsurlfilter) + +TypeScript content blocker library for browser extensions. Users can: + +- Explore how filtering logic is implemented +- Contribute fixes and features + +## There’s more + +Above, we listed 27 main public AdGuard repositories out of 96 total. If you want to go down the rabbit hole, you can [find the rest on the AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse). + +We’ll be waiting for your feedback there! Stay safe online and offline. diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/general/how-to-install.md b/i18n/vi/docusaurus-plugin-content-docs/current/general/how-to-install.md index 106a29529a8..4ba78d7a094 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/general/how-to-install.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/general/how-to-install.md @@ -1,6 +1,6 @@ --- title: How to install AdGuard -sidebar_position: 9 +sidebar_position: 10 --- Depending on which AdGuard app or browser extension you want to install, follow one of these links to find the relevant article: diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md index f8eafc44514..6322cd56b7b 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md @@ -43,6 +43,14 @@ Here you can choose which proxy AdGuard should use to download filter updates or ## Use SockFilter driver -Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. +Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. If this option is disabled, AdGuard will switch to the older WFP driver instead. -If this option is disabled, AdGuard will switch to the older WFP driver instead. +SockFilter was first introduced in v8.0 RC. It is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md index cfff1fd07f9..53a529a6824 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Because of this, TDI-based traffic visibility becomes increasingly unstable. In AdGuard already treats the TDI driver as deprecated, and its complete removal is planned as the product evolves. +## Permanent solution + +From v8.0 RC, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows-8/settings/app-settings/network-settings/). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Temporary solution Certain Windows registry changes can force the browser to stop using AppContainer, causing its processes to run in a non-sandboxed mode again. Network Service stops using the WSK stack and falls back to a network path that the TDI driver can see. AdGuard then regains the ability to filter browser traffic. @@ -123,7 +131,3 @@ You should see the following policies active: If available, click _Reload policies_. 完成！ - -## Permanent solution - -We’re planning to add support for the SockFilter driver in the upcoming versions. It will fix the issue by solving conflicts in the WFP stack. [More information](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index 15c804ac7c9..0f685131fbd 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -17,23 +17,35 @@ sidebar_position: 4 最后是代理设置部分。 用户可以在此处指定 AdGuard 更新过滤器，获取新版本等所用的代理服务器。 -### SockFilter and other network drivers +### Enable traffic filtering -In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. +Traffic filtering is the core mechanism that allows AdGuard to inspect and control the network traffic generated by applications on your computer. When it is enabled, AdGuard intercepts outgoing and incoming connections and checks them against its filtering rules. If a request matches a blocking rule, AdGuard can block it, modify it, or allow it depending on the configuration. In AdGuard for Windows, this interception is implemented through network drivers. -**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. +If HTTPS filtering is enabled, AdGuard performs a controlled local TLS interception: it decrypts the traffic using its local certificate, applies filtering rules, and then re-encrypts the traffic before sending it to the browser. The driver simply provides the system-level access needed for AdGuard to intercept these connections. -The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +#### SockFilter **SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. -Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: +SockFilter was first implemented in version 7.22.4, and it is still considered unstable — you may encounter bugs. Once fully tested and implemented, SockFilter has the potential to offer several advantages over other drivers: -- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. - **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. -- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. -When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. +#### WFP + +**WFP** (Windows Filtering Platform) is a Microsoft networking framework built into Windows that allows software to filter and monitor network packets at different layers of the system networking stack. AdGuard uses WFP to safely hook into the network flow of applications and apply filtering rules before the traffic reaches the browser or the Internet. [More information](https://learn.microsoft.com/en-us/windows/win32/fwp/windows-filtering-platform-architecture-overview). + +While it is a powerful driver, it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) and lower Internet speed for some users. + +#### TDI + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. ### AdGuard VPN diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index a5a75326aeb..ddc0e9a0013 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -44,12 +44,8 @@ In the Ad blocking module you can: Many websites gather information about their visitors, such as their IP addresses, browser and operating system details, screen resolution, and the webpage from which the user came or was redirected. Some websites use cookies to mark and identify your browser, save your personal settings and preferences. This allows them to “recognize” you on your next visit. Tracking protection safeguards your personal information from these data- and statistics-gathering systems. -![Tracking protection levels \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection1.png) - You can adjust the _Tracking Protection_ settings as needed. For example, you can prevent websites from receiving the search request that you used to find them on the Internet, automatically delete third- and first-party cookies, and disable location sharing in your browser, to prevent tracking of your whereabouts. -![Tracking protection custom features \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection2.png) - To learn everything about _Tracking protection_ and its many options, [read this article](/general/stealth-mode). ### 浏览安全 diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md index d7070ee7c8c..66cdac2947a 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Because of this, TDI-based traffic visibility becomes increasingly unstable. In AdGuard already treats the TDI driver as deprecated, and its complete removal is planned as the product evolves. +## Permanent solution + +From v7.22.4, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows/features/network/#sockfilter-and-other-network-drivers). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Temporary solution Certain Windows registry changes can force the browser to stop using AppContainer, causing its processes to run in a non-sandboxed mode again. Network Service stops using the WSK stack and falls back to a network path that the TDI driver can see. AdGuard then regains the ability to filter browser traffic. @@ -136,7 +144,3 @@ You should see the following policies active: If available, click _Reload policies_. 完成！ - -## Permanent solution - -We’re planning to add support for the SockFilter driver in the upcoming versions. It will fix the issue by solving conflicts in the WFP stack. [More information](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-mini-for-mac/features/settings/filters.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-mini-for-mac/features/settings/filters.md index adc88484f88..bf9dd1b420b 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-mini-for-mac/features/settings/filters.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-mini-for-mac/features/settings/filters.md @@ -3,22 +3,22 @@ title: 过滤器 sidebar_position: 2 --- -![Filters tab](https://cdn.adtidy.org/content/kb/ad_blocker/mini_mac/filters.png) +![过滤器标签](https://cdn.adtidy.org/content/kb/ad_blocker/mini_mac/filters.png) 前往「_设置_」→「_过滤_」，启用单独的过滤器或整个过滤器类别。 -Filters are the backbone of ad blocking and basically it’s what keeps the Internet clean. 过滤器是用特殊语法编写的规则列表。 根据这些规则，内容拦截器可以过滤网络流量：拦截广告或对恶意网站的请求。 +过滤器是广告拦截的核心，本质上正是它们让互联网保持整洁。 过滤器是用特殊语法编写的规则列表。 内容拦截器遵循这些规则来过滤网络流量：拦截广告或恶意网站的请求。 -Filters are combined into eight thematic categories: _Ad Blocking, Privacy, Social widgets, Annoyances, Security, Language-specific filters, Custom,_ and _Other filters_. +过滤器共分为八个主题类别：广告拦截、隐私、社交插件、恼人元素、安全、语言专用过滤器、自定义过滤器和其他过滤器。 -了解更多有关 [AdGuard 过滤器](/general/ad-filtering/adguard-filters)或[一般广告过滤](/general/ad-filtering/how-ad-blocking-works)的信息。 +阅读更多关于 [AdGuard 过滤器](/general/ad-filtering/adguard-filters) 或[广告过滤的一般信息(/general/ad-filtering/how-ad-blocking-works)。 -Changes in _Filters_ are also reflected in _Settings_ → _Safari extensions_. +过滤器的更改也会同步反映在「设置」→「Safari 扩展」中。 ## 自定义过滤器 -![Create custom filter](https://cdn.adtidy.org/content/kb/ad_blocker/mini_mac/create-custom.png) +![建立自定义过滤器](https://cdn.adtidy.org/content/kb/ad_blocker/mini_mac/create-custom.png) -To add a custom filter, go to _Settings_ → _Filters_ → _Custom filters_ and enter a URL or a local file path in the relevant field. +要添加自定义过滤器，请转到「设置」→「过滤器」→「自定义过滤器」，并在相关字段中输入 URL 或本地文件路径。 -You can find a lot of filters at [filterlists.com](https://filterlists.com/). +在 [filterlists.com](https://filterlists.com/) 上可以找到很多过滤器。 diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/github-repos.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/github-repos.md new file mode 100644 index 00000000000..dfb164c44bc --- /dev/null +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/github-repos.md @@ -0,0 +1,238 @@ +--- +title: AdGuard’s GitHub repositories +sidebar_position: 9 +--- + +At AdGuard, our goal is to make the Internet safer, more comfortable, and more transparent. This commitment is reflected not only in our product features and strict privacy policies, but also in the fact that we keep our work as open as possible. That includes actively interacting with our community. + +This is why [all of our products have public repositories](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse) — online spaces where anybody can see what we are working on, report issues directly to AdGuard developers, and even contribute to our open-source projects. The repositories cover our ad-blocking apps, filters, browser extensions, DNS solutions, VPN tools, developer utilities, and more. There are different platforms that offer such functionality, but the most popular one by far is GitHub, and all AdGuard projects are stored there. + +This article lists the most important repositories by category, summarizes the purpose of each one, and gives a simple breakdown of what users can do there. + +:::tip + +Pro tip: Creating an issue on GitHub is the most effective way to bring the attention of AdGuard developers to a problem. Just make sure to check that a similar issue doesn’t already exist and describe the problem in a comprehensive but concise way. If it does exist, you can upvote it. + +::: + +## What is Github and its repositories + +Very simply put, you can think of GitHub as sort of Google Docs for code, where multiple people can work on the same project, track changes, and see who made which updates. It provides a central, cloud-based place to store your code so it’s accessible from anywhere. It also has teamwork tools for reviewing changes, fixing issues, and merging everyone’s work smoothly. + +GitHub is widely used for open-source projects, letting anyone view the code, suggest improvements, and contribute. + +A repository (often called “repo” for short) is the most basic element of GitHub. It’s a place where you can store your code, your files, and each file’s revision history. Repositories can have multiple collaborators and can be either public or private. + +## What can you do in AdGuard’s repositories + +You can find links to key repositories below in this article or visit the [general AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all) for a full list. In most repos, you can: + +- **View README file** on the main page: it gives you an introduction to the product and its repo + ![README file \*border](https://cdn.adtidy.org/content/blog/github-repos/see-readme.png) + +- **Check existing bug reports or feature requests**, comment and upvote + ![Check issues \*border](https://cdn.adtidy.org/content/blog/github-repos/check-issues.png) + +- **Create issues** to report bugs or request features + ![Create issues \*border](https://cdn.adtidy.org/content/blog/github-repos/create-issue.png) + +- **Check releases** for different versions and their changelogs (and install an older version if needed) + ![Check releases \*border](https://cdn.adtidy.org/content/blog/github-repos/check-releases.png) + +- **Install any older or beta version** if needed + ![Download builds \*border](https://cdn.adtidy.org/content/blog/github-repos/download-releases.png) + +:::note + +If you are new to GitHub, you’ll need to create a GitHub account in order to create new issues and comment on the existing ones. + +::: + +In open-source repos advanced users can also: + +- **Browse code** to understand product logic, what technologies are used and how they are implemented +- **Fork and contribute** via pull requests + +Whether you’re a casual user, technical expert, or a developer, AdGuard welcomes all community participation across its GitHub repos. + +## Legal documents + +### [LegalDocs](https://github.com/AdguardTeam/LegalDocs) + +As part of our commitment to transparency, we host all legal documents — such as End-User License Agreements, Privacy Policies, and Terms and Conditions — on GitHub. Our _LegalDocs_ repo lets anyone check the full history of changes to these documents. + +## AdGuard Ad Blocker products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdguardForAndroid](https://github.com/AdguardTeam/AdguardForAndroid) + +Repository of AdGuard for Android — an app that provides system-wide ad blocking. + +### [AdguardForiOS](https://github.com/AdguardTeam/AdguardForiOS) + +Repository of AdGuard for iOS — Safari content blocker with DNS and custom filters. Users can also check open-source code. + +### [AdguardForWindows](https://github.com/AdguardTeam/AdguardForWindows) + +Repository of AdGuard for Windows. Non-open-source; GitHub used as an open bug tracker. + +### [AdguardForMac](https://github.com/AdguardTeam/AdguardForMac) + +Repository of AdGuard for Mac — macOS standalone content blocker. Bug tracker only. + +### [AdguardBrowserExtension](https://github.com/AdguardTeam/AdguardBrowserExtension) + +Repository of AdGuard Browser Extension — extension that provides ad blocking with enhanced privacy for Chrome, Firefox, Opera, Edge. + +### [AdguardForSafari](https://github.com/AdguardTeam/AdGuardForSafari) + +Repository of AdGuard for Safari — Safari ad blocking extension for Mac. Users can also check open-sourced code. + +### [AdGuardCLI](https://github.com/AdguardTeam/AdGuardCLI) + +Repository of AdGuard for Linux — a command‑line interface for managing ad blocking. + +## AdGuard VPN products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdGuardVPNForiOS](https://github.com/AdguardTeam/AdGuardVPNForiOS) + +Repository of AdGuard VPN for iOS. Serves as an open bug tracker. + +### [AdGuardVPNForAndroid](https://github.com/AdguardTeam/AdGuardVPNForAndroid) + +Repository of AdGuard VPN for Android. Serves as an open bug tracker. + +### [AdGuardVPNForWindows](https://github.com/AdguardTeam/AdGuardVPNForWindows) + +Repository of AdGuard VPN for Windows. Serves as an open bug tracker. + +### [AdGuardVPNForMac](https://github.com/AdguardTeam/AdGuardVPNForMac) + +Repository of AdGuard VPN for Mac — app designed for macOS. + +### [AdGuardVPNExtension](https://github.com/AdguardTeam/AdGuardVPNExtension) + +Repository of AdGuard VPN Browser Extension. + +### [AdGuardVPNCLI](https://github.com/AdguardTeam/AdGuardVPNCLI) + +Repository of AdGuard VPN for Linux — a command‑line interface for managing VPN connection. The repo acts as a bug tracker. + +## DNS-based products + +### [AdGuardDNS](https://github.com/AdguardTeam/AdGuardDNS) + +Open-source repository that is also used for tracking bugs and issues related to AdGuard DNS service. Users can: + +- View and report DNS issues +- Suggest improvements + +### [AdGuardHome](https://github.com/AdguardTeam/AdGuardHome) + +Repository of AdGuard Home — free network-wide software for blocking ads and trackers via DNS. Users can: + +- Check and file bug reports or feature requests +- Review or contribute to code +- Download and install releases + +## Documentation and Knowledge bases + +Knowledge bases are aimed to help users better understand and use AdGuard. They describe each AdGuard product in detail: from feature overviews and problem-solving guides to advanced setting manuals and API documentations. In the repositories users can: + +- Suggest corrections or edits to knowledge base articles +- Propose new articles +- Test or run the local version + +### [KnowledgeBase](https://github.com/AdguardTeam/KnowledgeBase) + +Central documentation for AdGuard Ad Blocker and the technologies related to it. + +### [KnowledgeBaseDNS](https://github.com/AdguardTeam/KnowledgeBaseDNS) + +Detailed feature overview, troubleshooting guides and documentation for AdGuard DNS (both Public and Private), AdGuard Home, and everything related to them. + +### [KnowledgeBaseVPN](https://github.com/AdguardTeam/KnowledgeBaseVPN) + +Detailed feature overview and troubleshooting guides for AdGuard VPN. + +### [KnowledgeBaseMail](https://github.com/AdguardTeam/KnowledgeBaseMail) + +Detailed feature overview and troubleshooting guides of AdGuard Mail. + +## Core libraries + +### [CoreLibs](https://github.com/AdguardTeam/CoreLibs) + +AdGuard’s cross-platform core filtering engine. Used in Android, Windows, and Mac products. Users can: + +- Explore filtering logic and DNS handling +- Report bugs and suggest features via Issues + +### [DNSLibs](https://github.com/AdguardTeam/DNSLibs) + +A DNS library used by CoreLibs and AdGuardHome. Users can: + +- Review and contribute to low-level DNS implementation +- Suggest optimizations + +### [VPNLibs](https://github.com/AdguardTeam/VPNLibs) + +Shared codebase used in AdGuard VPN products across platforms for AdGuard VPN protocol implementation. Users can: + +- Contribute to VPN stack behavior +- Report or view performance issues and bugs + +## Core ad blocking and filtering technologies + +### [AdguardFilters](https://github.com/AdguardTeam/AdguardFilters) + +Contains AdGuard’s core filter lists. Users can: + +- View and download filter lists +- Create issues to report false positives or suggest new rules +- Monitor updates to filter logic + +### [AdGuardSDNSFilter](https://github.com/AdguardTeam/AdGuardSDNSFilter) + +Repository of AdGuard DNS filter — the main DNS-level blocking list used in AdGuard DNS and DNS filtering features. Users can: + +- Inspect the current rule set +- Propose changes or additions + +### [AGLint](https://github.com/AdguardTeam/AGLint) + +A linter for adblock filter list syntax. Users can: + +- Install AGLint to check their projects for rule issues +- Contribute to lint rules + +### [Scriptlets](https://github.com/AdguardTeam/Scriptlets) + +JavaScript helpers used in filtering rules. Users can: + +- Explore available scriptlets +- Submit pull requests for new scriptlets + +### [tsurlfilter](https://github.com/AdguardTeam/tsurlfilter) + +TypeScript content blocker library for browser extensions. Users can: + +- Explore how filtering logic is implemented +- Contribute fixes and features + +## There’s more + +Above, we listed 27 main public AdGuard repositories out of 96 total. If you want to go down the rabbit hole, you can [find the rest on the AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse). + +We’ll be waiting for your feedback there! Stay safe online and offline. diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/how-to-install.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/how-to-install.md index 70c6f007a71..b695be5edd1 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/how-to-install.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/how-to-install.md @@ -1,6 +1,6 @@ --- title: 如何安装 AdGuard -sidebar_position: 9 +sidebar_position: 10 --- 根据您想安装的 AdGuard 应用程序或浏览器扩展，请按照以下不同的链接找到相关文章： diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md index 3953f47d26f..05642d350b0 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/network-settings.md @@ -43,6 +43,14 @@ Here you can choose which proxy AdGuard should use to download filter updates or ## Use SockFilter driver -Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. +Enable this option to use the SockFilter driver, which helps block ads and trackers in apps on Windows 8 and later. If this option is disabled, AdGuard will switch to the older WFP driver instead. -If this option is disabled, AdGuard will switch to the older WFP driver instead. +SockFilter was first introduced in v8.0 RC. It is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md index 251e49cf286..1ab588bb16c 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows-8/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Because of this, TDI-based traffic visibility becomes increasingly unstable. In AdGuard already treats the TDI driver as deprecated, and its complete removal is planned as the product evolves. +## Permanent solution + +From v8.0 RC, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows-8/settings/app-settings/network-settings/). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Temporary solution Certain Windows registry changes can force the browser to stop using AppContainer, causing its processes to run in a non-sandboxed mode again. Network Service stops using the WSK stack and falls back to a network path that the TDI driver can see. AdGuard then regains the ability to filter browser traffic. @@ -123,7 +131,3 @@ You should see the following policies active: If available, click _Reload policies_. Done! - -## Permanent solution - -We’re planning to add support for the SockFilter driver in the upcoming versions. It will fix the issue by solving conflicts in the WFP stack. [More information](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index 5945618ea9c..f8074e9cfa1 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -17,23 +17,35 @@ In this module you can select the checkbox _Use AdGuard as an HTTP proxy_ to use At last, there is a section with proxy settings. There you can specify which proxy server AdGuard should use to update filters, get new versions, and so on. -### SockFilter and other network drivers +### Enable traffic filtering -In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. +Traffic filtering is the core mechanism that allows AdGuard to inspect and control the network traffic generated by applications on your computer. When it is enabled, AdGuard intercepts outgoing and incoming connections and checks them against its filtering rules. If a request matches a blocking rule, AdGuard can block it, modify it, or allow it depending on the configuration. In AdGuard for Windows, this interception is implemented through network drivers. -**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. +If HTTPS filtering is enabled, AdGuard performs a controlled local TLS interception: it decrypts the traffic using its local certificate, applies filtering rules, and then re-encrypts the traffic before sending it to the browser. The driver simply provides the system-level access needed for AdGuard to intercept these connections. -The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +#### SockFilter **SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. -Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: +SockFilter was first implemented in version 7.22.4, and it is still considered unstable — you may encounter bugs. Once fully tested and implemented, SockFilter has the potential to offer several advantages over other drivers: -- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP’s low-level packet filtering. - **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. -- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn’t run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that’s exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. -When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. +#### WFP + +**WFP** (Windows Filtering Platform) is a Microsoft networking framework built into Windows that allows software to filter and monitor network packets at different layers of the system networking stack. AdGuard uses WFP to safely hook into the network flow of applications and apply filtering rules before the traffic reaches the browser or the Internet. [More information](https://learn.microsoft.com/en-us/windows/win32/fwp/windows-filtering-platform-architecture-overview). + +While it is a powerful driver, it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) and lower Internet speed for some users. + +#### TDI + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. ### AdGuard VPN diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index ab90a964b9f..5699b31b033 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -44,12 +44,8 @@ Before you start manually writing your own rules read our detailed [syntax guide Many websites gather information about their visitors, such as their IP addresses, browser and operating system details, screen resolution, and the webpage from which the user came or was redirected. Some websites use cookies to mark and identify your browser, save your personal settings and preferences. This allows them to “recognize” you on your next visit. Tracking protection safeguards your personal information from these data- and statistics-gathering systems. -![Tracking protection levels \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection1.png) - You can adjust the _Tracking Protection_ settings as needed. For example, you can prevent websites from receiving the search request that you used to find them on the Internet, automatically delete third- and first-party cookies, and disable location sharing in your browser, to prevent tracking of your whereabouts. -![Tracking protection custom features \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/settings/tracking_protection2.png) - To learn everything about _Tracking protection_ and its many options, [read this article](/general/stealth-mode). ### Browsing security diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md index 62370bf3eb1..bec08d0c665 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md @@ -33,6 +33,14 @@ Because of this, TDI-based traffic visibility becomes increasingly unstable. In AdGuard already treats the TDI driver as deprecated, and its complete removal is planned as the product evolves. +## Permanent solution + +From v7.22.4, we’ve added experimental support for the SockFilter driver. It fixes the issue by solving conflicts in the WFP stack. [More information](/adguard-for-windows/features/network/#sockfilter-and-other-network-drivers). + +To use it, go to _Settings → Network → Traffic filtering_, enable traffic filtering, and select _SockFilter (Experimental)_ from the list of available options. + +Since it’s experimental, there may be bugs. If you notice anything unusual, unexpected, or just plain broken, **you can switch back to TDI or WFP at any time** in the same section. + ## Temporary solution Certain Windows registry changes can force the browser to stop using AppContainer, causing its processes to run in a non-sandboxed mode again. Network Service stops using the WSK stack and falls back to a network path that the TDI driver can see. AdGuard then regains the ability to filter browser traffic. @@ -136,7 +144,3 @@ You should see the following policies active: If available, click _Reload policies_. Done! - -## Permanent solution - -We’re planning to add support for the SockFilter driver in the upcoming versions. It will fix the issue by solving conflicts in the WFP stack. [More information](https://github.com/AdguardTeam/AdguardForWindows/issues/5780). diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/github-repos.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/github-repos.md new file mode 100644 index 00000000000..dfb164c44bc --- /dev/null +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/github-repos.md @@ -0,0 +1,238 @@ +--- +title: AdGuard’s GitHub repositories +sidebar_position: 9 +--- + +At AdGuard, our goal is to make the Internet safer, more comfortable, and more transparent. This commitment is reflected not only in our product features and strict privacy policies, but also in the fact that we keep our work as open as possible. That includes actively interacting with our community. + +This is why [all of our products have public repositories](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse) — online spaces where anybody can see what we are working on, report issues directly to AdGuard developers, and even contribute to our open-source projects. The repositories cover our ad-blocking apps, filters, browser extensions, DNS solutions, VPN tools, developer utilities, and more. There are different platforms that offer such functionality, but the most popular one by far is GitHub, and all AdGuard projects are stored there. + +This article lists the most important repositories by category, summarizes the purpose of each one, and gives a simple breakdown of what users can do there. + +:::tip + +Pro tip: Creating an issue on GitHub is the most effective way to bring the attention of AdGuard developers to a problem. Just make sure to check that a similar issue doesn’t already exist and describe the problem in a comprehensive but concise way. If it does exist, you can upvote it. + +::: + +## What is Github and its repositories + +Very simply put, you can think of GitHub as sort of Google Docs for code, where multiple people can work on the same project, track changes, and see who made which updates. It provides a central, cloud-based place to store your code so it’s accessible from anywhere. It also has teamwork tools for reviewing changes, fixing issues, and merging everyone’s work smoothly. + +GitHub is widely used for open-source projects, letting anyone view the code, suggest improvements, and contribute. + +A repository (often called “repo” for short) is the most basic element of GitHub. It’s a place where you can store your code, your files, and each file’s revision history. Repositories can have multiple collaborators and can be either public or private. + +## What can you do in AdGuard’s repositories + +You can find links to key repositories below in this article or visit the [general AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all) for a full list. In most repos, you can: + +- **View README file** on the main page: it gives you an introduction to the product and its repo + ![README file \*border](https://cdn.adtidy.org/content/blog/github-repos/see-readme.png) + +- **Check existing bug reports or feature requests**, comment and upvote + ![Check issues \*border](https://cdn.adtidy.org/content/blog/github-repos/check-issues.png) + +- **Create issues** to report bugs or request features + ![Create issues \*border](https://cdn.adtidy.org/content/blog/github-repos/create-issue.png) + +- **Check releases** for different versions and their changelogs (and install an older version if needed) + ![Check releases \*border](https://cdn.adtidy.org/content/blog/github-repos/check-releases.png) + +- **Install any older or beta version** if needed + ![Download builds \*border](https://cdn.adtidy.org/content/blog/github-repos/download-releases.png) + +:::note + +If you are new to GitHub, you’ll need to create a GitHub account in order to create new issues and comment on the existing ones. + +::: + +In open-source repos advanced users can also: + +- **Browse code** to understand product logic, what technologies are used and how they are implemented +- **Fork and contribute** via pull requests + +Whether you’re a casual user, technical expert, or a developer, AdGuard welcomes all community participation across its GitHub repos. + +## Legal documents + +### [LegalDocs](https://github.com/AdguardTeam/LegalDocs) + +As part of our commitment to transparency, we host all legal documents — such as End-User License Agreements, Privacy Policies, and Terms and Conditions — on GitHub. Our _LegalDocs_ repo lets anyone check the full history of changes to these documents. + +## AdGuard Ad Blocker products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdguardForAndroid](https://github.com/AdguardTeam/AdguardForAndroid) + +Repository of AdGuard for Android — an app that provides system-wide ad blocking. + +### [AdguardForiOS](https://github.com/AdguardTeam/AdguardForiOS) + +Repository of AdGuard for iOS — Safari content blocker with DNS and custom filters. Users can also check open-source code. + +### [AdguardForWindows](https://github.com/AdguardTeam/AdguardForWindows) + +Repository of AdGuard for Windows. Non-open-source; GitHub used as an open bug tracker. + +### [AdguardForMac](https://github.com/AdguardTeam/AdguardForMac) + +Repository of AdGuard for Mac — macOS standalone content blocker. Bug tracker only. + +### [AdguardBrowserExtension](https://github.com/AdguardTeam/AdguardBrowserExtension) + +Repository of AdGuard Browser Extension — extension that provides ad blocking with enhanced privacy for Chrome, Firefox, Opera, Edge. + +### [AdguardForSafari](https://github.com/AdguardTeam/AdGuardForSafari) + +Repository of AdGuard for Safari — Safari ad blocking extension for Mac. Users can also check open-sourced code. + +### [AdGuardCLI](https://github.com/AdguardTeam/AdGuardCLI) + +Repository of AdGuard for Linux — a command‑line interface for managing ad blocking. + +## AdGuard VPN products + +In these repositories, users can: + +- View and report bugs or feature requests via GitHub issues +- Check changelogs, track release history, monitor updates +- Download latest, previous, and beta builds (except for iOS) + +### [AdGuardVPNForiOS](https://github.com/AdguardTeam/AdGuardVPNForiOS) + +Repository of AdGuard VPN for iOS. Serves as an open bug tracker. + +### [AdGuardVPNForAndroid](https://github.com/AdguardTeam/AdGuardVPNForAndroid) + +Repository of AdGuard VPN for Android. Serves as an open bug tracker. + +### [AdGuardVPNForWindows](https://github.com/AdguardTeam/AdGuardVPNForWindows) + +Repository of AdGuard VPN for Windows. Serves as an open bug tracker. + +### [AdGuardVPNForMac](https://github.com/AdguardTeam/AdGuardVPNForMac) + +Repository of AdGuard VPN for Mac — app designed for macOS. + +### [AdGuardVPNExtension](https://github.com/AdguardTeam/AdGuardVPNExtension) + +Repository of AdGuard VPN Browser Extension. + +### [AdGuardVPNCLI](https://github.com/AdguardTeam/AdGuardVPNCLI) + +Repository of AdGuard VPN for Linux — a command‑line interface for managing VPN connection. The repo acts as a bug tracker. + +## DNS-based products + +### [AdGuardDNS](https://github.com/AdguardTeam/AdGuardDNS) + +Open-source repository that is also used for tracking bugs and issues related to AdGuard DNS service. Users can: + +- View and report DNS issues +- Suggest improvements + +### [AdGuardHome](https://github.com/AdguardTeam/AdGuardHome) + +Repository of AdGuard Home — free network-wide software for blocking ads and trackers via DNS. Users can: + +- Check and file bug reports or feature requests +- Review or contribute to code +- Download and install releases + +## Documentation and Knowledge bases + +Knowledge bases are aimed to help users better understand and use AdGuard. They describe each AdGuard product in detail: from feature overviews and problem-solving guides to advanced setting manuals and API documentations. In the repositories users can: + +- Suggest corrections or edits to knowledge base articles +- Propose new articles +- Test or run the local version + +### [KnowledgeBase](https://github.com/AdguardTeam/KnowledgeBase) + +Central documentation for AdGuard Ad Blocker and the technologies related to it. + +### [KnowledgeBaseDNS](https://github.com/AdguardTeam/KnowledgeBaseDNS) + +Detailed feature overview, troubleshooting guides and documentation for AdGuard DNS (both Public and Private), AdGuard Home, and everything related to them. + +### [KnowledgeBaseVPN](https://github.com/AdguardTeam/KnowledgeBaseVPN) + +Detailed feature overview and troubleshooting guides for AdGuard VPN. + +### [KnowledgeBaseMail](https://github.com/AdguardTeam/KnowledgeBaseMail) + +Detailed feature overview and troubleshooting guides of AdGuard Mail. + +## Core libraries + +### [CoreLibs](https://github.com/AdguardTeam/CoreLibs) + +AdGuard’s cross-platform core filtering engine. Used in Android, Windows, and Mac products. Users can: + +- Explore filtering logic and DNS handling +- Report bugs and suggest features via Issues + +### [DNSLibs](https://github.com/AdguardTeam/DNSLibs) + +A DNS library used by CoreLibs and AdGuardHome. Users can: + +- Review and contribute to low-level DNS implementation +- Suggest optimizations + +### [VPNLibs](https://github.com/AdguardTeam/VPNLibs) + +Shared codebase used in AdGuard VPN products across platforms for AdGuard VPN protocol implementation. Users can: + +- Contribute to VPN stack behavior +- Report or view performance issues and bugs + +## Core ad blocking and filtering technologies + +### [AdguardFilters](https://github.com/AdguardTeam/AdguardFilters) + +Contains AdGuard’s core filter lists. Users can: + +- View and download filter lists +- Create issues to report false positives or suggest new rules +- Monitor updates to filter logic + +### [AdGuardSDNSFilter](https://github.com/AdguardTeam/AdGuardSDNSFilter) + +Repository of AdGuard DNS filter — the main DNS-level blocking list used in AdGuard DNS and DNS filtering features. Users can: + +- Inspect the current rule set +- Propose changes or additions + +### [AGLint](https://github.com/AdguardTeam/AGLint) + +A linter for adblock filter list syntax. Users can: + +- Install AGLint to check their projects for rule issues +- Contribute to lint rules + +### [Scriptlets](https://github.com/AdguardTeam/Scriptlets) + +JavaScript helpers used in filtering rules. Users can: + +- Explore available scriptlets +- Submit pull requests for new scriptlets + +### [tsurlfilter](https://github.com/AdguardTeam/tsurlfilter) + +TypeScript content blocker library for browser extensions. Users can: + +- Explore how filtering logic is implemented +- Contribute fixes and features + +## There’s more + +Above, we listed 27 main public AdGuard repositories out of 96 total. If you want to go down the rabbit hole, you can [find the rest on the AdGuardTeam GitHub page](https://github.com/orgs/AdguardTeam/repositories?type=all&q=visibility%3Apublic+archived%3Afalse). + +We’ll be waiting for your feedback there! Stay safe online and offline. diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/how-to-install.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/how-to-install.md index 106a29529a8..4ba78d7a094 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/how-to-install.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/how-to-install.md @@ -1,6 +1,6 @@ --- title: How to install AdGuard -sidebar_position: 9 +sidebar_position: 10 --- Depending on which AdGuard app or browser extension you want to install, follow one of these links to find the relevant article: