R
R
Roman Sopov2013-04-09 16:05:41
Browsers
Roman Sopov, 2013-04-09 16:05:41

How to sell a browser plugin?

There is a certain cross-browser plugin that works with cryptography and tokens. We want to sell it separately from the boxed system.
If someone buys a plug-in for their own needs, then nothing will prevent them from posting it on the network and they will use it illegally, violating the license.
How can we protect ourselves in this case?

Answer the question

In order to leave comments, you need to log in

4 answer(s)
N
NeonMercury, 2013-04-09
@NeonMercury

Raise the server and store the list of licenses there (key, ...). When the plugin starts, send a request to your server and indicate that this key is online. When the plugin ends, send a request and indicate that it is offline. As soon as a request is made to make the key online, which is already online, then the key has been leaked and it is blocked.

U
UZER2006, 2013-04-09
@UZER2006

You can make some kind of one-time authorization in the plugin using your server. The key is issued upon purchase and can only be used once.
Also, in all cases, you need to take care of protecting the source codes. After all, they are, as it were, open, so at least some kind of obfuscation really does not hurt.

R
Roman Sopov, 2013-04-09
@sopov

What if you bind to a domain name? After all, this plugin can only be used in web applications ... but what about internal resources? In several companies vnt. domains can be similar ... it's another matter if these are .ru, .com, etc. zones.
Or is it nonsense?

M
mihavxc, 2013-04-10
@mihavxc

Use binding to HASP software or hardware keys or some other.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question