Explain that UDF security manager will be coming in 3.0

This commit is contained in:
Jonathan Ellis 2015-05-27 17:02:01 -05:00
parent 7aafe053e7
commit 61bea5a0d9
2 changed files with 12 additions and 5 deletions

View File

@ -53,9 +53,14 @@ New features
been added to CQL.
************************************************************************
IMPORTANT NOTE: user-defined functions can be used to execute
arbitrary and possibly evil code in Cassandra 2.2-beta1.
To enable UDFs edit cassandra.yaml and set enable_user_defined_functions
to true. CASSANDRA-9402 will add a security manager for UDFs.
arbitrary and possibly evil code in Cassandra 2.2, and are
therefore disabled by default. To enable UDFs edit
cassandra.yaml and set enable_user_defined_functions to true.
CASSANDRA-9402 will add a security manager for UDFs in Cassandra
3.0. This will inherently be backwards-incompatible with any 2.2
UDF that perform insecure operations such as opening a socket or
writing to the filesystem.
************************************************************************
- Row-cache is now fully off-heap.
- jemalloc is now automatically preloaded and used on Linux and OS-X if

View File

@ -845,6 +845,8 @@ tracetype_query_ttl: 86400
tracetype_repair_ttl: 604800
# UDFs (user defined functions) are disabled by default.
# As of Cassandra 2.2-beta1, there is no security manager or anything else in place that
# prevents execution of evil code. CASSANDRA-9402 will fix this issue for Cassandra 2.2-rc1.
# As of Cassandra 2.2, there is no security manager or anything else in place that
# prevents execution of evil code. CASSANDRA-9402 will fix this issue for Cassandra 3.0.
# This will inherently be backwards-incompatible with any 2.2 UDF that perform insecure
# operations such as opening a socket or writing to the filesystem.
enable_user_defined_functions: false