You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the server requires a client certificate, and grpcurl is not configured with the -cert/-key options, it fails with a timeout instead of an explicit message, even though the server communicates the problem with a certificate_requiredalert and closes the connection.
Steps to reproduce: create a server that requires a client certificate (for example by modifying the grpc-go authentication to pass a tls.Config with tls.RequireAndVerifyClientCert).
Run grpcurl -insecure localhost:50051 list
Expected output (this is what grpc-go outputs when letting an RPC fail or dialing WithBlock):
Failed to dial target host "localhost:50051": desc = "error reading server preface: remote error: tls: certificate required
Actual output:
Failed to dial target host "localhost:50051": context deadline exceeded
grpcurl seems to not consider the alert fatal and continue attempting to dial.
The text was updated successfully, but these errors were encountered:
When the server requires a client certificate, and
grpcurl
is not configured with the-cert/-key
options, it fails with a timeout instead of an explicit message, even though the server communicates the problem with acertificate_required
alert and closes the connection.tls.Config
withtls.RequireAndVerifyClientCert
).Expected output (this is what grpc-go outputs when letting an RPC fail or dialing
WithBlock
):Actual output:
grpcurl seems to not consider the alert fatal and continue attempting to dial.
The text was updated successfully, but these errors were encountered: