Skip to content
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

<use_own_name> doesn't work in ossec-logtest #162

Open
mstarks01 opened this issue Mar 25, 2014 · 3 comments
Open

<use_own_name> doesn't work in ossec-logtest #162

mstarks01 opened this issue Mar 25, 2014 · 3 comments
Labels

Comments

@mstarks01
Copy link
Contributor

The <use_own_name> decoder option does not work in ossec-logtest. More info here: https://groups.google.com/forum/#!msg/ossec-list/TtFKNnaA6SA/yWaKXCuV5z4J

@mstarks01 mstarks01 added the bug label Mar 25, 2014
@mstarks01
Copy link
Contributor Author

I don't think this is limited to ossec-logtest. When using
decoded_as in a rule where the decoded_as value is the name of a child decoder that also has use_own_name defined, it does't work. However, if you change the decoded_as element to the parent decoder name, then the rule works.

@ddpbsd
Copy link
Member

ddpbsd commented Mar 26, 2014

I don't remember the use_own_name stuff ever working the way I thought it
should work. So either it's busted or I don't understand it. Either way,
I've ignored it for 4 years.

On Wed, Mar 26, 2014 at 12:58 PM, mstarks01 notifications@github.comwrote:

I don't think this is limited to ossec-logtest. When using
decoded_as in a rule where the decoded_as value is the name of a child
decoder that also has use_own_name defined, it does't work. However, if you
change the decoded_as element to the parent decoder name, then the rule
works.

Reply to this email directly or view it on GitHubhttps://github.com//issues/162#issuecomment-38709849
.

@mstarks01
Copy link
Contributor Author

Yeah, I haven't had a need to focus on IIS logs until recently. I, like many others I'm sure, assumed it "just worked." It looks like it probably never worked.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants