Can I ask how does the X-Pack license work? Is there perhaps an asymmetric encryption public key bundled with ElasticSearch? And if one buys an enterprise plan subscription, then Elastic-the-company creates a license, and signs with a private key? And the ElasticSearch software uses the built-in public key to verify that the license is valid? (i.e. signed by Elastic-the-Company's private key)
Or does the license and signature work, in some other way?
Theoretically, people could fork the ElasticSearch repo, edit the public key (assuming there is one?) so they can sign licenses with their own private key? Or they could edit the source code and remove various checks that tests if there's a licence or not? ... And companies don't do that, for many reasons, like 1) it's illegal. 2) It's maybe not well-spent-time: the company's engineers can create more value for the company, by spending time on other things than hacking each new releases of X-Pack. And 3) it'd lower morale inside the company, if the employees notice that their employer does things like that? (Or what are your thoughts? If it's ok that I ask things like these)