About Encryption

[wjtpt]

I've written a lot of Autolisp programs and I want to know how to encrypt Autolisp programs so that others can't directly view them in text editors or even modify them with malice.

 

[Walt Engle]

I've written a lot of Autolisp programs and I want to know how to encrypt Autolisp programs so that others can't directly view them in text editors or even modify them with malice.

I have a Kelv program that encrypts lsp programs - this is the original program for this operation. Takes a bit of explanation which is not something for this forum. If you want, can send to you via email with full explanation.
W.

 

[caduser]

use protect.exe provide by autodesk u can protect your lisp routine

wjtpt <> wrote:

I've written a lot of Autolisp programs and I want to know how to encrypt Autolisp programs so that others can't directly view them in text editors or even modify them with malice.

 

[jeroenberkers]

If you have release 2000 or higher, use the vlide-editor (visualLisp editor in acad) and create FAS-files. This give a secure encryption to your applications.

 

[Rakesh Rao]

Hello,

In AutoCAD 2000 and above, you can use Visual Lisp to complile your programs into an FAS file or VLX application. This is a binary file and cannot be viewed or changed.

Regards
Rakesh

I've written a lot of Autolisp programs and I want to know how to encrypt Autolisp programs so that others can't directly view them in text editors or even modify them with malice.

 

[Ian A. White]

<DIV><FONT face=Arial size=2>use protect.exe provide by autodesk u can protect your lisp routine</FONT></DIV>

Unfortunately there are many programs to unprotect these around.

 

[Ian A. White]

<DIV>If you have release 2000 or higher, use the vlide-editor (visualLisp editor in acad) and create FAS-files. This give a secure encryption to your applications.<BR>-- <BR>Jeroen Berkers<BR>A2k - W98SE</DIV>

Even FAS files are not safe. A while back someone passed me a routine to decrypt them, and unfortunately it gave me back the source code very clearly.

KELV.EXE is good as it takes a very long time to re-assemble anything that you can use. There are cautions here, and the key is an updated KELV.DEF file. The last one I had was for R14. For any routine written with 2000 and later you will need it updated to take care of all the VL, VLA, VLAX, VLR functions otherwise they will be scrambled and you will not be able to run the routine.

 

[petd]

Ian is the encryption with doslib a good one ?

 

[Kevin Nehls]

Those are still not binary files. They are byte-encoded very similarly to how protect did the old "autolisp protected" files. And as such, can be decrypted. The only fortunate thing right now is that there isn't a program to decrypt these files that's easy to get ahold of. There is one out there being worked on and I've seen probably the same program Ian has only at a much earlier stage.

Learning VC++ and programming your applications in ARX is the only true way to protect your code.

 

[Ian A. White]

Ian is the encryption with doslib a good one ?

Probably as good as any, but I don't think it works with AutoLISP files on the fly. I understand it encrypts the drawing file as a security measure (at least when I tried it a while back).

The problem with PROTECT is that no matter what the "password/key" you use, only the first letter is used, and all you have to do is list the protected file and it stares you in the face.

 

[Kevin Nehls]

The problem with PROTECT is that no matter what the "password/key" you use, only the first letter is used, and all you have to do is list the protected file and it stares you in the face.

You don't even need to do that as any (or most) of the decrypt programs out there will just do that itself and decrypt the file in just a couple of seconds.