How to protect my code

[iTijn]

Sharing code amongst programmers isn't the same as sharing it with your clients.

 

I have written quite some VBA code for a tool that has cought the attention of a major multinational. Before distributing this package I would like to know how to protect the software in a better way than just adding a password to the project. (There are many "password recovery tools" that can crack it.)

 

 

All suggestions are welcome.

Thanks.

[JohnM]

Will you be selling this program?

If so you could check out Aladdin hardware key software A.K.A HASP key

I use it with lisp but VBA is a little different

The cost is reasonable because they charge you for each key you purchace. Last I looked it was about $50.00 a key when I bought it the software was free and they charged for the keys.

I have never done a VBA project for AutoCAD but the principals should be the same.

I think you would have to make your code a DLL file and use the Aladdin software to create a wrapper around the DLL then write a calling code for AutoCAD.

So when the user starts the program a call is made to the DLL and the wrapper will check for the HASP key before it lets the DLL fire. The wrapper encodes the dll so it can’t be cracked.

There is more to it but this is just the nutshell.

[Freerefill]

I haven't used VBA, but I know there's a way to export a LISP into a sort of executable, which creates a .vlx file, which you cannot view the source code of. Does VBA have anything similar?

[BIGAL]

Why not convert it to .net and compile makes it very hard to crack, using lisp kelvinator etc there are cracks around, good as a first stage of protection if trying to stop the average guy. We hard coded the autocad serial number into our code once ammazingly got a call from a customer asking why it would not work on some elses computer Dah ! pay for it!

 

If you have a commercial product and look at making lots of money then spend a little securing it. A signed piece of paper makes good fire starter or big flames in court.

 

Ps do you know any one who can write in assembler ? no it was disassembler.

[iTijn]

Indeed I have compiled LISP into a VLX file.

But I have never found a tool to compile VBA into a 'machine readable only' format.

VBA seems to want to work with the raw code. (‘Just in time compiler'?)

The code can be protected with a password, but with enough time you can always 'recover' it. This gives the ‘hacker’ access to all your code including your comments. So calling an Aladdin function (DLL) for security could easily be edited / bypassed.

 

.NET seems the way to go with a VBA background. (I have only just started to read up on it.) There seem plenty of .NET tutorials around to get started. But before I go there.. what about security for .NET?

[JohnM]

To truly protect your code you have 2 ways to go. A hardware key or a software key

Hardware keys are cheaper. No mater what language you compile your code in it will be subject to hacking unless protected by encoding with a security software. I sell programs written in lisp / Vlisp and compile to a vlx and use a HASP key for one of my packages and I use a software key for others and I have not had any problems (yet).

The bottom line is if someone wants to hack your coed they will find a way. Security just keep the honest crooks out.

[MarcoW]

Hi there,

 

I got a bit curious about this all for there was a time that I wanted to protect a drawing. Not for clients but for collegues. It happens that people alter other peoples drawings, for some reason. Whenever (in a later time) there seem to be faults or probs nobody is home .

It then looks as if it is my fault in a case of wich I am shure it wasn't me:huh:. It would be good to "protect" the drawing for that reason...

[Freerefill]

I don't know much about protecting a drawing, but I do know plenty of ways to CYA. The first one is, keep track of when you last saved a drawing. There should be a timestamp and a name in the properties of the file.

 

Another better method is using a Field, which is sort of like linking a text object or attribute (not sure what the exact specifications are) to some parameter of the drawing, including who used it last and who saved it last. That way, it's right there on the drawing itself who messed with it.

[JohnM]

When I worked for a company that had several draftsmen working on the same project I always kept a copy on my hard drive to cover my butt. Stamps and logon info is good but it doesn’t help when the moron uses your computer when your out. From experience I learned to make a copy of everything and keep it in a safe place just incase.

But protecting programs is a lot different from protecting drawings.

[Freerefill]

Well that gets me thinking. There must be a way to write a LISP program to create a reactor which logs certain input... I know there's one for saving a drawing.. and just exporting that data to a protected folder smuggled away on your hard drive. You could have the LISP automatically load during startup, so unless someone was VERY clever and intentionally trying to screw you over, anything they do on your machine using AutoCAD will be kept track of.

[Commandobill]

Hi there,

 

I got a bit curious about this all for there was a time that I wanted to protect a drawing. Not for clients but for collegues. It happens that people alter other peoples drawings, for some reason. Whenever (in a later time) there seem to be faults or probs nobody is home .

It then looks as if it is my fault in a case of wich I am shure it wasn't me:huh:. It would be good to "protect" the drawing for that reason...

 

'securityoptions' you can password protect your dwgs....