-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sql/tree: the schema names and role/user names are not properly anonymized #55385
Labels
A-security
A-sql-syntax
Issues strictly related to the SQL grammar, with no semantic aspect
C-bug
Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
release-blocker
Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked.
Comments
knz
added
C-bug
Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
A-sql-syntax
Issues strictly related to the SQL grammar, with no semantic aspect
A-security
release-blocker
Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked.
labels
Oct 9, 2020
The code must be changed to use Related (but not identical to) #54696 |
solongordon
added a commit
to solongordon/cockroach
that referenced
this issue
Oct 12, 2020
Schema and owner names were improperly being represented by strings rather than `tree.Name`s in the AST. This meant they would not be properly anonymized in telemetry. Fixes cockroachdb#55385 Release note: None
This applies to ENUM values as well. I'll resolve this in the same PR. |
solongordon
added a commit
to solongordon/cockroach
that referenced
this issue
Oct 13, 2020
Schema and owner names were improperly being represented by strings rather than `tree.Name`s in the AST. This meant they would not be properly anonymized in telemetry. Fixes cockroachdb#55385 Release note: None
solongordon
added a commit
to solongordon/cockroach
that referenced
this issue
Oct 13, 2020
ENUM values were improperly being represented as strings in the AST, which meant that they were not anonymized in telemetry. I created a new AST node type for them which respects anonymization. Fixes cockroachdb#55385 Release note: None
solongordon
added a commit
to solongordon/cockroach
that referenced
this issue
Oct 13, 2020
Schema and owner names were improperly being represented by strings rather than `tree.Name`s in the AST. This meant they would not be properly anonymized in telemetry. Fixes cockroachdb#55385 Release note: None
solongordon
added a commit
to solongordon/cockroach
that referenced
this issue
Oct 13, 2020
ENUM values were improperly being represented as strings in the AST, which meant that they were not anonymized in telemetry. I created a new AST node type for them which respects anonymization. Fixes cockroachdb#55385 Release note: None
solongordon
added a commit
to solongordon/cockroach
that referenced
this issue
Oct 13, 2020
Schema and owner names were improperly being represented by strings rather than `tree.Name`s in the AST. This meant they would not be properly anonymized in telemetry. Fixes cockroachdb#55385 Release note: None
solongordon
added a commit
to solongordon/cockroach
that referenced
this issue
Oct 13, 2020
ENUM values were improperly being represented as strings in the AST, which meant that they were not anonymized in telemetry. I created a new AST node type for them which respects anonymization. Fixes cockroachdb#55385 Release note: None
solongordon
added a commit
to solongordon/cockroach
that referenced
this issue
Oct 13, 2020
ENUM values were improperly being represented as strings in the AST, which meant that they were not anonymized in telemetry. I created a new AST node type for them which respects anonymization. Fixes cockroachdb#55385 Release note: None
craig bot
pushed a commit
that referenced
this issue
Oct 13, 2020
55473: sql: anonymize schema names, owner names, and enum values r=solongordon a=solongordon Schema and owner names were improperly being represented by strings rather than `tree.Name`s in the AST. This meant they would not be properly anonymized in telemetry. ENUM values had the same problem, but we cannot use `tree.Name` in this case because we need the values to be quoted. I created a custom AST node for this case. Fixes #55385 Release note: None Co-authored-by: Solon Gordon <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-security
A-sql-syntax
Issues strictly related to the SQL grammar, with no semantic aspect
C-bug
Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
release-blocker
Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked.
The AST uses the Go type
string
to represent:tree.CreateSchema
This is incorrect: only
tree.Name
is equipped to automatically and properly anonymize the identifiers when constructing telemetry data.With the current code, the telemetry leaks (potentially sensitive) schema names and role names.
cc @solongordon @arulajmani
The text was updated successfully, but these errors were encountered: