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
[dev.icinga.com #6690] Support filter expressions for searching #848
Comments
Updated by elippmann on 2014-07-15 08:28:52 +00:00
|
Updated by tgelf on 2014-07-31 16:51:55 +00:00
No, it isn't. What happens here is that the search is treated as a filter expression. This is wrong, but not dangerous. In your example it treats the string on the right side of the pipe as a boolean column named " *". It checks whether the DataView has such and complains as it doesn't. Searching for ping|host=net would lead to success - but is still not exploitable in any way. I'll fix this. Best, |
Updated by tgelf on 2014-07-31 17:01:58 +00:00 While thinking about it instead of "fixing it" we could consider this a feature. Who uses |, &, =, >, ( etc wants to type a filter expression, doesn't he? So why not allowing one to do so? If such operator is found, no *-magic should happen to get filters working as expected. |
Updated by elippmann on 2015-03-31 08:23:34 +00:00
|
Updated by jmeyer on 2015-06-11 07:50:54 +00:00
|
Updated by elippmann on 2015-07-17 09:48:01 +00:00
|
Updated by elippmann on 2015-08-31 09:12:20 +00:00
|
Updated by elippmann on 2015-11-09 10:18:18 +00:00
|
Updated by jmeyer on 2016-11-03 10:14:24 +00:00
|
@nilmerg this looks fixed or at least changed? :-) |
Not that I'm aware of. Note that this is about the global search. |
This issue has been migrated from Redmine: https://dev.icinga.com/issues/6690
Created by jmeyer on 2014-07-10 12:06:03 +00:00
Assignee: (none)
Status: New
Target Version: (none)
Last Update: 2015-11-09 10:18:18 +00:00 (in Redmine)
Attachments
Parent Task: #9479
Relations:
The text was updated successfully, but these errors were encountered: