I still think the way Metabox did their key licensing management system is perhaps one of the most elegant solutions I have seen.
If the Bricks team takes a look at how the Metabox team did it, I am quite sure that they could definitely implement something (albeit more limited/simpler) so that key encryption won’t be such a bother.
Where are we on this? I too am concerned in this regard to the license - like, do a website - pass it off to client - then what? Is that violating the license agreement, then? I do have a lifetime license and want to keep it - but also be able to just hand sites off to clients. Do they need to then buy their own bricks keys? What’s the official solution here, and what’s the idea?
I understand the concept behind this writ in the license agreement is that one does not publicly sell or provide key to someone else, but, like sinanisler presented, w/ the key in the database stored as clear text, anyone w/ the access to db basically gets the key and can simply use it to deploy other sites.
Not that clients are aware, I’d say, for most part - but what if? What’s the official standpoint - it’s been over a year and a half since this was posted…
We’ve addressed this internally by adding support for defining the Bricks license key via a BRICKS_LICENSE_KEY PHP constant, so the key does not have to be stored in the database for blueprint, cloned, or client-handoff workflows.
This is currently staged and not part of a public release yet. We’ll update this thread once it ships
We’ve addressed this in Bricks 2.4-beta (beta release), now available for manual download from your Bricks account.
Please read the changelog entry before testing, and let us know if you experience any issues. Note: beta builds are not recommended for production sites.
