gRPC-Go 1.82
Last reviewed Sep 6, 2026
Prompt Details
Prompt Composition
2prompts
- Go 1.27130 lines · 5.5K tokens
- gRPC-Go 1.8260 lines · 2.5K tokens
Total190 lines · 8K tokens
CWE Coverage
- 15
- 20
- 22
- 59
- 78
- 79
- 89
- 94
- 117
- 190
- 208
- 209
- 250
- 252
- 257
- 287
- 295
- 306
- 307
- 319
- 323
- 327
- 338
- 347
- 352
- 362
- 367
- 378
- 409
- 426
- 444
- 488
- 494
- 532
- 732
- 759
- 770
- 772
- 807
- 862
- 863
- 915
- 916
- 918
- 942
- 1004
- 1275
- 1395
Prompt Preview
Apply the Go 1.27 baseline first. These rules cover google.golang.org/grpc 1.82 clients, servers, credentials, interceptors, protobuf messages, streaming, retries, authorization policy, xDS, and operational services.
Version, transport, and authority
- Take the newest 1.82 patch while you stay on this line, and confirm what the build selects with
go list -m google.golang.org/grpc, since another module's requirement can raise it to a newer minor. gRPC-Go patches the two minor releases before its newest only on demand or for serious security problems, and not every fix is backported, as the receive-buffer rule below shows, so plan the move to a newer minor before this line leaves that window. - Create clients with
grpc.NewClientandgrpc.WithTransportCredentials(credentials.NewTLS(...)); useinsecure.NewCredentials()only on an isolated plaintext transport carrying no credentials or protected data. - Configure client and server
tls.Configwith trusted roots, expected DNS names, and client certificates where service identity is required; never useInsecureSkipVerifywithout an equivalent chain and hostname check inVerifyConnection. Enable server TLS withgrpc.Creds(credentials.NewTLS(...))and a server certificate; for mutual TLS, setClientAuth: tls.RequireAndVerifyClientCertand trustedClientCAs. - Return true from
credentials.PerRPCCredentials.RequireTransportSecurityfor bearer tokens and other reusable secrets, and bound token acquisition with the RPC context. - Accept
grpc.WithAuthorityandgrpc.CallAuthorityvalues only from trusted