In https://github.com/golang/go/issues/51434 a shim for the BoringSSL BoGo test suite, and a unit test to drive it, were added to crypto/tls. See bogo_shim_test.go. To limit the scope of that initial work many tests were disabled in the associated JSON config.

To maximize the value of this test shim we should work through this list and either provide a clear reason for why skipping the test makes sense based on some additional context (missing features, protocol ambiguity, etc) or implement the required fixes to enable the test.

Comment From: gopherbot

Change https://go.dev/cl/650715 mentions this issue: crypto/tls: small bogo shim test tidying

Comment From: gopherbot

Change https://go.dev/cl/650735 mentions this issue: crypto/tls: reject empty TLS13 session ticket

Comment From: gopherbot

Change https://go.dev/cl/650735 mentions this issue: crypto/tls: reject empty TLS 1.3 session ticket

Comment From: gopherbot

Change https://go.dev/cl/650736 mentions this issue: crypto/tls: run SkipNewSessionTicket bogo test

Comment From: gopherbot

Change https://go.dev/cl/650716 mentions this issue: crypto/tls: ignore TLS 1.3 user canceled alerts

Comment From: gabyhelp

Related Issues

Related Code Changes

(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)

Comment From: gopherbot

Change https://go.dev/cl/650737 mentions this issue: crypto/tls: support bogo -wait-for-debugger

Comment From: gopherbot

Change https://go.dev/cl/650717 mentions this issue: crypto/tls: update GREASE-Server-TLS13 BoGo skip

Comment From: gopherbot

Change https://go.dev/cl/652995 mentions this issue: crypto/tls: align cert decode alert w/ BSSL

Comment From: gopherbot

Change https://go.dev/cl/650738 mentions this issue: crypto/tls: add support for cipher flags to bogo_shim_test

Comment From: gopherbot

Change https://go.dev/cl/652997 mentions this issue: crypto/tls: reject TLS 1.3 compat session ID in TLS 1.2

Comment From: ledlightjungledStefan

Before signing in to GitHub, read the linked issue To read it a second time, I have to open the link again ( . . . replace the binding with an underscore. . .) I use round brackets in this case; it could be a folder name Windows is used with brackets to move folders named with, for example, square brackets above text folder names. The command ResumeShimWritesFirst is not resolved in the label text processed. Obviously, why not? Here in the markdown text also not, ok. Why should the command be resolved in view? Why should the text be viewed inline with a process? Assumption:To prevent confusion?

leoDOTorg in German conventional letter The binding, a conventional letter, is bound and has to be replaced. Assumption:one, more or none

With the site link https://go.dev/doc/install The site content has a button that leads only to the issue GitHub page.

I need a ticket.

Comment From: gopherbot

Change https://go.dev/cl/669175 mentions this issue: crypto/tls: skip BadRSAClientKeyExchange-[4,5]

Comment From: gopherbot

Change https://go.dev/cl/669156 mentions this issue: crypto/tls: update TLS 1.3 client compression validation

Comment From: gopherbot

Change https://go.dev/cl/669158 mentions this issue: crypto/tls: enable more large record bogo tests

Comment From: gopherbot

Change https://go.dev/cl/669155 mentions this issue: crypto/tls: use illegal param alert for bad compression

Comment From: gopherbot

Change https://go.dev/cl/669157 mentions this issue: crypto/tls: err for unsupported point format configs

Comment From: gopherbot

Change https://go.dev/cl/671195 mentions this issue: crypto/tls: fix TLS <1.3 client cert required alert

Comment From: gopherbot

Change https://go.dev/cl/671235 mentions this issue: crypto/tls: handle client hello version too high

Comment From: ledlightjungledStefan

"Filing a Ticket" button: comment: has the filing a ticket button ever been in use?

Comment From: ledlightjungledStefan

The sentence includes... by filing a ticket on our issue tracker.

For. . . , even if ClientHello.legacy_version is 0x0304 or later.

This commit updates the client hello processing logic to allow this behaviour.

... processing - the behaviour could be that the sentence is a readable text content.

The word client is without ampersands for readability as a proofreader because it is not shortcutted to a Webassambly token. It does not update the client hello handshake. It updates the logic without a stable written event?

For a read and write commit change if TLS 1.3 is not in use. What is it at all? It does not update process logic.

Comment From: ledlightjungledStefan

This commit this behaviour updates

the client hello logic

Comment From: ledlightjungledStefan

I am a host, and the services on a server are set as text to the client without a web assembly token.

Comment From: gopherbot

Change https://go.dev/cl/671415 mentions this issue: crypto/tls: fix bogo IgnoreClientVersionOrder skip reason

Comment From: gopherbot

Change https://go.dev/cl/673236 mentions this issue: crypto/tls: have servers prefer TLS 1.3 when supported

Comment From: gopherbot

Change https://go.dev/cl/673736 mentions this issue: crypto/tls: match compression method alert across versions

Comment From: gopherbot

Change https://go.dev/cl/673735 mentions this issue: crypto/tls: verify server chooses advertised curve

Comment From: gopherbot

Change https://go.dev/cl/673756 mentions this issue: crypto/tls: enable BoGo DisabledCurve-HelloRetryRequest-TLS13

Comment From: gopherbot

Change https://go.dev/cl/673737 mentions this issue: crypto/tls: update BoGo SessionID test skip reasons

Comment From: gopherbot

Change https://go.dev/cl/673757 mentions this issue: crypto/tls: reject duplicate TLS 1.3 EncryptedExtensions

Comment From: gopherbot

Change https://go.dev/cl/673738 mentions this issue: crypto/tls: use decode alert for handshake msg unmarshal err

Comment From: ledlightjungledStefan

Hello. My investigations on the crime scene on the Internet are concluded with a so-called mass. "Are all related keys with the symbol $ used with at least the upper part of an iceberg"?

The mentioned interpolation key is not to introduce variable spaces for personal word creations. Comments, explanations, and functions with books are only suitable if they fit like a jigsaw puzzle. To use a variable name with a variable format container or contained sums up to be integrated into something, interpolated, between brackets.

The tutorial for GO!lang does not mention that with a Windows installation, the interpolation symbol turns the cmd not into a bash. The Windows CMD does not use $ for GO!lang development. Just in case a tutorial is not a tutorial. Something else.

Comment From: gopherbot

Change https://go.dev/cl/683456 mentions this issue: crypto/tls: update bogo version