Jump to content

Using a DONGLE to protect my software..?!

Recommended Posts

Hello big-minds: :D

What is the best way to protect my software fro being used on many computers?

i tried | DriveGetSerial(@HomeDrive) | , but it seems not so good as it's able to change the drive serial number with a special software.

so how about a DONGLE? is it able to be used with AutoIt? if not, what do you the best way is?

thanx in advanced.

Link to post
Share on other sites
  • Moderators

Hi, SYRAU3. This subject has been discussed many many times. Do a forum search for "protect script" and you'll find 250+ threads concerning what options are and are not available to you.

"Profanity is the last vestige of the feeble mind. For the man who cannot express himself forcibly through intellect must do so through shock and awe" - Spencer W. Kimball

How to get your question answered on this forum!

Link to post
Share on other sites

@SYRAU3 look for MoleBox, Enigma, VMProtect and Armadillo , they should help you

Edited by Belini
Link to post
Share on other sites

I scored a Commodore 64 in the early 80's (to replace my Heathkit computer) and recall a game that came with this optical prism thingy. Each time you launched the game it would display 2 scrambled characters on the monitor. Just a bunch of line fragments and dots, but, magically, when you placed the prism over the dots they would transform into 2 letters. Different letters each time you launched the game. Type those 2 characters on the keyboard and the game would finish loading. I recall thinking: "Wow! They went to a lot of effort!". In my teenage boredom one night I decided to try and crack it. I used a monitor program to step through 6502 assembly instructions for about 20 minutes and after a couple of bad attempts finally flipped the correct byte from a BE (branch equal) instruction to a BNE (branch not equal). From then on, the game started if you typed in the wrong 2 characters, and would only lock you out if you happened to type in the 2 correct characters. All that effort by the manufacturer was overcome in an hour. I can't count how many Branch, or Jump, or Call instructions got flipped or replaced with a string of 90's (NOP's) back in my "troublesome" teenage years.

So the moral of the story, and what all the above posters are alluding to, and what all 250 posts they refer to will say, is:

What one person can do, someone else, given enough time, can undo. And what can be more disheartening, sometimes they can undo your efforts in one-tenth the time you took to put them in place.

Link to post
Share on other sites

As JLogan3o13 already stated. There is no way to secure your code. If someone wants to use your code it's easy to retrieve the source and rip out the code parts where you protect your script.

My UDFs and Tutorials:


Active Directory (NEW 2021-06-05 - Version - Download - General Help & Support - Example Scripts - Wiki
ExcelChart (2017-07-21 - Version - Download - General Help & Support - Example Scripts
OutlookEX (NEW 2021-06-14 - Version - Download - General Help & Support - Example Scripts - Wiki
OutlookEX_GUI (2021-04-13 - Version - Download
Outlook Tools (2019-07-22 - Version - Download - General Help & Support - Wiki
PowerPoint (NEW 2021-08-31 - Version - Download - General Help & Support - Example Scripts - Wiki
Task Scheduler (2019-12-03 - Version - Download - General Help & Support - Wiki

Standard UDFs:
Excel - Example Scripts - Wiki
Word - Wiki

ADO - Wiki
WebDriver - Wiki


Link to post
Share on other sites

I ant been on for a while as my pc as been in for a long repair, and though i don't normally post on these kind of topics i wanted to throw in my two cents. (PS This is not a rant, just my view)

I see allot of posts of people asking for ways to add security or protection to their software, which I think is a good idea. I agree with the general view its impossible to completely protect your work (This is mainly because any defences are static *Ie don't change* while a attacker is dynamic *can change*) but this doesn't mean everyone should just flame the topic saying don't do it. Last time i checked, this is a support forum for members to get support on topics *As long as its within the rules ofc*

So there we go, i agree people are allowed to there views but if everyone takes the view "its not worth the effort", then nothing would ever get done. At lest if some people try then maybe something could out of the works that would maybe at lest stop script-kiddies getting in or understanding. The Harder it is to break in, the faster they are to just give up and move onto something else.

Anyways (Turns on my Shields and i am sure i am now a walking bullseye to be attacked ^^)

Link to post
Share on other sites

Steady on there.

Asking the same question over and over again, and getting the same replies over and over again

is neither positive or productive, the way AutoIT is made means it cannot be protested, simple.

I'm not sure what you mean by "these kind of topics" but the OP has answers to his question

in both suggestion and the knowledge that it is indeed a waste of time.

AutoIt Absolute Beginners    Require a serial    Pause Script    Video Tutorials by Morthawt   ipify 

Monkey's are, like, natures humans.

Link to post
Share on other sites

This question has been asked and answered at least a dozen times in the past year. A search of the forum would have turned up the results of those requests. As well as showing one way of trying to protect your script. Could be that the users are starting to get tired of answering the question over and over again.

If I posted any code, assume that code was written using the latest release version unless stated otherwise. Also, if it doesn't work on XP I can't help with that because I don't have access to XP, and I'm not going to.
Give a programmer the correct code and he can do his work for a day. Teach a programmer to debug and he can do his work for a lifetime - by Chirag Gude
How to ask questions the smart way!

I hereby grant any person the right to use any code I post, that I am the original author of, on the autoitscript.com forums, unless I've specifically stated otherwise in the code or the thread post. If you do use my code all I ask, as a courtesy, is to make note of where you got it from.

Back up and restore Windows user files _Array.au3 - Modified array functions that include support for 2D arrays.  -  ColorChooser - An add-on for SciTE that pops up a color dialog so you can select and paste a color code into a script.  -  Customizable Splashscreen GUI w/Progress Bar - Create a custom "splash screen" GUI with a progress bar and custom label.  -  _FileGetProperty - Retrieve the properties of a file  -  SciTE Toolbar - A toolbar demo for use with the SciTE editor  -  GUIRegisterMsg demo - Demo script to show how to use the Windows messages to interact with controls and your GUI.  -   Latin Square password generator

Link to post
Share on other sites
  • Moderators

Not to mention, I don't see anyone "flaming the topic". I believe we have endeavored to help the OP, by pointing out the inherent issues with believing you can completely protect any Intellectual Property, let alone an AutoIt script. We've also directed him to use the forum as the resource that it is, inviting him to go over some of the many posts and the pitfalls therein.

I don't disagree that security, to the degree you can reasonably attain, is a good thing. I just don't see where anyone has done anything but attempt to assist the OP.

"Profanity is the last vestige of the feeble mind. For the man who cannot express himself forcibly through intellect must do so through shock and awe" - Spencer W. Kimball

How to get your question answered on this forum!

Link to post
Share on other sites

I agree with EVERY single one of you!

I'm not discouraging some level of protection.

Basic protection is effective in keeping the average user from committing piracy and is worthwhile.

But I also think that going to extreme measures will never stop someone determined to crack your software.

I think the dongle route definitely falls into the category of "hardcore security" and is likely more effort than it is worth.

Somewhere in your code is going to be a test saying "Is the dongle present?". So, someone doesn't have to assault your security head-on to defeat it, they'll just bypass or reverse the logic of the test and step right around your elaborate protection.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.

  • Create New...