It might be interesting to follow the conversation in https://github.com/grpc/grpc/pull/10529, which explains some of the motivation for why this is discouraged in production.
On Wednesday, May 1, 2019 at 11:06:26 PM UTC-7, [email protected] wrote: > > Yes this seems to solve the problem, but the comments say: >> >> should never be used in production > > > What is the reason? > Is this option unsafe or unstable? > > Thanks > Guido > > On Wednesday, May 1, 2019 at 7:21:39 PM UTC+2, Muxi Yan wrote: >> >> This is probably what you are looking for: >> https://github.com/grpc/grpc/blob/7bf82de9eda0aa8fecfe5edb33834f1b272be30b/include/grpcpp/support/channel_arguments_impl.h#L66 >> >> On Tuesday, April 30, 2019 at 6:27:09 AM UTC-7, [email protected] wrote: >>> >>> Is it possible in GRPC C++ to separate the endpoint used in the TCP >>> connection from the server name that is verified by SSL? >>> >>> The simple case for an SSL client connection setup is this: >>> >>> auto channel = grpc::CreateChannel("myhost.domain:50051", grpc:: >>>> SslCredentials(grpc::SslCredentialsOptions())); >>>> >>>> >>> The host name "myhost.domain" is used to make the TCP connection and is >>> used by SSL to verify the servers certificate. >>> >>> I would like to connect to a TCP address as endpoint (e.g. " >>> 10.1.2.3:50051") and to let SSL verify that the server name in the >>> certificate is "myhost.domain". >>> Is this possible and how ? >>> >>> Thanks >>> >> -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/c4d0d9f1-38f9-45ff-ae04-a96677428325%40googlegroups.com.
