AdguardTeam / AdguardTeam/CoreLibs

Signed Certificate Timestamps support is broken

Aperta
#1,979 2 commenti 1 reazione 1 assegnatario Rivendicata da @sfionov Vedi su GitHub
Bug needs tech clarification Priority: P4
Lingua principale
Nessun dato sulla lingua
Stelle
52
Fork
10
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

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

![Image](https://github.com/user-attachments/assets/73d679d4-5b9b-41c4-87a4-4e926cac3b45)

![Image](https://github.com/user-attachments/assets/51a19d65-924a-40aa-9730-7532f81a338f)

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

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.