Protecting LISP files

[Anonymous]

I am a programmer writing LISP Programs for payimg Clients

I am getting concerned that my (and yours) programs can now be
comprimised by Un-protect programs

Can we develop a way of "locking" the LISP files to a NT FileServer
Directory, or a location that allows AutoCad to read the LISP file but
not allow the user to copy it or saveas or anything like that...so we
can still "protect.exe" it but with the added protection of it not being
copied either ?

Regards
Richard Ferguson
www.romeocad.com

[Anonymous]

Richard,

What version of AutoCAD are your programming for? If your programming for
AutoCAD R2000, you can use the built in Visual LISP FAS/VLX compilation to
protect your files. This is much more protective than the simple AutoLISP
encryption programs out there. If Visual LISP is not an option, go to
www.cadalog.com and search for CONVERT7, which is a protector AND
Kelvinator/comment remover that makes the file almost impossible to read
even if decrypted.

Hope this helps,
--
Phillip Kenewell
CAD Systems Technician
Air Gage Company
pkenewell@airgage.com
===================
> Not < a Member of the AutoDESK
Discussion Forum Moderator Program
Richard Ferguson wrote in message
news:38D6DFD8.42C329DD@autofire.com.au...
> I am a programmer writing LISP Programs for payimg Clients
>
> I am getting concerned that my (and yours) programs can now be
> comprimised by Un-protect programs
>
> Can we develop a way of "locking" the LISP files to a NT FileServer
> Directory, or a location that allows AutoCad to read the LISP file but
> not allow the user to copy it or saveas or anything like that...so we
> can still "protect.exe" it but with the added protection of it not being
> copied either ?
>
> Regards
> Richard Ferguson
> www.romeocad.com
>

[Anonymous]

Thank you for you help Phil, www.cadalog.com looks like the way to go
Ragards
Richard
www.romeocad.com

Phil Kenewell wrote:

> Richard,
>
> What version of AutoCAD are your programming for? If your programming for
> AutoCAD R2000, you can use the built in Visual LISP FAS/VLX compilation to
> protect your files. This is much more protective than the simple AutoLISP
> encryption programs out there. If Visual LISP is not an option, go to
> www.cadalog.com and search for CONVERT7, which is a protector AND
> Kelvinator/comment remover that makes the file almost impossible to read
> even if decrypted.
>
> Hope this helps,
> --
> Phillip Kenewell
> CAD Systems Technician
> Air Gage Company
> pkenewell@airgage.com
> ===================
> > Not < a Member of the AutoDESK
> Discussion Forum Moderator Program
> Richard Ferguson wrote in message
> news:38D6DFD8.42C329DD@autofire.com.au...
> > I am a programmer writing LISP Programs for payimg Clients
> >
> > I am getting concerned that my (and yours) programs can now be
> > comprimised by Un-protect programs
> >
> > Can we develop a way of "locking" the LISP files to a NT FileServer
> > Directory, or a location that allows AutoCad to read the LISP file but
> > not allow the user to copy it or saveas or anything like that...so we
> > can still "protect.exe" it but with the added protection of it not being
> > copied either ?
> >
> > Regards
> > Richard Ferguson
> > www.romeocad.com
> >

[Anonymous]

I've been writing LISP files for a while but, to be honest, I've never
considered protecting the source code until now and I'm not certain what the
best way is to do this as I've never looked into it before. What is the
easiest and most efficient way to accomplish this?

[Anonymous]

Keep it free & open!
;-)

[Anonymous]

I'd like to, however, the problem is that I have some CADD users that don't
know enough to leave things alone if they don't understand them and I don't
want to keep fixing things that shouldn't have been touched to begin with.

"Andrey Marinov" wrote in message
news:eec6415.3@WebX.maYIadrTaRb...
> Keep it free & open!
> 😉
>
>

[Anonymous]

Question. Why aren't your lisp files along with all of the other "standard"
customizable files located in one central, network location, that only you
can write to?

