Kbase P19338: 4GL/ABL: How to compile encrypted 4GL/ABL source code?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
12/29/2008 |
|
Status: Verified
GOAL:
4GL/ABL: How to compile encrypted 4GL/ABL source code?
GOAL:
How to compile 4GL/ABL source code encrypted without a user defined KEY?
GOAL:
How to compile 4GL/ABL source code encrypted with a user defined KEY?
GOAL:
Can unencrypted source code of an encrypted 4GL/ABL code be deduced or listed?
FACT(s) (Environment):
All Supported Operating Systems
Progress 8.x
Progress 9.x
OpenEdge 10.x
FIX:
1. If the 4GL/ABL source code has been encrypted using the XCODE utility without a user defined key(?k), that is, the code was compiled using the XCODE default key, then any progress executable can compile the encrypted code.
2. If the 4GL/ABL source code has been encrypted using the XCODE utility with a user defined key(?k), then any progress executable that can supply the key via the XCODE option of the COMPILE statement can compile the encrypted code.
3. The encrypted 4GL/ABL source code is compiled by supplying the encryption key using the XCODE option of the COMPILE statement.
4. Encrypting a 4GL/ABL source code procedure is a one-way non-reversible encoding process. The original 4GL/ABL source code of an encrypted 4GL procedure can not be deduced or listed.