AdguardTeam / AdguardTeam/CoreLibs
Signed Certificate Timestamps support is broken
- Vorherrschende Sprache
- Keine Sprachdaten
- Sterne
- 52
- Forks
- 10
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
### Please answer the following questions for yourself before submitting an issue
- [x] Filters were updated before reproducing an issue
- [x] I checked the [knowledge base](https://adguard.com/kb/) and found no answer
- [x] I checked to make sure that this issue has not already been filed
### AdGuard version
7.20.3
### Browser version
Chrome 137
### OS version
Windows 11 24H2
### Issue Details
Steps to reproduce:
1. Go to https://no-sct.badssl.com/ to check that the Signed Certificate Timestamps are working correctly
2. View site information (button next to the URL in Chrome)
### Expected Behavior
The browser should issue the error: net::ERR_CERTIFICATE_TRANSPARENCY_REQUIRED and mark the connection as an unsecured connection.
### Actual Behavior
The browser loads the web page and marks it as a secure connection, when it is not.
### Screenshots
Screenshot 1


### Additional Information
The feature [was implemented in 2023](https://github.com/AdguardTeam/CoreLibs/issues/1529), but it doesn't seem to be working properly. did adguard remove it, or is it a bug?
Beitragsleitfaden
Für dieses Repository ist kein Beitragsleitfaden indexiert
Bewertung
Dieses Issue wurde noch nicht bewertet.