This feature is not supported in gRPC c core right now. I have created an issue for tracking this feature. https://github.com/grpc/grpc/issues/14216
On Friday, January 26, 2018 at 12:04:37 PM UTC-8, [email protected] wrote: > > They keys are in PEM format. I'm unsure if they were converted from PKCS12 > prior to that. > > On Friday, 5 January 2018 10:35:58 UTC-8, Carl Mastrangelo wrote: >> >> And just to clarify, I think you are talking about PKCS 12 for the key >> encryption? I am more familiar with Java so my experience is limitted. >> That said, in Java you can pass a keystore into into your SSL context when >> creating the Server (or channel). Also IIRC, Go got support for >> encrypted keys a while back. >> >> On Thursday, January 4, 2018 at 4:45:53 PM UTC-8, [email protected] >> wrote: >>> >>> For my needs specifically, C++, though ideally this would be supported >>> across all languages as part of general SSL support in gRPC. >>> >>> On Thursday, 4 January 2018 16:37:40 UTC-8, Carl Mastrangelo wrote: >>>> >>>> What language? >>>> >>>> On Tuesday, December 19, 2017 at 10:23:54 AM UTC-8, [email protected] >>>> wrote: >>>>> >>>>> Looking to use SSL in my client application. The SSL keys we use are >>>>> often passphrase encrypted. Libcurl supports passing in the passphrase as >>>>> an option, but I've been unable to find any such option in gRPC. >>>>> >>>> -- 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 post to this group, send email to [email protected]. 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/933a1e80-3599-4180-85f8-31b954a26a27%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
