pvginkel / progressencode

Implementation of the Progress OpenEdge ENCODE algorithm

ProgressEncode

The code in this repository is in the public domain. See CC0 1.0 Universal (CC0 1.0) Public Domain Dedication for more information.

Introduction

Progress OpenEdge 4GL has a function named ENCODE. This function is a one way hash function that is used by many legacy applications written in Progress to e.g. hash passwords.

Progress has stated (http://knowledgebase.progress.com/articles/Article/P111508) that they are not willing to make the algorithm behind the ENCODE function public. This can cause problems when you need to interoperate with legacy applications. This project contains implementations of the algorithm behind the Progress ENCODE function specifically to allow this kind of operability.

New languages

If you have a version of this algorithm in a different language, feel free to create a pull request to have it added to this repository. Note however that addition of your code to this repository requires it to conform to the CC0 license.

Issues

The unit tests which are part of the project contain a randomly generated set of inputs and outputs encoded by Progress. The only known issue is that Progress does not allow NUL characters in strings, so I could not test this. The list of encoded strings in the unit tests all pass.

Bugs

Bugs should be reported through github at http://github.com/pvginkel/ProgressEncode/issues.

progressencode's Issues

Common Lisp implementation

First off, thanks for doing this project: it has saved my bacon in a pretty significant way (we have a web application with existing users whose passwords are hashed with, you guessed it, ENCODE()).

I've ported your code to Common Lisp (here, licensed CC0), which you're welcome to include here if you like. I'm not sure how you'd want to do that: I kind of need it in my own repository for distribution purposes. Perhaps a git subtree? Plain old file copy? In any case, don't feel obligated; it just seemed like a good idea to make it available here as well.