Using a DONGLE to protect my software..?!

[Yashied]

Using _WinAPI_UniqueHardwareID() it's a good idea.

[SYRAU3]

what to doooooooooo !!! is it AutoIt waekness point or this is general in all languages?

[water]

It's not a weakness of AutoIt - it's called WAD (works as designed).

[Reg2Post]

Nothing is 100% secure. Even less when connected to the Internet. @OP: I suggest you simply find the right combination of usability and security for the intended users and usage of your software. Sure, one unique identifier is not so secure but who are you protecting the software from? Either way, you can go into multi-factor authentication identifiers and DO NOT tell anyone how you hashed your security identifier and protect your source code. If that was obscure, note that it was intentional. (hint: combine multiple unique hardware id/sn into a composite one). Keep in mind you are still stuck with your identifier in your software which is another issue all in itself.

[OregonJohn]

I'm using LimeLM, a relatively new service for licensing. They are helpful in getting their coding into your script. Otherwise, i agree with all the others that there is no ultimate way to protect the software itself. Locks on doors only protect against non-professional thieves.

[SYRAU3]

is the hardare information returned by _WinAPI_UniqueHardwareID() never change even with using different operating systems?

[Yashied]

is the hardare information returned by _WinAPI_UniqueHardwareID() never change even with using different operating systems?

Yes.

[ZiggyStardust]

A couple months back I used a SecureDongleX ($6-$8 depending on quantity ordered) as a hardware key. Very cheap and will thwart 80-90% of the users trying to hack it. Well woth the $8 and the code was pretty simple. If you are interested let me know.

[SYRAU3]

i think there is always a way to dump the dongle info or make a virtual copy of it....... here, in the Arabian world i live in, the dongles are the last security tool to be used..

[SYRAU3]

Yes.

i hope so, thank you