Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>First, lets leave alone the commercial/GPL war out of SO and actually answer the OP's question...</p> <p>I work for a company selling <strong>protected</strong> Java software. Our software is good. It actually rocks and completely owns the competition's offerings. If users aren't happy with our protection scheme, they can go use the inferior products our competitors are making.</p> <p>The thing is: we're moving to a more and more networked world. Our software <em>mandates</em> an Internet connection for some functionalities to work correctly (the software will launch without an Internet connection, but not everything will work correctly).</p> <p>A correctly designed server/client protection scheme, where sufficiently enough processing happens on the server side, cannot be pirated. At one point, it becomes easier to rewrite the software than to try to reproduce what's happening on the server side.</p> <p>You can think of it this way: nobody ever succeeded playing on the real "World of Warcraft" servers with a pirated or keygen'ed licence (there have been fake servers but that would be missing the point: people playing on rogue servers are <em>not</em> playing in the real economy, which is a massive fail).</p> <p>Or this way: nobody has pirated GMail. GMail definitely rocks: it's probably the app I use the most (after my IDE). Sure, it's free... But nobody can clone it: nearly everything is happening on the server side.</p> <p>It is <em>very</em> common in some software circles to have restrictive copy protection in place: it was hardware dongles back in the days now it's mostly server/client scheme. For example there are a <em>lot</em> of very good and <strong>very</strong> expensive software thare are using the "Flex license manager", including expensive C++ compiler that beat the crap out of anything free (or cheap), which some companies are <em>very</em> happy to shell out big $$$ for and very happy to have the ability to buy such a software (and they don't mind needing an internet connection for the license verification).</p> <p>So, to answer your question:</p> <blockquote> <p>I want to put a key or licence or other kind of security to prevent redistribution of software by the client. I just want to know how to go about it?</p> </blockquote> <p>Go about it by puttin a client/server key verification in place. Ideally, make part of the computation your desktop software is doing happen on the server side: that gives headaches to wannabe pirates (they either have to pirate your server or to reproduce what the server does, there's simply no other way around it).</p> <p>Here's a +7 upvotes answer I made to a similar question which gives more detail:</p> <p><a href="https://stackoverflow.com/questions/2466424/making-commercial-java-software/2466666">Making commercial Java software (DRM)</a></p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload