regex_policy patterns are case-senstive
Bug #956153 reported by
Daniel Nichter
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Drizzle |
Confirmed
|
Undecided
|
Vladimir Cernov |
Bug Description
regex_policy plugin patterns are case-senstive but Drizzle is not case-senstive.
To reproduce:
1. create schema daniel
2. Use policy "daniel schema=daniel ACCEPT"
3. Login user=daniel and schema appears, OK, but...
4. Use policy "daniel schema=DANIEL ACCEPT" _or_ "DANIEL schema=daniel ACCEPT"
5. Login user=daniel and schema does not appear
Suggested fix: make all patterns case-insenstive by default. Maybe add an option: --regex-
Partial workaround:
daniel schema=daniel ACCEPT
daniel schema=DANIEL ACCEPT
That doesn't cover schema=Daniel, schema=DaNiEl, etc.
Changed in drizzle: | |
assignee: | nobody → Vladimir Cernov (cernov-vladimir) |
To post a comment you must log in.
Seems like you could indeed just transform all the regexps to case insensitive, since all objects are that too. I don't think an option is even needed. (Or can be added later.)
This is clearly low-hanging-fruit