C# grpc server considered safe for facing public internet?

[p...@configit.com]

After reading a bit about the need to put the new Kestrel webserver behind a reverse proxy, i was wondering whether a grpc server is expected to be safe to expose as a public endpoint? I would hope so, since one use case is using it from mobile apps, but just want to be sure :)

[Jan Tattermusch]

Yes, it should be safe to expose gRPC C# as a public endpoint, but it obviously depends on you use case and the level of security/stability you are looking for. The key pieces of gRPC C# (the serving logic, authentication, encryption) is based on gRPC C core, which is intended to be safe to use as a public endpoint. On the other hand, we haven't really done any extensive testing with gRPC C# to be sure it is absolutely bulletproof. I think one could pull off a DoS attact against a gRPC C# server (but DoS is hard to prevent without a more sophisticated serving infrastructure anyway), but your data should be safe.

On Fri, Apr 21, 2017 at 7:44 AM, <p...@configit.com> wrote:

After reading a bit about the need to put the new Kestrel webserver behind a reverse proxy, i was wondering whether a grpc server is expected to be safe to expose as a public endpoint? I would hope so, since one use case is using it from mobile apps, but just want to be sure :)

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to grp...@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/e16f4d76-4442-41a0-b0f4-3261203518eb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.