I would like to find out more about stambia encryption and decryption algorithm.
If source data has encrypted data, is it possible to decrypt at source and encrypt at Target by using SHA-1 256? Also, may I know what algorithm Stambia using?
If we talk about SHA-256 hash data, this cannot be decrypted. A hash function does not produce encrypted data : it produces a hash (a nearly unique key representing the data).
Can you provide more information on how the source data was encrypted ?
I would like to understand more about Stambia encryption method.
When we introduce encryption to client, some customer has their own security policy which we must follow.
For example, a source data contains a password in text format and client would like to move source to target (data migration) and meantime, the password needs to be encrypted by certain method. It could be MD-5(Hash) or SHA1-256 or Triple des.
Please advise me how we can include this into the process.
By the way, this is not actual project and I am checking some possible scenario.
The solution really depends on what you need to do - very precisely
I understand that you do not have yet detailed information, so here is some examples :
Example #1 : mapping rdbms to rdbms
When using a Bind technique, there is no real need to make encryption. The data is read from source, and written to the target within the same process. Not stored anywhere else, so no need to encrypt it, right ?
Example #2 : exporting data to a file with FileExport, for future import into a target rdbms
In this case, you don't want the password to be stored as clear text in the file. The idea is simply to use the source rdbms' encryption functions. For example with a Mysql database:
; or DBMS_CRYPTO package on Oracle ; etc...
I hope this helps
If you have more info on what you need to do please share it : what are source and target technologies, are there temporary files, etc.