for such functions interacting with the file system would be ExecuteHook. This item was analyzed in depth to see if it is by any means possible to inject API commands. The overarching goal was clearly to circumvention were found. • A potential timing issue pointed out by the development team was investigated in-depth but revealed no readily available exploitation paths. The reason behind the secure premise is stored password hash (e.g. via SQL injection), a timing attack can be performed by xoring the tested bit with sha1(salt + sha1(sha1(pw)). By exploiting the timing-unsafe comparison, an attacker would be able

NotSupported innodb_ft_user_stopword_table NotSupported max_points_in_geometry NotSupported max_sp_recursion_depth NotSupported myisam_repair_threads NotSupported myisam_sort_buffer_size NotSupported myisam_stats_method min_examined_row_limit ReservedConn old_passwords ReservedConn optimizer_prune_level ReservedConn optimizer_search_depth ReservedConn optimizer_switch ReservedConn optimizer_trace ReservedConn optimizer_trace_features ReservedConn that all numbers less than 0x8000000000000000 will fall in shard -80. Any number with the highest bit set will be >= 0x8000000000000000, and will therefore belong to shard 80-. This left-justified approach

NotSupported innodb_ft_user_stopword_table NotSupported max_points_in_geometry NotSupported max_sp_recursion_depth NotSupported myisam_repair_threads NotSupported myisam_sort_buffer_size NotSupported myisam_stats_method min_examined_row_limit ReservedConn old_passwords ReservedConn optimizer_prune_level ReservedConn optimizer_search_depth ReservedConn optimizer_switch ReservedConn optimizer_trace ReservedConn optimizer_trace_features ReservedConn that all numbers less than 0x8000000000000000 will fall in shard -80. Any number with the highest bit set will be >= 0x8000000000000000, and will therefore belong to shard 80-. This left-justified approach

NotSupported innodb_ft_user_stopword_table NotSupported max_points_in_geometry NotSupported max_sp_recursion_depth NotSupported myisam_repair_threads NotSupported myisam_sort_buffer_size NotSupported myisam_stats_method min_examined_row_limit ReservedConn old_passwords ReservedConn optimizer_prune_level ReservedConn optimizer_search_depth ReservedConn optimizer_switch ReservedConn optimizer_trace ReservedConn optimizer_trace_features ReservedConn type vindex produces an unsigned 64 bit integer as output. This means that all integers less than 0x8000000000000000 will fall in shard -80. Any number with the highest bit set will be >= 0x8000000000000000

innodb_ft_user_stopword_table NotSupported max_points_in_geometry NotSupported max_sp_recursion_depth NotSupported myisam_repair_threads NotSupported myisam_sort_buffer_size NotSupported myisam_stats_method min_examined_row_limit ReservedConn old_passwords ReservedConn optimizer_prune_level ReservedConn optimizer_search_depth ReservedConn optimizer_switch ReservedConn optimizer_trace ReservedConn optimizer_trace_features ReservedConn type vindex produces an unsigned 64 bit integer as output. This means that all integers less than 0x8000000000000000 will fall in shard -80. Any number with the highest bit set will be >= 0x8000000000000000

NotSupported innodb_ft_user_stopword_table NotSupported max_points_in_geometry NotSupported max_sp_recursion_depth NotSupported myisam_repair_threads NotSupported myisam_sort_buffer_size NotSupported myisam_stats_method min_examined_row_limit ReservedConn old_passwords ReservedConn optimizer_prune_level ReservedConn optimizer_search_depth ReservedConn optimizer_switch ReservedConn optimizer_trace ReservedConn optimizer_trace_features ReservedConn type vindex produces an unsigned 64 bit integer as output. This means that all integers less than 0x8000000000000000 will fall in shard -80. Any number with the highest bit set will be >= 0x8000000000000000

receive and apply events from the binlog. A user can apply filtering rules to a VStream to obtain in depth information about what is going on under the hood at a given keyspace, shard, and position. For reference that all numbers less than 0x8000000000000000 will fall in shard -80. Any number with the highest bit set will be >= 0x8000000000000000, and will therefore belong to shard 80-. 35 This left-justified above case, we are essentially creating two shards: any keyspace id that does not have its leftmost bit set will go to -80. All others will go to 80-. Applying the above change should result in the creation

that all numbers less than 0x8000000000000000 will fall in shard -80. Any number with the highest bit set will be >= 0x8000000000000000, and will therefore belong to shard 80-. This left-justified approach instance shards, and then apply it to a target instance. An user can leverage VStream to obtain in-depth information about data change events for given Vitess keyspace, shard, and position. A single VStream solved by multi-master: • Scalability: There are situations where multi-master gives you a little bit of additional runway. However, since the statements have to eventually be applied to all masters, it’s

that all numbers less than 0x8000000000000000 will fall in shard -80. Any number with the highest bit set will be >= 0x8000000000000000, and will therefore belong to shard 80-. This left-justified approach instance shards, and then apply it to a target instance. An user can leverage VStream to obtain in-depth information about data change events for given Vitess keyspace, shard, and position. A single VStream solved by multi-master: • Scalability: There are situations where multi-master gives you a little bit of additional runway. However, since the statements have to eventually be applied to all masters, it’s