How do you protect your software???
-
Hi there! We are thinking about a way to protect our software for our systems so I just want to know if you protect your software and if so, what do you use and how does it work?? A dongle, software dongle, codes, serials...? I'd be happy to hear what you are doing in that case. Ok, I know, this is not a programming forum but I don't want to see some sourcecode, just in general... ;) Thank you for answers, Olli!
Olli "Ooooooh, they have the internet on computers now!"
Homer Simpson
:beer: + :java: = NULL :=> X| -
Hi there! We are thinking about a way to protect our software for our systems so I just want to know if you protect your software and if so, what do you use and how does it work?? A dongle, software dongle, codes, serials...? I'd be happy to hear what you are doing in that case. Ok, I know, this is not a programming forum but I don't want to see some sourcecode, just in general... ;) Thank you for answers, Olli!
Olli "Ooooooh, they have the internet on computers now!"
Homer Simpson
:beer: + :java: = NULL :=> X|I protect my software by never letting anyone else use it.
-
Hi there! We are thinking about a way to protect our software for our systems so I just want to know if you protect your software and if so, what do you use and how does it work?? A dongle, software dongle, codes, serials...? I'd be happy to hear what you are doing in that case. Ok, I know, this is not a programming forum but I don't want to see some sourcecode, just in general... ;) Thank you for answers, Olli!
Olli "Ooooooh, they have the internet on computers now!"
Homer Simpson
:beer: + :java: = NULL :=> X|watermarking
-
don't bother.. software/dongles systems just irritate users and (worst of all) don't work. It is impossible to protect your software from cracking. If someone wants to copy your software they will do it. Just price your software appropriately so that it becomes preferable for your customers to pay the costs of the software and gain the benefits of whatever support you offer... you might try providing a unique build to each customer so that you ever do find illegal copies being distributed at least you can track this back to who you sold it to.
While I agree that dongles are not good, reasonable licensing systems are better than no licensing systems. It's all about perceived value to the customer. If you create something with no restrictions and a suggestion to pay then you'll find very few users actually bother to do so - there is no perceived value. If you create something with reasonable licensing that forces users to pay then you'll find that legitimate users will pay - there is a perceived value. Sure the software will be cracked, but the people using pirated software will never pay anyway, regardless of the cost, so you may as well cater to the people who will pay (as long as you don't annoy them with over-bearing licensing schemes).
-
Hi there! We are thinking about a way to protect our software for our systems so I just want to know if you protect your software and if so, what do you use and how does it work?? A dongle, software dongle, codes, serials...? I'd be happy to hear what you are doing in that case. Ok, I know, this is not a programming forum but I don't want to see some sourcecode, just in general... ;) Thank you for answers, Olli!
Olli "Ooooooh, they have the internet on computers now!"
Homer Simpson
:beer: + :java: = NULL :=> X|With my life!
-
Hi there! We are thinking about a way to protect our software for our systems so I just want to know if you protect your software and if so, what do you use and how does it work?? A dongle, software dongle, codes, serials...? I'd be happy to hear what you are doing in that case. Ok, I know, this is not a programming forum but I don't want to see some sourcecode, just in general... ;) Thank you for answers, Olli!
Olli "Ooooooh, they have the internet on computers now!"
Homer Simpson
:beer: + :java: = NULL :=> X|I write such terrible software that no one will buy it. That way, I don't have to worry about protecting it. :) Marc
-
With my life!
-
I write such terrible software that no one will buy it. That way, I don't have to worry about protecting it. :) Marc
Patent violation!!! ;P
-
Hi there! We are thinking about a way to protect our software for our systems so I just want to know if you protect your software and if so, what do you use and how does it work?? A dongle, software dongle, codes, serials...? I'd be happy to hear what you are doing in that case. Ok, I know, this is not a programming forum but I don't want to see some sourcecode, just in general... ;) Thank you for answers, Olli!
Olli "Ooooooh, they have the internet on computers now!"
Homer Simpson
:beer: + :java: = NULL :=> X|I protect mine with a gun. Go ahead. Steal it. I dare you.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001 -
Hi there! We are thinking about a way to protect our software for our systems so I just want to know if you protect your software and if so, what do you use and how does it work?? A dongle, software dongle, codes, serials...? I'd be happy to hear what you are doing in that case. Ok, I know, this is not a programming forum but I don't want to see some sourcecode, just in general... ;) Thank you for answers, Olli!
Olli "Ooooooh, they have the internet on computers now!"
Homer Simpson
:beer: + :java: = NULL :=> X|I'm just exploring this topic now. One of the companies I work for used to use dongles but are wanting to remove them from the next version (finally!). Dongles are a real pain to support and only inconvenience genuine users. Furthermore like everyone says they're still vulnerable to hackers like anything else. I'm hoping to replace the dongle with a simple key or serial number. I'm also considering using some kind of online activation service as well - but this comes with its own headaches and problems. Not really sure if its worth the hassle. Surprisingly, I struggled to find many off-the-shelf modules that provide such functionality - at least not ones which didn't cost the earth. I honestly thought there would be hundreds of this kind of thing out there! I did find a couple but none which met my need. I think I'm going to end up rolling my own, probably based upon the following articles which I found really useful: http://www.codeproject.com/library/ssdsdk.asp http://www.codeproject.com/install/LicenseKeyGeneration.asp Let me know if you find anything better ready to go.
-- The Obliterator
-
Hi there! We are thinking about a way to protect our software for our systems so I just want to know if you protect your software and if so, what do you use and how does it work?? A dongle, software dongle, codes, serials...? I'd be happy to hear what you are doing in that case. Ok, I know, this is not a programming forum but I don't want to see some sourcecode, just in general... ;) Thank you for answers, Olli!
Olli "Ooooooh, they have the internet on computers now!"
Homer Simpson
:beer: + :java: = NULL :=> X|Someone has to say it... Chuck Norris protects it for me...
------------------------------------------- Don't walk in front of me, I may not follow; Don't walk behind me, I may not lead; Just bugger off and leave me alone!!
-
I'm just exploring this topic now. One of the companies I work for used to use dongles but are wanting to remove them from the next version (finally!). Dongles are a real pain to support and only inconvenience genuine users. Furthermore like everyone says they're still vulnerable to hackers like anything else. I'm hoping to replace the dongle with a simple key or serial number. I'm also considering using some kind of online activation service as well - but this comes with its own headaches and problems. Not really sure if its worth the hassle. Surprisingly, I struggled to find many off-the-shelf modules that provide such functionality - at least not ones which didn't cost the earth. I honestly thought there would be hundreds of this kind of thing out there! I did find a couple but none which met my need. I think I'm going to end up rolling my own, probably based upon the following articles which I found really useful: http://www.codeproject.com/library/ssdsdk.asp http://www.codeproject.com/install/LicenseKeyGeneration.asp Let me know if you find anything better ready to go.
-- The Obliterator
Thanks for advice. In my case ist the term that we have modular concepts, means that we do have parts of the software which are implemented but maybe not payed at the moment, therefore we're lookin for a way to protect (at least) our knowledge a little bit.
Olli "Ooooooh, they have the internet on computers now!"
Homer Simpson
:beer: + :java: = NULL :=> X| -
Someone has to say it... Chuck Norris protects it for me...
------------------------------------------- Don't walk in front of me, I may not follow; Don't walk behind me, I may not lead; Just bugger off and leave me alone!!
-
don't bother.. software/dongles systems just irritate users and (worst of all) don't work. It is impossible to protect your software from cracking. If someone wants to copy your software they will do it. Just price your software appropriately so that it becomes preferable for your customers to pay the costs of the software and gain the benefits of whatever support you offer... you might try providing a unique build to each customer so that you ever do find illegal copies being distributed at least you can track this back to who you sold it to.
James Brown wrote:
you might try providing a unique build to each customer so that you ever do find illegal copies being distributed at least you can track this back to who you sold it to.
That's one of the best ideas I think, because we don't write kindof 'mass-software'. Thx! olli!
Olli "Ooooooh, they have the internet on computers now!"
Homer Simpson
:beer: + :java: = NULL :=> X| -
Cool, I'll protect my software with your life :-D
Visit http://www.readytogiveup.com/[^] and do something special today.
-
Hi there! We are thinking about a way to protect our software for our systems so I just want to know if you protect your software and if so, what do you use and how does it work?? A dongle, software dongle, codes, serials...? I'd be happy to hear what you are doing in that case. Ok, I know, this is not a programming forum but I don't want to see some sourcecode, just in general... ;) Thank you for answers, Olli!
Olli "Ooooooh, they have the internet on computers now!"
Homer Simpson
:beer: + :java: = NULL :=> X|Olli wrote:
protect our software
Through a process of ever increasing rounds of feature creep, our software never gets released thus providing us the ulitmate protection.
Why is common sense not common? Never argue with an idiot. They will drag you down to their level where they are an expert. Sometimes it takes a lot of work to be lazy The people in the lounge said I should google for the answer to a programming question but I do not know what search engine to use
-
Hi there! We are thinking about a way to protect our software for our systems so I just want to know if you protect your software and if so, what do you use and how does it work?? A dongle, software dongle, codes, serials...? I'd be happy to hear what you are doing in that case. Ok, I know, this is not a programming forum but I don't want to see some sourcecode, just in general... ;) Thank you for answers, Olli!
Olli "Ooooooh, they have the internet on computers now!"
Homer Simpson
:beer: + :java: = NULL :=> X|Don't bother with dongles. As others have said already, dongles are annoying and can still be cracked. The main reason they can still be cracked is that most software that uses dongles still has some piece of code that boils down to something like:
if(dongle not found) { display error message and quit } else { run program or specific feature }All a cracker has to do is change the instruction that does the comparison and s/he is in. Your best protection is against unauthorized use of some functionality is to simply not make it available. For example, if you have a demo version of your application and want to disable certain features, the only way you can be sure they will never be enabled is to not include them in the build. Internet activation can be a good way to go, as it takes the serial calculations out of the cracker's hands. However, it can still fall to the same problem as a dongle (simple good boy/bad boy compare). It also depends on your application and whether or not it may be used on a computer without an internet connection. I feel a good way to follow the idea of "not making the feature available" is wise use of encryption. You mentioned having a modular application with different features. Try encrypting the feature libraries or data files with a strong standard encryption algorithm like RSA or AES. Make the key unique for each customer. Have the customer's serial number(s) be the decription key. Never validate the key itself in your application, only the checksum of the decrypted dll or data. This way a cracker has no way of knowing exactly what the decrypted dll or data should look like. A paying customer can still distribute their copy, but if you watermark the encrypted files, you should be able to tell who's up to no good. -
Hi there! We are thinking about a way to protect our software for our systems so I just want to know if you protect your software and if so, what do you use and how does it work?? A dongle, software dongle, codes, serials...? I'd be happy to hear what you are doing in that case. Ok, I know, this is not a programming forum but I don't want to see some sourcecode, just in general... ;) Thank you for answers, Olli!
Olli "Ooooooh, they have the internet on computers now!"
Homer Simpson
:beer: + :java: = NULL :=> X|Proprietary licensing system consisting of a limited trial version downloaded from the internet which can be unlocked with a license key that we email them. The license key contains is digitally signed xml document and contains their company name and details so they will feel *very* uncomfortable passing it on to friends etc (which is the most common form of piracy, not crackers). And being .net we also obfuscate our binaries and they are all strongly named. I've worried about and studied this issue for over 10 years now and there really is no business case for dongles and excessive methods. No method will keep out the most sophisticated crackers and most will just annoy legitimate users which is not a good business plan. Keep in mind that the most common form of piracy is either multiple copies in use at the same business and / or people passing on their license or serial number to their friends or associates; this is also the easiest form of piracy to combat if you plan for it. Keep it simple, don't worry about it too much and take out time every few weeks to search for keys and cracks of your software posted on warez sites and be prepared to make slight alterations to your source code to combat them and re-release with the next update.
"I don't want more choice. I just want better things!" - Edina Monsoon