litespeedtech / litespeedtech/openlitespeed

OLS doesn't renew OCSP respone with certbot

Open
#332 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
1.5k
Forks
233
Avg merge
2d 19h
Merged PRs (30d)
5

Description

Certbot uses symlinks to /etc/letsencrypt/archive/domain/ instead of replacing the file in /etc/letsencrypt/live/domain/, OLS doesn't check for the changes in the symlink and staples the OSCP response for the older cert along with the new cert, firefox throws a certificate error and blocks the connection

Steps to recreate.

Use certbot for SSL

Vist site ( it works normally)

Renew SSL

Restart OLS

Visit the site again in firefox ( it won't work )

Proposed solution:
As OLS checks for change to get a new cached OCSP response, it should also check if cert/key in vhost is a symlink and in case it is a link, check for the change in link and get a new response to staple

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the Certbot renewal sequence described: visit the site, renew the certificate, restart OLS, and revisit it in Firefox. Start by tracing how OLS detects certificate changes and caches OCSP responses for vhost cert/key paths, especially when those paths are symlinks. Done means the renewed certificate receives a matching OCSP response and Firefox no longer reports a certificate error.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
backend, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.