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

HTTPS filtering original certificate caching algorithm #1402

Closed
ameshkov opened this issue Jan 25, 2021 · 0 comments
Closed

HTTPS filtering original certificate caching algorithm #1402

ameshkov opened this issue Jan 25, 2021 · 0 comments

Comments

@ameshkov
Copy link
Member

ameshkov commented Jan 25, 2021

It seems that currently, we don't update the target server's cert when the target server cert's common name is changed.

This leads to the fact that I am seeing the same old cert when inspecting it via the browser assistant.

Steps to reproduce:

  1. Set up a server with some cert (for instance, CN=testdomain.yourdomain.org)
  2. Open it with AG enabled, inspect the original cert via the browser assistant extension
  3. Replace the old cert with a new one (for instance, CN=*.yourdomain.org)
  4. Reload the website and check what cert you're seeing via the browser assistant.
@ameshkov ameshkov added this to the v1.8 milestone Jan 25, 2021
@ameshkov ameshkov changed the title HTTPS filtering certificate re-issue algorithm HTTPS filtering certificate caching algorithm Jan 25, 2021
@ameshkov ameshkov changed the title HTTPS filtering certificate caching algorithm HTTPS filtering original certificate caching algorithm Jan 25, 2021
@ameshkov ameshkov modified the milestones: v1.8, v1.9 Jan 25, 2021
@adguard-bot adguard-bot modified the milestones: v1.9, v1.8 Jan 25, 2021
@adguard-bot adguard-bot assigned ngorskikh and unassigned sfionov Dec 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants