janhoy commented on PR #4320: URL: https://github.com/apache/solr/pull/4320#issuecomment-4435458227
> employ a Java agent, but I'm unsure if we should lean on that alone here. I'm going to start implementation on [SIP-24](https://cwiki.apache.org/confluence/display/SOLR/SIP-24%3A+Java+Security+Manager+replacement) tomorrow, and it will prevent any outbound HTTP traffic that is not explicitly allowed. There will also be an "override" policy file where admins can add allow-rules for cases like this. It is very error prone and fragile to rely on devs remembering for all future changes to always add explicit checks on every single call site. That's why I propose to deprecate `SolrPaths.assertPathAllowed()` and keep all enforcement centralized in the agent. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
