alamb opened a new issue, #26061: URL: https://github.com/apache/datafusion/issues/26061
I added an initial security policy in this PR - https://github.com/apache/datafusion/pull/25917 @samueleresca noted (❤️ ) in https://github.com/apache/datafusion/issues/25917#issuecomment-5980840704 that it would be helpful to add additional documentation on how to harden DataFusion from threats by explicitly state the configurations that contribute to security hardening and their default. For example, DuckDB [does something similar in their operations manual](https://duckdb.org/docs/current/operations_manual/securing_duckdb/overview#settings-to-limit-duckdbs-capabilities). Some corresponding examples in the DataFusion domain from @samueleresca: - `SQLOptions` and `with_allow_ddl`, `with_allow_dml`, `with_allow_statements` are all allowed by default, as already mentioned. - [SessionContext::enable_url_table](https://docs.rs/datafusion/latest/datafusion/execution/context/struct.SessionContext.html#method.enable_url_table) - No memory limits by default (e.g., [UnboundedMemoryPool](https://docs.rs/datafusion/latest/datafusion/execution/memory_pool/trait.MemoryPool.html#implementing-memorypool)) He suggested > The stuff above might go in a dedicated section on the already existing [Config page](https://datafusion.apache.org/user-guide/configs.html#). I would personally suggest adding a new page in our library user guide here: - https://datafusion.apache.org/library-user-guide/index.html -- 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]
