AdguardTeam / AdguardTeam/CoreLibs

Browser uses the default certificate after re-enabling protection

Ouverte
#1,832 4 commentaires 0 réactions 1 personne assignée Réclamée par @sfionov Voir sur GitHub
Bug Priority: P4
Langage dominant
Aucune donnée de langage
Étoiles
52
Forks
10
Métriques de merge des PR
Aucune PR mergée en 30 j

Description

### 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_

Guide de contribution

Aucun guide de contribution indexé pour ce dépôt

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.