Welcome Guest! Log in
×

Notice

The forum is in read only mode.
Due to some maintenance operations, stambia.org will be switched to read-only mode during the 13th November. It will be possible to read and download, but impossible to post on the forums or create new accounts. For any question please contact the support team.

Topic-icon Question Encryption and decryption algorithm

More
22 May 2015 05:46 #1 by jason.choi
jason.choi created the topic: Encryption and decryption algorithm
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?

Thanks
More
22 May 2015 12:04 #2 by Thomas BLETON
Thomas BLETON replied the 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 ?
More
25 May 2015 05:30 - 25 May 2015 05:31 #3 by jason.choi
jason.choi replied the 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.
More
25 May 2015 11:00 #4 by Thomas BLETON
Thomas BLETON replied the 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.