I need C# licensing system

Lordinaryus

Registered Member
Joined
Nov 28, 2018
Messages
61
Reaction score
6
I need simple example for licensing system. It needs to be log in with user-pass and time-based. Also read old thread on BHW but didn't get very well because there was a no example. So, just need basically example and also is there anybody can show me?
 
your a programmer come on it simple.

a membership database with a serial number attached to an app so users can only use the app if the serial is valid.

also updates are only added if the serial is valid.
 
your a programmer come on it simple.

a membership database with a serial number attached to an app so users can only use the app if the serial is valid.

also updates are only added if the serial is valid.

Thx. Thats what i thought before your comment but what about decompile situation?
 
You make the system in PHP and just make requests to the API endpoints from C#

You need to make sure of a lot of things. No SQL injection is a must.
 
Anything in c# can be decompiled, just have a look at dotnet peek.

You can make it harder to crack but never impossible.
 
1. Use paddle.com SDK (free) for licensing system .

2. Use ConfuserEx (free) to protect your code and make it harder to crack .

I'm using same above for my commercial tools i coded in C# and after long research found it's easiest and fastest way , not mentioning it's totally free .
 
1. Use paddle.com SDK (free) for licensing system .

2. Use ConfuserEx (free) to protect your code and make it harder to crack .

I'm using same above for my commercial tools i coded in C# and after long research found it's easiest and fastest way , not mentioning it's totally free .

You're begging to get your tool cracked if you use Confuser Ex.
 
This is why all my new stuff is cloud based lol...
 
You're begging to get your tool cracked if you use Confuser Ex.

Theoretically any tool coded with .NET Framework languages could be cracked , this is why microsoft products itself crack available everywhere online ,
when using obfuscator to protect the code from being stolden from other coders and make it harder to be cracked -to make noobs reverse engineers away - , back to ConfuserEx if use it with maximum obfuscation option you will get similar results of most paid obfuscator tools , check that with tools like .Net Reflector or dotPeek , however the best choice to make your app web app and not desktop app to get rid from all of that ...
 
Theoretically any tool coded with .NET Framework languages could be cracked , this is why microsoft products itself crack available everywhere online ,
when using obfuscator to protect the code from being stolden from other coders and make it harder to be cracked -to make noobs reverse engineers away - , back to ConfuserEx if use it with maximum obfuscation option you will get similar results of most paid obfuscator tools , check that with tools like .Net Reflector or dotPeek , however the best choice to make your app web app and not desktop app to get rid from all of that ...

You do realize ConfuserEx is public source? LOL

If you would like a tiny improvement, it would be a good idea to modify it: https://github.com/yck1509/ConfuserEx
 
You do realize ConfuserEx is public source? LOL

If you would like a tiny improvement, it would be a good idea to modify it: https://github.com/yck1509/ConfuserEx

I refered to that public ConfuserEx link in my first post ! , obfuscation will be applied to our app , what is the difference if the if the obfuscater tool is public or private one ?! , if you say the obfuscation process itself in this case could be reverse engineered this is possible but still more efforts and time for the cracker , for your first suggestion about "system in PHP and just make requests to the API endpoints from C#" do you know this easily could be cracked also with tools like fiddler capturing and decrypting the traffic and http response manipulating ... ? , So no ideal solution for this , if there's ideal solutions you will not find cracked copies for big IT company products .

OP asked for "simple example for licensing system" i answered him , he didn't ask for CIA Software protection system , writing "LOL" for members comments trying to help to look smart boy does not apply in this situation , if you want to help OP provide him your secure system .
 
Last edited:
I refered to that public ConfuserEx link in my first post ! , obfuscation will be applied to our app , what is the difference if the if the obfuscater tool is public or private one ?! , if you say the obfuscation process itself in this case could be reverse engineered this is possible but still more efforts and time for the cracker , for your first suggestion about "system in PHP and just make requests to the API endpoints from C#" do you know this easily could be cracked also with tools like fiddler capturing and decrypting the traffic and http response manipulating ... ? , So no ideal solution for this , if there's ideal solutions you will not find cracked copies for big IT company products .

OP asked for "simple example for licensing system" i answered him , he didn't ask for CIA Software protection system , writing "LOL" for members comments trying to help to look smart boy does not apply in this situation , if you want to help OP provide him your secure system .

PHP code is hidden so there is no issue if a user intercepts the traffic through Fiddler?

Obviously the security measures need to lie in the PHP, not the C#. Make rate limits, captcha, IP checks, MySQL injection prevention, etc.

Instagram's API's are fully public. Does that mean they are exploitable? Sure, but not because they're public.

And the "LOL" comes from me laughing at your advice. It's extremely bad for you to advise people to use public protection apps like ConfuserEx.
 
PHP code is hidden so there is no issue if a user intercepts the traffic through Fiddler?

Obviously the security measures need to lie in the PHP, not the C#. Make rate limits, captcha, IP checks, MySQL injection prevention, etc.

Instagram's API's are fully public. Does that mean they are exploitable? Sure, but not because they're public.

And the "LOL" comes from me laughing at your advice. It's extremely bad for you to advise people to use public protection apps like ConfuserEx.

from your reply you have no idea what you are talking about , http response will be on client machine with ok or not and the software codes itself will be on client machine and this could be override from client machine , watch [Video Tuts] HTTP Programming with C# to understand what i mean , no server or php access needed to be exploited for that .

btw all of your suggestions about php API ....etc already implemented in paddle platform , first point of in first post .
 
from your reply you have no idea what you are talking about , http response will be on client machine with ok or not and the software codes itself will be on client machine and this could be override from client machine , watch [Video Tuts] HTTP Programming with C# to understand what i mean , no server or php access needed to be exploited for that .

I think you're confusing yourself buddy.

"http response will be on client machine" -> did i ever imply anything different? where else do you want them to be? LOOL
"and the software codes itself will be on client machine and this could be override from client machine" -> did ever imply that the software would not run on a client machine?
"watch [Video Tuts] HTTP Programming with C# to understand what i mean , no server or php access needed to be exploited for that " -> i am more than comfortable on the concepts of HTTP. so what's your point? PHP is hidden, so even if you intercept it, you still can't exploit it if you've taken the appropriate security measures.

Also I'm trying to decipher stuff through your broken English, but I think I answered most of your confusions.

You might need to research PHP some more.

Also, you're implying the HTTP requests on the client machine can't be encrypted and deciphered on server side too. This is something that a user with fiddler will struggle with.

But as I said, it's always better to have your own API and have your protections there.
 
I will leave all of your ignorant parts , but for this :

But as I said, it's always better to have your own API and have your protections there.

and why the API you created or OP created will be better than Paddle platform API ?! , paddle platform source codes not public , Paddle servers faster with advanced backup system ... , what make that lower quality of your API or OP API ?!
 
If you really want to protect your IP, then you must design around SaaS. Your business domain must be delivered by your server. The c# client would just be a thin client. The second you put your business domain into a client, you're open to reverse engineering.
 
Back
Top