|
Grootte: 1265
Commentaar:
|
Grootte: 1657
Commentaar:
|
| Verwijderingen worden op deze manier gemarkeerd. | Toevoegingen worden op deze manier gemarkeerd. |
| Regel 1: | Regel 1: |
| = Why compile CAD Lisp? = Lisp is interpreted. So compiling is a bit misleading here, it does not offer substantial changes, it remains interpreted. But what does compiling offer? Files will be encrypted and slowing down elements like spacers are removed. = How to compile? = |
|
| Regel 3: | Regel 7: |
| For AutoCAD... Start LISP IDE, then... Do something like | For AutoCAD... Start LISP IDE, then... Do something like |
| Regel 5: | Regel 10: |
| (vlisp-compile 'st "C:\MyLisp\Example.lsp" "C:\MyLisp\Example.fas")}}} | (vlisp-compile 'st "C:\MyLisp\Example.lsp" "C:\MyLisp\Example.fas") }}} = "Security through obscurity" = People don't like to talk about decompiling LISP and feel save when files are encrypted. |
| Regel 7: | Regel 15: |
| "Security through obscurity" means that people don't like to talk about decompiling LISP and feel save when files are encrypted. The truth: It is not save! | The truth: Do talk about decompiling and reverse engineering and yes, encryption is weak and not save! |
| Regel 9: | Regel 17: |
| Removing items from Autodesk fora doesn't help much and bringing it as "Better not to be discussed in public" is a joke. If it is a problem, then improve the encryption, period. | Items are even removed from Autodesk fora. Positioning decompiling as "Better not to be discussed in public" is a joke and doesn't help much. Message for these people: Suppose we talk about your bank account's encrypted data exchange instead of Lisp and reconsider please. |
| Regel 11: | Regel 19: |
| If you disagree, then suppose we talk about your bank account's encrypted data exchange instead of LISP and then please, reconsider ;-) | If weak encryption is a problem, then improve the encryption, period. |
| Regel 15: | Regel 23: |
| And for those that lost their source code, it can be a welcome solution. | And for those that lost their source code, decompiling can be a welcome solution. |
Why compile CAD Lisp?
Lisp is interpreted. So compiling is a bit misleading here, it does not offer substantial changes, it remains interpreted. But what does compiling offer? Files will be encrypted and slowing down elements like spacers are removed.
How to compile?
Compiling for BricsCAD can be done with DEScoder.exe, see your BricsCAD installation under Program Files. The beauty is simplicity here.
For AutoCAD... Start LISP IDE, then... Do something like
(vlisp-compile 'st "C:\MyLisp\Example.lsp" "C:\MyLisp\Example.fas")
"Security through obscurity"
People don't like to talk about decompiling LISP and feel save when files are encrypted.
The truth: Do talk about decompiling and reverse engineering and yes, encryption is weak and not save!
Items are even removed from Autodesk fora. Positioning decompiling as "Better not to be discussed in public" is a joke and doesn't help much. Message for these people: Suppose we talk about your bank account's encrypted data exchange instead of Lisp and reconsider please.
If weak encryption is a problem, then improve the encryption, period.
In fact, it is not hard to decompile and encryption is not much more than just an obstacle. For BricsCAD, encryption is stronger but the chain is as weak as, so don't expect your code to be save. See for example http://www.sporaw.com/work/decompilers.htm, or https://lispbox.wordpress.com/2014/12/23/visual-lisp-vlxfas-and-visual-basic-v5v6-files-decompiling-procedure/, http://cd.textfiles.com/unprotect/AUTODC/, to wake you up.
And for those that lost their source code, decompiling can be a welcome solution.