TLS gRPC tests timing out

[tobert]

Description

Two TLS-related gRPC tests are timing out consistently:

1. minimum configuration (tls, no-verify, recording, grpc)
2. minimum configuration (tls, client cert auth, recording, grpc)

Test Output

main_test.go:533: [minimum configuration (tls, no-verify, recording, grpc)] timeout, killing process...
main_test.go:555: [minimum configuration (tls, no-verify, recording, grpc)] command exited: signal: killed
main_test.go:204: [minimum configuration (tls, no-verify, recording, grpc)] test timeout status is true but expected false

main_test.go:533: [minimum configuration (tls, client cert auth, recording, grpc)] timeout, killing process...
main_test.go:555: [minimum configuration (tls, client cert auth, recording, grpc)] command exited: signal: killed
main_test.go:204: [minimum configuration (tls, client cert auth, recording, grpc)] test timeout status is true but expected false

Notes

• The equivalent HTTPS tests pass successfully
• This appears to be specific to TLS over gRPC
• Discovered while adding logs support (PR coming)

To Reproduce

go build && go test

[tobert]

Root Cause Identified

The issue is a fundamental mismatch between how gRPC and HTTP handle TLS:

HTTP/HTTPS: TLS is handled entirely by the listener. An HTTP server works fine with a TLS listener.

gRPC: TLS requires both:

1. TLS credentials configured in the gRPC server itself via grpc.Creds()
2. OR a TLS listener (but this doesn't work properly without server credentials)

Current code (grpcserver.go:45):

server: grpc.NewServer(),  // insecure server

The problem: Tests create a TLS listener and pass it to an insecure gRPC server. This causes a protocol mismatch - the listener expects TLS handshake but the server doesn't perform one.

Solution: The gRPC server needs to be created with TLS credentials when TLS is required:

creds := credentials.NewTLS(tlsConfig)
server: grpc.NewServer(grpc.Creds(creds))

However, this requires refactoring NewGrpcServer to accept TLS configuration, which is a significant change to the test harness and potentially the server command.

🤖 Claude claude@anthropic.com