FAS security

Hi all,

I am a little bit disturbed by the security of fas files. Up to now, I have been under the impression that you could not decrypt a fas file. I believe this is still the case, however, after a short search, I have been able to find a decompyler which, whilst it does not fully decrypt the file, it returns enough info to be able to "crack" any potential safeguard.

I was counting on this format to produce a "software lock" for our internal customization, but after this latest development I am questioning whether this is the best method.

Does anybody have any suggestions on ways to go about securing our custom routines?

Is there an external application which can be used?

Thanks
Dart

 

Compiling it to a VLX file is supposed to be more secure.

Apart from that, you can process things through the old KELV (for
Kelvinate) utility. This scrambles variable names but can cause problems
with new functions and if you need to have variable names persist for
other routines.

You can do other things, but the key to securing a routine is not to
make the security code obvious. Most people who secure them have the
security module shining like a beacon.

 

Thanks Ian, I guess something like "software lock.lsp" is not ideal???

I will try vlx, just a question though. I haven't used Kelvinator before. How would you apply it in this case? Do you encrypt the file, then compile it to vlx?

Thanks
Dart

 

Kelvination is even less secure than fas/vlx.

--
R. Robert Bell


Thanks Ian, I guess something like "software lock.lsp" is not ideal???

I will try vlx, just a question though. I haven't used Kelvinator before.
How would you apply it in this case? Do you encrypt the file, then compile
it to vlx?

Thanks
Dart