Feedback
Did this article resolve your question/issue?

   

Article

What is the algorithm used by the ENCODE() 4GL function?

« Go Back

Information

 
TitleWhat is the algorithm used by the ENCODE() 4GL function?
URL NameP111508
Article Number000128016
EnvironmentProgress 8.x
Progress 9.x
OpenEdge 10.x, 11.x, 12.x
All Supported Operating Systems
Question/Problem Description
What is the algorithm used by the ENCODE() 4GL function?
Does the ABL ENCODE() function use industry standard hashing algorithms?
Is it possible to implement the ENCODE() 4GL function in other programming languages?
Steps to Reproduce
Clarifying Information
Error Message
Defect/Enhancement Number
Cause
Resolution

The algorithm used by the ENCODE() 4GL function is not publicly available. If you need a standard hashing algorithm, then you could use either MD5 or SHA-1 in your ABL clients. 

A common question that is asked about the ENCODE function with regards to industry defined security standards (for example the PCI DSS standards) is wether the ENCODE function uses one of the recognized hashing algorithms.

The answer to this is that it does not do so.

Workaround
Notes
Last Modified Date9/16/2020 9:30 PM
Attachment 
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.