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

verbose mode with oscap xccdf remediate doesn't work #520

Closed
ybznek opened this issue Sep 6, 2016 · 5 comments
Closed

verbose mode with oscap xccdf remediate doesn't work #520

ybznek opened this issue Sep 6, 2016 · 5 comments
Assignees
Labels
Milestone

Comments

@ybznek
Copy link
Contributor

ybznek commented Sep 6, 2016

Version:
latest oscap version in Fedora24 & latest upstream maint-1.2

oscap xccdf remediate --verbose INFO --verbose-log-file /tmp/verbose.xml --report /tmp/rep.xml /tmp/res.xml

--verbose parameters are correctly validated, but verbose mode doesn't print anything.

/tmp/verbose.xml doesn't exist after command run, so it seems that verbose mode doesn't work completely for this use case.

@ybznek ybznek added the bug label Sep 6, 2016
@ybznek ybznek added this to the 1.2.11 milestone Sep 6, 2016
@ybznek
Copy link
Contributor Author

ybznek commented Sep 6, 2016

@jan-cerny I haven't already checked the code. Should it work for such use cases?

@jan-cerny
Copy link
Member

@ybznek Verbose mode works only with "oval eval", "oval collect" and "xccdf eval commands". Verbose mode is not allowed together with remediation now. I think it can be implemented easily by enabling those 2 options in appropriate oscap submodule.

@mpreisler
Copy link
Member

mpreisler commented Sep 8, 2016

@jan-cerny I am confused, are you saying that this is or isn't a bug? Looks like a bug to me if the options are accepted but don't enable verbose mode.

EDIT: I would furthermore check all the oscap submodules and made sure verbose mode gets enabled for every single one of them.

@jan-cerny jan-cerny modified the milestones: 1.2.12, 1.2.11 Oct 14, 2016
@mpreisler mpreisler modified the milestones: 1.2.13, 1.2.12 Nov 15, 2016
@mpreisler
Copy link
Member

@jan-cerny Could you please take a look at this one for 1.2.13? Looks like an easy fix.

@rsprudencio
Copy link
Contributor

Please take #603 into consideration. 😄

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

4 participants