bvolpato commented on PR #29206: URL: https://github.com/apache/beam/pull/29206#issuecomment-1789950379
> It looks like the threat model is the publisher of a message is the adversary and the deserializer, right? So if we have no easy option than deprecating/ceaveating it and leaving it in the repo maybe that is manageable. I don't know if there is standard practice in this case. Just the publisher (connection to broker) if I understand it correctly. An attacker can serialize a class that gets into the class loader (therefore, can execute static blocks) on the broker. -- 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]
