example-cpp-license-validation VS example-electron-license-activation

Would be a real shame if someone used mitmproxy modify the validation request in transit. Looking at one of the provided examples [0] it does not have any mention of certificate pinning.

With all due respect this service seems to alleviate the most simple to implement parts of a licensing scheme while not solving the actually challenging parts. Even combined with a sophisticated obfuscating tool it leaves a lot of holes to be filled by the end user.

[0]: https://github.com/keygen-sh/example-cpp-license-validation

I’m currently developing a commercial product with Rust and I was wondering what the best way to distribute and sell licenses for it is. Should I use a third party like keygen or is there an easy way I could get started on implementing my own. I’m out of my depth when it comes to software licensing so I figure I should ask before assuming it’s a task I can take on myself.

have you checked https://keygen.sh/, yoyll get ideas there

Some sort of customer portal (or spreadsheet), where the customer can add, remove licences. After payment/confirmation you simply generate a json and encrypt with an async key. In your soft you read that as config file input, that will limit how many users can be created etc. keygen.sh or any other tool might also do it.