On Thu, Nov 9, 2017 at 6:13 PM, <[email protected]> wrote: > By looking at this thread > <https://www.mail-archive.com/[email protected]/msg01161.html>, it > seems that the python client requires a secure channel to send credentials. >
Yes, this was a deliberate decision and I think there's even logic in gRPC Core to prevent the accidental transmission of clients over unsecured channels. This is not the case in golang (it is an option > <https://github.com/grpc/grpc-go/blob/master/credentials/credentials.go#L42> > ). > > Is there any workaround in python for this? > There is no currently-supported workaround and... I'm not even sure I could come up with an unsupported workaround. Are there any plans to support it with an interface like the one defined in > go? > There are no such plans at this time. Can you tell us more about your use case? -Nathaniel -- 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/CAEOYnAQ1rJtODJ2j1ZGunzyWE0EGOfA3RQXALDRvOQy6d8xPmg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
smime.p7s
Description: S/MIME Cryptographic Signature
