-
Notifications
You must be signed in to change notification settings - Fork 44
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
Profile fails inspec json
#33
Comments
I recommend going with encoding, any PR to make it happen is welcome. |
james-stocks
pushed a commit
to james-stocks/nginx-baseline
that referenced
this issue
May 21, 2019
Fixes dev-sec#33 There are a number of issues open and closed for encoding in InSpec profiles https://github.com/inspec/inspec/issues?utf8=%E2%9C%93&q=is%3Aissue+encoding To work in all versions of InSpec currently supported, this profile should keep the `# encoding: UTF-8` declaration. Signed-off-by: James Stocks <jstocks@chef.io>
james-stocks
pushed a commit
to james-stocks/nginx-baseline
that referenced
this issue
May 21, 2019
Fixes dev-sec#33 There are a number of issues open and closed for encoding in InSpec profiles https://github.com/inspec/inspec/issues?utf8=%E2%9C%93&q=is%3Aissue+encoding To work in all versions of InSpec currently supported, this profile should keep the `# encoding: UTF-8` declaration. Signed-off-by: James Stocks <jstocks@chef.io>
chris-rock
pushed a commit
that referenced
this issue
May 21, 2019
Fixes #33 There are a number of issues open and closed for encoding in InSpec profiles https://github.com/inspec/inspec/issues?utf8=%E2%9C%93&q=is%3Aissue+encoding To work in all versions of InSpec currently supported, this profile should keep the `# encoding: UTF-8` declaration. Signed-off-by: James Stocks <jstocks@chef.io>
I raised an InSpec issue with a small reproduction profile: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Using InSpec 4.3.2
There are a number of issues open and closed for encoding in InSpec profiles https://github.com/inspec/inspec/issues?utf8=%E2%9C%93&q=is%3Aissue+encoding
To work in all versions of InSpec currently supported, this profile should either keep the
# encoding: UTF-8
declarations, or should limit the InSpec control source to ASCII characters.The text was updated successfully, but these errors were encountered: