Introduction
Hashcode is a fixed length code that can be used to verify integrity. An algorithm known as hash function can be used to create hash codes on messages/files. Ideally, these algorithms have several unique properties.
Not reversible
It is impossible to generate a message o a hash code. Hash functions are known as trap doors because they only go one way from message->hashcode
Avalanche effect
Small changes in a message lead to a big change in the hash code.
Hash collision
It is extremely unlikely that two messages will generate the same hash code. Should this happen it is known as hash collision.
Now my questions:
- Customers/Partners: Has anyone implemented this hash coding (e.g. for exporting bank statements)?
- IFS R&D: Is there or will there be functionality in IFS to support hash coding?