BTW, you can use Vlide to compile your lsp files into fas or vlx, you can
also use the (vlisp-compile.....) function once you load vlide once. Take a
look in the help files for more info. 😉 It's all there.

--
Kevin Nehls


"David Penk" wrote in message
news:6491FC77E2448731405F78233EC40E88@in.WebX.maYIadrTaRb...
> I'd like to, however, the problem is that I have some CADD users that
don't
> know enough to leave things alone if they don't understand them and I
don't
> want to keep fixing things that shouldn't have been touched to begin with.
>

[Anonymous]

2 suggestions:

1. Assuming you're using a network share for routines/blocks/etc and you
have someone for IT, ask them to modify permissions on the files/directories
that only you should be able to make changes to.

2. You could compile you're LISP routines/files as VLX files. This isn't
foolproof either, but the users can't view/edit the source code, though they
could still do things to give you a headache, depending on their knowledge
of working with the VLISP editor. Short of deleting/moving files.

"David Penk" wrote in message
news:6491FC77E2448731405F78233EC40E88@in.WebX.maYIadrTaRb...
> I'd like to, however, the problem is that I have some CADD users that
don't
> know enough to leave things alone if they don't understand them and I
don't
> want to keep fixing things that shouldn't have been touched to begin with.
>
> "Andrey Marinov" wrote in message
> news:eec6415.3@WebX.maYIadrTaRb...
> > Keep it free & open!
> > 😉
> >
> >
>
>

[Anonymous]

I sat down with my IT manager and we're going to locate all the files on one
central network drive (as suggested) along with the rest of our CADD-related
information that none of the users have write-access to.

"Jason Wilder" wrote in message
news:E54E87CC551FFCE2D136694EBB8AC938@in.WebX.maYIadrTaRb...
> 2 suggestions:
>
> 1. Assuming you're using a network share for routines/blocks/etc and you
> have someone for IT, ask them to modify permissions on the
files/directories
> that only you should be able to make changes to.
>
> 2. You could compile you're LISP routines/files as VLX files. This isn't
> foolproof either, but the users can't view/edit the source code, though
they
> could still do things to give you a headache, depending on their knowledge
> of working with the VLISP editor. Short of deleting/moving files.
>
> "David Penk" wrote in message
> news:6491FC77E2448731405F78233EC40E88@in.WebX.maYIadrTaRb...
> > I'd like to, however, the problem is that I have some CADD users that
> don't
> > know enough to leave things alone if they don't understand them and I
> don't
> > want to keep fixing things that shouldn't have been touched to begin
with.
> >
> > "Andrey Marinov" wrote in message
> > news:eec6415.3@WebX.maYIadrTaRb...
> > > Keep it free & open!
> > > 😉
> > >
> > >
> >
> >
>
>

[Anonymous]

You'll be glad you did. It will make your life a lot easier. It's nice to
update one file and everyone instantly has that update. 😉

--
Kevin Nehls


"David Penk" wrote in message
news:B6231B41DFCB1AE658EF292748BC7414@in.WebX.maYIadrTaRb...
> I sat down with my IT manager and we're going to locate all the files on
one
> central network drive (as suggested) along with the rest of our
CADD-related
> information that none of the users have write-access to.
>

[Anonymous]

just keep uncompiled copies! (but you Knew that!)

[Anonymous]

Anyway, compiling and optimizing will make your lisp programs load and
probably run faster.
So it could be a good idea even if not for security reasons.

Regards,
Reinaldo Togores


"Kevin Nehls" escribió en el mensaje
news:6AD56DBA5484B112196ED222DCF192EB@in.WebX.maYIadrTaRb...
> You'll be glad you did. It will make your life a lot easier. It's nice
to
> update one file and everyone instantly has that update. 😉
>
> --
> Kevin Nehls
>
>
> "David Penk" wrote in message
> news:B6231B41DFCB1AE658EF292748BC7414@in.WebX.maYIadrTaRb...
> > I sat down with my IT manager and we're going to locate all the files on
> one
> > central network drive (as suggested) along with the rest of our
> CADD-related
> > information that none of the users have write-access to.
> >
>
>