opwvhk commented on code in PR #3681: URL: https://github.com/apache/avro/pull/3681#discussion_r2914867004
########## doc/content/en/project/Security/_index.md: ########## @@ -38,7 +38,8 @@ Security Model The Avro library implementations are designed to read and write any data conforming to a schema. Transport is outside the scope of the Avro library: applications using Avro should be surrounded by security measures that prevent attackers from writing -random data and otherwise interfering with the consumers of schemas. +random data and otherwise interfering with the consumers of schemas. In addition, +the Avro IPC mechanism should not be exposed on a public network to untrusted actors. Review Comment: Using the Avro SASL profile there actually is authentication, though the documentation is very sketchy (to put it mildly). And when reading the code, I see that implementing an authentication method requires non-trivial work. Also, it is not immediately clear how to add encryption. All in all, Avro IPC would benefit from the hardening that @lf- mentions and more documentation. Ideally with a detailed example that uses an SSL connection with DIGEST or OAUTHBEARER authentication. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
