golang/go

crypto/tls: implement OCSP Must-Staple

Open

#22,274 opened on Oct 14, 2017

View on GitHub
 (8 comments) (2 reactions) (0 assignees)Go (19,008 forks)batch import
NeedsFixProposal-AcceptedProposal-Cryptohelp wanted

Repository metrics

Stars
 (133,883 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

A bit over a year ago, someone created an issue to add support for RFC 7633 TLS Feature Extension into crypto/tls but it was closed by @agl because he felt it was premature and that OCSP stapling wasn't really supported as a client in Go (not sure if that has changed?).

See #13074

It's been more than a year so I'm creating this issue to see what he thinks of it now.

Contributor guide

Research direction
Study RFC 7633 and Go's crypto/tls package. Examine the previous issue #13074 and understand the current stapling client support. Propose implementation steps.
Tech stack
go
Domain
backendsecurity
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GoTLS/SSLcryptography
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20