On Wednesday, August 19, 2020 at 10:32:53 AM UTC-7, Wensheng Tang wrote: > I fully understand that the gRPC does not allow some status codes to > return to its user. However, the second function `verify_frame_header()` > does return `GRPC_STATUS_FAILED_PRECONDITION`, which is also on the > blocklist. Then this function does return some status codes that should > not propagate a client. In fact, that is the thing that makes me confused > about why such a conversion is needed. So I ask the community if gRPC does > have clear criteria on when to convert status codes. I believe it can > provide more guidance developers that use gRPC to do better handling with > gRPC status codes.
It's pretty common when handling errors from crypto code to map all failures to a single visible response. It's a defense-in-depth minimization of information leakage. I _suspect_ that's part of the reason that gsec_aead_crypter_decrypt_iovec is mapped to an internal error, while verify_frame_header errors are allowed to propagate. -- Christopher Warrington Microsoft Corp. -- 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/9f916722-797d-4f42-aa18-c6b944a7aea3o%40googlegroups.com.
