Welcome Guest! Log in


The forum is in read only mode.
Stambia versions 2.x, 3.x, S17, S18, S19 and S20 are reaching End of Support January, 15th, 2024. Please consider upgrading to the supported Semarchy xDI versions. See Global Policy Support and the Semarchy Documentation.

The Stambia User Community is moving to Semarchy! All the applicable resources have already been moved or are currently being moved to their new location. Read more…

Topic-icon Question Encryption and decryption algorithm

22 May 2015 05:46 #1 by jason.choi
Encryption and decryption algorithm was created by jason.choi
Hi Support

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?

22 May 2015 12:04 #2 by Thomas BLETON
Replied by Thomas BLETON on topic Encryption and decryption algorithm
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 ?
25 May 2015 05:30 - 25 May 2015 05:31 #3 by jason.choi
Replied by jason.choi on topic Encryption and decryption algorithm
Hi Thomas

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.
Last edit: 25 May 2015 05:31 by jason.choi.
25 May 2015 11:00 #4 by Thomas BLETON
Replied by Thomas BLETON on topic Encryption and decryption algorithm
Hello Jason,
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: dev.mysql.com/doc/refman/5.5/en/encryption-functions.html ; 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.