| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Use of the DB2 encrypt function in WMQI |
« View previous topic :: View next topic » |
| Author |
Message
|
| chaman |
 Posted: Mon Jul 14, 2003 10:11 am Post subject: Use of the DB2 encrypt function in WMQI |
 |
|
Newbie
Joined: 14 Mar 2002
Posts: 7
Location: Montreal, Canada
|
Hi all,
I have a flow that use the "new" DB2 encrypt function to encrypt part of the incoming message in a table. The problem is that the DB2 encrypt and decrypt_char functions needs a password, that is used as a key to encrypt/decrypt the message and I don't want to put it in clear in the Database node. Any ideas How to get the password from within the Database node besides developing a plugin that would call encrypting/decrypting modules?
Thanks |
|
| Back to top |
|
 |
| kirani |
| Posted: Mon Jul 14, 2003 10:41 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
I believe another option would be to store your password into DB table and then use it in a DB node when calling encrypt/decrypt functions.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| chaman |
| Posted: Mon Jul 14, 2003 10:53 am Post subject: |
|
|
Newbie
Joined: 14 Mar 2002
Posts: 7
Location: Montreal, Canada
|
| The problem is if I want that password to be encrypted as well, same dilemma... |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Jul 14, 2003 12:39 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| chaman wrote: |
| The problem is if I want that password to be encrypted as well, same dilemma... |
If you want to store the password encrypted, you will need to then be able to decrypt the password before you pass it in to the encryption routine. So it's a recursive dilemma - because now you have a key or password being used to access your password and obviously this second key or password needs to be secure as well.
You could wrap the encrypt/decrypt access in a stored procedure, and put the password in that stored procedure. Then only the people who can read the stored procedure will know what it is, and this can be secured fairly well. And possibly the DB2 system (I don't know the encryption routines in DB2) will allow you to encrypt the stored procedure except for when it's being run. |
|
| Back to top |
|
|
| chaman |
| Posted: Tue Jul 15, 2003 7:00 am Post subject: |
|
|
Newbie
Joined: 14 Mar 2002
Posts: 7
Location: Montreal, Canada
|
| Good idea Jeff, I'll try something along those lines |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
