crypto/tls: optional ocspStapling

[brad-burch]

go version go1.3

I have a server outside my control that fails to respond properly when OSCP stapling is
enabled and causes a "tls: received unexpected handshake message..." error.

I would like to be able to set a tls.Config{} option to disable OSCP stapling instead of
recompiling the package.  I am attaching the rudimentary patch I have been compiling
into crypto/tls.

Attachments:

1. DisableOSCPStapling.patch (1166 bytes)

[griesemer]

Comment 1:

Labels changed: added release-none, repo-crypto.

[brad-burch]

go version go1.4rc2

Attaching a different patch which resolves my issue and follows the wording in RFC4366 more precisely.

https://gist.github.com/brad-burch/148a7dfe258c3e6fd68f

[mberhault]

Any movement on this? It has caused some confusion on this stack overflow question. Given that the patch proposes to accurately implement the RFC, is there any downside in integrating it?

[bradfitz]

@mberhault, any movement would be reflected in this bug, so I would say there's been no movement. And no patch was formally sent via https://golang.org/doc/contribute.html

@agl, any opinion on making OCSP stapling optional?