Closed kclinden closed 5 years ago
Attached are the following files in a zip file. esxi-files.zip
metadata.json
DoD-DISA-logos-as-JPEG.jpg
STIG_unclass.xsl
U_VMware_vSphere_6-5_ESXi_STIG_V1R1_Manual-xccdf.xml
Great. Thankyou. @samcornwell can you take a peek.
@kclinden I'm having a hard time reproducing this. I am unable to recreate your configuration because apparently InSpec 4.3.2 requires ruby >= 2.4. Can you do me a favor and show me the output of gem list | grep inspec
? I'm wondering if inspec_tools
is using an older version of inspec.
I used homebrew to install inspec and brew-gem to install inspec_tools.
If I run brew cask info inspec
, I get the following:
klinden-a02:~ klinden$ brew cask info inspec
inspec: 4.3.2
https://www.inspec.io/
/usr/local/Caskroom/inspec/4.3.2 (2 files, 25.4MB)
From: https://github.com/chef/homebrew-chef/blob/master/Casks/inspec.rb
==> Name
InSpec by Chef
==> Artifacts
inspec-4.3.2-1.pkg (Pkg)
I linked the latest version of ruby with homebrew vs the default OS version and got the same error.
ruby 2.6.3p62 (2019-04-16 revision 67580) [x86_64-darwin18]
I ended up installing rvm, then ruby and inspec/inspec_tools to get this to work. It must have been something to do with the version like you mentioned.
Aaron Lippold
lippold@gmail.com
260-255-4779
twitter/aim/yahoo,etc. 'aaronlippold'
On Mon, Jun 17, 2019 at 7:48 PM Kasey Linden notifications@github.com wrote:
I ended up installing rvm, then ruby and inspec/inspec_tools to get this to work. It must have been something to do with the version like you mentioned.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/mitre/inspec_tools/issues/63?email_source=notifications&email_token=AALK42CGEMAAY3YCF5AB4J3P3APEPA5CNFSM4HYNV3P2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODX4YGYY#issuecomment-502891363, or mute the thread https://github.com/notifications/unsubscribe-auth/AALK42D5HCXTTASHGUZ7JXTP3APEPANCNFSM4HYNV3PQ .
@aaronlippold I don't think this has anything to do with that. I think I know how to fix the error he was having originally, but had no way to test it first. I'm just going to make the fix and submit it as a PR. It just involves adding some more explicit require
statements.
So I am running into this issue again with the csv2inspec command. I am trying to avoid using rvm this time.
xccdf2inspec fails with the below error.
Command
xccdf2inspec fails with the following command.
Error