RyanSkraba commented on code in PR #3681: URL: https://github.com/apache/avro/pull/3681#discussion_r2910034407
########## 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: I'm thinking about this! I don't want to suggest that adding a layer of input validation or logging in users would solve the problem (and I don't particularly know how to document how to do that!) But we could definitely be a bit more categorical: > The Avro IPC mechanism is intended for use in inter-process communication between trusted components within a controlled and secure network environment. It does not implement input validation, authorization, or authentication mechanisms, and therefore must not be deployed on public networks or made accessible to untrusted clients or services. What do you think? -- 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]
