I have checked the binaries, and they are 32-bit ones. So, architecture doesn’t
seem to be a problem.
Even my guess is it is related to the compiler options.
If there is a oscap msi/exe version that is compiled with flags to support
older windows versions, it will help. In case if anybody has
Thanks for reply, Watson…
I’m using the SCAP contents from the OVAL CIS repository.
And, yes I have already tried on a Linux box and the performance over there is
much better.
Regards,
Bharath M
From: Watson Sato
Sent: Thursday, December 20, 2018 9:06 PM
To: Mohanraj, Bharath
Cc: open-scap-l
On Wed, Nov 28, 2018 at 11:47 PM Mohanraj, Bharath <
bharath_mohanraj...@bmc.com> wrote:
> Hi Team,
>
> I'm evaluating oscap 1.3.0 on windows, and I have a query on the same.
>
> I'm trying to evaluate definitions on a Win 10 box and I see that the
> operation takes 1-3 minutes for each definition
Hi Team,
I'm evaluating oscap 1.3.0 on windows, and I have a query on the same.
Unfortunately, in my environment there are few boxes still running in older
windows platforms like XP. When I tried to run "oscap.exe -h", it throws me an
error saying "oscap.exe is not a valid win 32 application".
