Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

⬆️ Update AdguardTeam/AdGuardHome to v0.107.53 #554

Merged
merged 1 commit into from
Oct 3, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 3, 2024

This PR contains the following updates:

Package Update Change
AdguardTeam/AdGuardHome patch v0.107.52 -> v0.107.53

Release Notes

AdguardTeam/AdGuardHome (AdguardTeam/AdGuardHome)

v0.107.53

Compare Source

See also the v0.107.53 GitHub milestone.

NOTE: Add new changes BELOW THIS COMMENT.
-->

Security
  • Previous versions of AdGuard Home allowed users to add any system it had
    access to as filters, exposing them to be world-readable. To prevent this,
    AdGuard Home now allows adding filtering-rule list files only from files
    matching the patterns enumerated in the filtering.safe_fs_patterns property
    in the configuration file.

    We thank @​itz-d0dgy for reporting this vulnerability, designated
    CVE-2024-36814, to us.

  • Additionally, AdGuard Home will now try to change the permissions of its files
    and directories to more restrictive ones to prevent similar vulnerabilities
    as well as limit the access to the configuration.

    We thank @​go-compile for reporting this vulnerability, designated
    CVE-2024-36586, to us.

  • Go version has been updated to prevent the possibility of exploiting the Go
    vulnerabilities fixed in 1.23.2.

Added
  • Support for 64-bit RISC-V architecture (#​5704).
  • Ecosia search engine is now supported in safe search (#​5009).
Changed
  • Upstream server URL domain names requirements has been relaxed and now follow
    the same rules as their domain specifications.
Configuration changes

In this release, the schema version has changed from 28 to 29.

  • The new array filtering.safe_fs_patterns contains glob patterns for paths of
    files that can be added as local filtering-rule lists. The migration should
    add list files that have already been added, as well as the default value,
    $DATA_DIR/userfilters/*.
Fixed
  • Property clients.runtime_sources.dhcp in the configuration file not taking
    effect.
  • Update Google safe search domains list (#​7155).
  • Enforce Bing safe search from Edge sidebar (#​7154).
  • Text overflow on the query log page (#​7119).
Known issues
  • Due to the complexity of the Windows permissions architecture and poor support
    from the standard Go library, we have to postpone the proper automated Windows
    fix until the next release.

    Temporary workaround: Set the permissions of the AdGuardHome directory
    to more restrictive ones manually. To do that:

    1. Locate the AdGuardHome directory.
    2. Right-click on it and navigate to Properties → Security → Advanced.
    3. (You might need to disable permission inheritance to make them more
      restricted.)
    4. Adjust to give the Full control access to only the user which runs
      AdGuard Home. Typically, Administrator.

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added dependencies Upgrade or downgrade of project dependencies. no-stale This issue or PR is exempted from the stable bot. labels Oct 3, 2024
Copy link

coderabbitai bot commented Oct 3, 2024

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@frenck frenck merged commit d96fd0b into main Oct 3, 2024
23 checks passed
@frenck frenck deleted the renovate/adguardteam-adguardhome-0.x branch October 3, 2024 13:24
@github-actions github-actions bot locked and limited conversation to collaborators Oct 5, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
dependencies Upgrade or downgrade of project dependencies. no-stale This issue or PR is exempted from the stable bot.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant