AdguardTeam / AdguardTeam/CoreLibs

Browser uses the default certificate after re-enabling protection

未关闭
#1,832 4 条评论 0 个 reaction 已指派 1 人 已被 @sfionov 认领 在 GitHub 查看
Bug Priority: P4
主要语言
没有语言数据
星标
52
派生
10
PR 合并指标
30 天内没有已合并 PR

描述

### Please answer the following questions for yourself before submitting an issue.

- [X] I am running the latest version
- [X] I checked the documentation and found no answer
- [X] I checked to make sure that this issue has not already been filed

### AdGuard version

4.3n21

### Environment

```markdown
- OS: Android 11
- Device: POCO F1
```

### Root access

- [X] Yes, I have it.

### What filters do you have enabled?

AdGuard Base filter, AdGuard Mobile Ads filter, AdGuard Russian filter, AdGuard Tracking Protection filter, AdGuard URL Tracking filter, AdGuard Social Media filter, AdGuard Annoyances filter

### What Stealth Mode options do you have enabled?

_No response_

### Issue Details

Steps to reproduce:
1. Disable protection
2. Open `github.com` in Chrome
3. Check the certificate and you will see it's given by `DigiCert`
4. Return to app and enable protection
5. Refresh the page.

### Expected Behavior

The certificate must be provided by AdGuard.

### Actual Behavior

The certificate are provided by DigiCert.

### Screenshots

Screenshot 1:

### Additional Information

_No response_

贡献指南

这个仓库没有索引到贡献指南

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。