Exists This error is because etcd was not cleaned up from the previous run of the example. You can manually fix this by running ./401_teardown.sh, removing vtdataroot and then starting again: Error: 105: Key Key already exists (/vitess/zone1) [6] Error: 105: Key already exists (/vitess/global) [6] MySQL Fails to Initialize This error is most likely the result of SELinux enabled: 1027 18:28:23.462926 19486 mysqld: [ERROR] Failed to open required defaults file: /home/morgo/vitess/vtdataroot/vt_0000000102/my.cnf mysqld: [ERROR] Fatal error in defaults handling. Program aborted! could not stat mysql error log

Exists This error is because etcd was not cleaned up from the previous run of the example. You can manually fix this by running ./401_teardown.sh, removing vtdataroot and then starting again: Error: 105: Key Key already exists (/vitess/zone1) [6] Error: 105: Key already exists (/vitess/global) [6] MySQL Fails to Initialize This error is most likely the result of SELinux enabled: 1027 18:28:23.462926 19486 mysqld: [ERROR] Failed to open required defaults file: /home/morgo/vitess/vtdataroot/vt_0000000102/my.cnf mysqld: [ERROR] Fatal error in defaults handling. Program aborted! could not stat mysql error log

Exists This error is because etcd was not cleaned up from the previous run of the example. You can manually fix this by running ./401_teardown.sh, removing vtdataroot and then starting again: Error: 105: Key Key already exists (/vitess/zone1) [6] Error: 105: Key already exists (/vitess/global) [6] MySQL Fails to Initialize This error is most likely the result of SELinux enabled: 1027 18:28:23.462926 19486 /usr/sbin/mysqld: exit status 1, output: mysqld: [ERROR] Failed to open required defaults file: /home/morgo/vitess/vtdataroot/vt_0000000102/my.cnf mysqld: [ERROR] Fatal error in defaults handling. Program aborted

already is. • Not supported. For these settings, attempting to change them will always result in an error. • Vitess aware. These are settings that change Vitess’ behaviour, and are not sent down to MySQL lc_time_names CheckAndIgnore lock_wait_timeout CheckAndIgnore max_allowed_packet CheckAndIgnore max_error_count CheckAndIgnore max_execution_time CheckAndIgnore max_join_size CheckAndIgnore max_length_for_sort_data Exists This error is because etcd was not cleaned up from the previous run of the example. You can manually fix this by running ./401_teardown.sh, removing vtdataroot and then starting again: Error: 105: Key

already is. • Not supported. For these settings, attempting to change them will always result in an error. • Vitess aware. These are settings that change Vitess’ behaviour, and are not sent down to MySQL lc_time_names CheckAndIgnore lock_wait_timeout CheckAndIgnore max_allowed_packet CheckAndIgnore max_error_count CheckAndIgnore max_execution_time CheckAndIgnore max_join_size CheckAndIgnore max_length_for_sort_data Exists This error is because etcd was not cleaned up from the previous run of the example. You can manually fix this by running ./401_teardown.sh, removing vtdataroot and then starting again: Error: 105: Key

already is. • Not supported. For these settings, attempting to change them will always result in an error. • Vitess aware. These are settings that change Vitess’ behaviour, and are not sent down to MySQL System variable Handled lock_wait_timeout CheckAndIgnore max_allowed_packet CheckAndIgnore max_error_count CheckAndIgnore max_execution_time CheckAndIgnore max_join_size CheckAndIgnore max_length_for_sort_data Exists This error is because etcd was not cleaned up from the previous run of the example. You can manually fix this by running ./401_teardown.sh, removing vtdataroot and then starting again: Error: 105: Key

already is. • Not supported. For these settings, attempting to change them will always result in an error. • Vitess aware. These are settings that change Vitess’ behaviour, and are not sent down to MySQL lc_time_names CheckAndIgnore lock_wait_timeout CheckAndIgnore max_allowed_packet CheckAndIgnore max_error_count CheckAndIgnore max_execution_time CheckAndIgnore max_join_size CheckAndIgnore max_length_for_sort_data Exists This error is because etcd was not cleaned up from the previous run of the example. You can manually fix this by running ./401_teardown.sh, removing vtdataroot and then starting again: Error: 105: Key

already is. • Not supported. For these settings, attempting to change them will always result in an error. • Vitess aware. These are settings that change Vitess’ behaviour, and are not sent down to MySQL lc_time_names CheckAndIgnore lock_wait_timeout CheckAndIgnore max_allowed_packet CheckAndIgnore max_error_count CheckAndIgnore max_execution_time CheckAndIgnore max_join_size CheckAndIgnore max_length_for_sort_data Exists This error is because etcd was not cleaned up from the previous run of the example. You can manually fix this by running ./401_teardown.sh, removing vtdataroot and then starting again: Error: 105: Key

GetClusters(ctx context.Context, req *vtadminpb.GetClustersRequest) (*vtadminpb.GetClustersResponse, error) { span, _ := trace.NewSpan(ctx, "API.GetClusters") defer span.Finish() clusters, _ := api.getC elevated their privileges. The root cause of such an attack scenario is likely to be an implementation error. The role of VTAdmin and Vitess’s attack surface VTAdmin adds a new, more granular user access control 740737b79/g o/vt/vtgate/vindexes/hash.go#L139 var blockDES cipher.Block func init() { var err error blockDES, err = des.NewCipher(make([]byte, 8)) if err != nil { panic(err) } Register("hash", NewHash)

disclosure of personally identifiable information (PII), particularly in rarely encountered error cases. Additionally, the deployment infrastructure was further investigated for generalizable Affected Code: func (a *AuthServerStatic) Negotiate(c *Conn, user string, remoteAddr net.Addr) (Getter, error) { [...] for _, entry := range entries { // Validate the password. if matchSourceHost(remoteAddr