Protection if my lisp code.

Hello there,

Has anyone got an idea on how to protect my lisp code (with a password) but
still be able te edit it easaly.

M

 

Compile it. Then keep the source in a secure location.
___

 

There is a protection method available but once created, it cannot be edited
again. You have to keep the original unprotected copy to use for editing
purposes and re-protect.
If you want more infor, email me:

 

Hi Walt Engle from Houston (we have a problem)

I was hoping there would be some way to be able to open a converted lispfile
with vlide and save it converted with a password again. In MS Excel for
example I can save my file with a password. And when I open it I'd have to
type the password again.

What kind of protection method or converter would you use anyway?

I have one from an earlier version of AutoCAD.

Marcel from
The Netherlands
www.hiensch.nl

 

apples and oranges.
use vlide to compile the lisp to unreadable code for distrubution and keep the source code.
visual lisp does not have a password protection scheme. Good thing too, because office documents are very easily
crackable. There is plenty of programs out there to crack password protected schemes. I've seen password crackers for
almost every file time out there, all of em.


"Marcel Janmaat" <>
|>Hi Walt Engle from Houston (we have a problem)
|>
|>I was hoping there would be some way to be able to open a converted lispfile
|>with vlide and save it converted with a password again. In MS Excel for
|>example I can save my file with a password. And when I open it I'd have to
|>type the password again.
|>
|>What kind of protection method or converter would you use anyway?
|>
|>I have one from an earlier version of AutoCAD.
|>
|>Marcel from
|>The Netherlands
|>www.hiensch.nl
|>
|>
|>"Walt Engle" <> schreef in bericht
|>|>> There is a protection method available but once created, it cannot be
|>> edited
|>> again. You have to keep the original unprotected copy to use for editing
|>> purposes and re-protect.
|>> If you want more infor, email me:
|>>
|>


David

 

Hello David,

Thanks for your reply.

I agree concerning the protection of excel files.
I'm looking for the fastest an easiest way, being able to test and edit my
code.

I'm not verry familiar with the creation of .fas and .vlx
I've always written my lisp code as an open source and left it available to
anyone to enhance it.

In the acad.lsp file at (s::startup) I call some .lsp files to load and this
also happens with the autoloader.
But when my code is compiled to .fas files, these calls probably wil not
work any more right?

I'm wondering how I should handle this?

Regards

M

 

Dave they should work just fine!

But I would like to point out a common misconception.

fas and vlx files are not compiled files they are encrypted files.
A simple scrambling of your code that one day may be unscrambled.

Regards Gary.

 

Do you mean that when I provide the .fas files to the users of my code,
calling a 'lets say, check.lsp file from the acad.lsp will actualy use the
check.fas file???