-
Notifications
You must be signed in to change notification settings - Fork 682
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
License Check issue on 6.6.0 #6863
Comments
@lmayorga1980 |
Chef InSpec 6 does require communication with a license server to perform any scan, whether local or remote. If you are running offline - without network communication - you will need to run a local license server and connect to that. For further details, please see the troubleshooting entry, https://docs.chef.io/inspec/troubleshooting/#unable-to-connect-to-the-licensing-server-inspec-requires-server-communication-to-operate |
I was running Inspec since version 3 and never require a license and now starting version 6 a license server will be needed even though is still open source version? Also, even if you have a license provided, why would i need to go to the internet or set up an external component like a local license server. This can be an overkill configuration for users who just have some profiles locally and want to execute locally inspec. |
Looks like a license key is required even for using this great open source tool in other open-source projects? wow! |
Since InSpec 4 (2019), InSpec has been under a dual license: the Apache v2 license applies to distribution of the source code, but the Chef EULA applies to the usage of the software - including commercial usage, and limiting most personal usage. When you execute InSpec since version 4 you must agree to these dual license terms using the license acceptance mechanisms. However, in InSpec 4 and 5, there was no enforcement of the usage aspect of the licensing system. Beginning in InSpec 6, we at Progress Chef are starting to enforce tracking of the usage of the license, so that we can better guide our resources in future development of InSpec. This provides better service to our customers and allows us to continue to bring new features to the wider community. |
This is sad news for the community. |
Could you explain how you define a "target"? Do you mean |
Please find the definition of target here : Q: What is a target? https://www.chef.io/licensing-tiers-faq You are limited to 10 different targets (inspec exec -t ) with the free-tier license |
Is this possible without internet connection? |
Generally, people will require an internet connection to use InSpec 6. InSpec 6 requires a network connection to a license server. For most people, that is an internet connection to the Progress Chef global license service. For customers behind an air gap (disconnected from the Internet), Progress Chef offers a standalone private license server. |
Yeah, very strange. Goss & Ansible FTW. |
In your particular environment, perhaps the CINC project would be a good
option for you.
Check out http://cinc.sh
It’s a project sponsored by Progress and The OSL.
It’s the pure Apache to build of the inspec Code.
The license covers the Chef built binaries.
…--------
Aaron Lippold
***@***.***
260-255-4779
twitter/aim/yahoo,etc.
'aaronlippold'
On Wed, Feb 28, 2024 at 19:34 BordenIT, LLC Admin ***@***.***> wrote:
Looks like a license key is required even for using this great open source
tool in other open-source projects? wow!
Yeah, very strange.
—
Reply to this email directly, view it on GitHub
<#6863 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AALK42HU2PKGP5WI4CQDPXTYV7ZMXAVCNFSM6AAAAAA7M2DCUKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZQGMZTKMZRGI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
I am getting this error using the latest version
6.6.0
. Is there a flag to skip this since I am running local profiles and don't need a chef licensing server?Unable to connect to the licensing server. InSpec requires server communication to operate
The text was updated successfully, but these errors were encountered: