chaitin / chaitin/SafeLine

[Suggestion] Enable OCSP stapling for the certificate

Open
#1,199 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
22.6k
Forks
1.5k
Avg merge
4h 30m
Merged PRs (30d)
11

Description

What would you like to be added or improved?

Please add OCSP stapling if it is available in the certificate

OCSP stapling explained on:
https://en.wikipedia.org/wiki/OCSP_stapling

Why is it needed?

With OCSP stappling the client will receive the online version of the certificate revocation list (from the CA) during HTTPS handshake directly from the server.

This improves speed of handshake and security as the client will not look up the revocation information from the root CA but will use the provided OCSP information.

To test the certificate for OCSP use the following openssl command:
openssl x509 -in /path/to/CERTIFICATE.crt -noout -ocsp_uri

Add this to the conf file if OCSP is available:

    # OCSP Stapling ENABLED for better security
    ssl_stapling on;
    ssl_stapling_verify on;
    resolver 1.1.1.1 8.8.8.8 9.9.9.9 valid=300s;
    resolver_timeout 5s;

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

The issue names the certificate check (openssl x509 -in /path/to/CERTIFICATE.crt -noout -ocsp_uri) and the proposed TLS configuration directives, but no repository file or test. First locate SafeLine’s reverse-proxy HTTPS configuration and identify how certificate availability is handled. Done means supported certificates use the requested OCSP behavior and the configuration remains valid.

Written by the indexing model from the issue text.

Assessment

Tech stack
nginx
Domain
networking, security
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.