dehydrated-io / dehydrated-io/dehydrated
ocsp fetch delay required after new cert was issued
- Dominant language
- Shell
- Stars
- 6.2k
- Forks
- 724
- PR merge metrics
- No merged PRs in 30d
Description
If you issue a new cert, then the ocsp information for that certificate is sometimes not yet available at the ocsp servers. In such situations a must-staple certificat will be unusable. A small delay between the certificate issuing and the ocsp fetching would help already but it looks like this is not possible to do just by changing the configuration or hook script. A "oscp-fetch-delay-after-cert-issuing" variable is needed I think, a fixed delay of something like 5s might also be okay, but I can imagine that some CAs might need an even longer sleep here.
Contributor guide
No contributing guide indexed for this repository
Research direction
Trace the shell client's certificate-issuing flow through its OCSP-fetching step, and inspect how configuration and hook scripts currently participate. Confirm how a delay could be represented and verify that the resulting behavior allows must-staple certificates to work when OCSP data is not immediately available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- cli, security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100