I am writing some test code where I am creating `tls.Server()` and `tls.Client()` using the `Conn` pair returned by `net.Pipe()`. I have a few positive tests (where the Handshakes are expected to succeed) and a few negative tests (where the Handshakes are expected to fail). Each test sets up a `tls.Config` pair for a client and a server and runs `server.Handshake()` and `client.Handshake()` in separate goroutines. The positive tests run fine, but the negative tests hang for ever, waiting for the `Handshake()`s to return in both the server and the client goroutines.
I poked around a bit by introducing a timeout and noticed that the client reader contains the following bytes sitting around, waiting to be read: Client: n=7 bytes=[21 3 3 0 2 2 42] These bytes translate to: TLS record type alert `recordTypeAlert` (21), Version TLS 1.2 (3 3), message length `2`, alert type `alertLevelError` (2) and alert reason `alertBadCertificate` (42). This is the exact error an HTTPS server would have returned if I had set this test up using `net/http/httptest`. So my question is, why do the client and server goroutines hang here? Shouldn't these bytes be read and interpreted returning the error to the callers? Is this a bug? Here is the relevant part of the test: https://gist.github.com/madhusudancs/6c248769481e10ab7f2e9f002b007bcc -- Cheers, Madhu -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
