It is technically possible, but not part of gRPC API guarantees at the moment. If you did implement your own security, you would need to make sure it stays up to date with the internal gRPC APIs.
One alternative you could do is run a local proxy, which accepts plaintext grpc in and uses security going one. Then you could use gRPC to connect to the encrypting proxy without depending on the internals API. On Monday, December 4, 2017 at 10:03:19 AM UTC-8, aaj...@gmail.com wrote: > > Is there a way to set custom transport security other than SSL? > > I saw this post https://github.com/grpc/grpc/issues/9985 but it wasn't > particularly helpful. > > > I have browsed through the source of gRPC a bit and see what appears to be > a generic handshake mechanism that looks promising but it would take a > while to comprehend. If I wanted to use something other than SSL for > encryption (e.g. a key exchange algorithm) how would I go about doing it? > Follow up question, can a custom handshake implementation be used with the > C++ abstractions? > > 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 grpc-io+unsubscr...@googlegroups.com. To post to this group, send email to grpc-io@googlegroups.com. Visit this group at https://groups.google.com/group/grpc-io. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/320a9317-c681-4867-87c4-adb15df4dd28%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
