Simple encryption result is displaying in log
Posted: Mon Jun 11, 2007 2:23 pm
Is there a way to prevent the encrypted parameter result of the simple encryption algorithm from being displayed when in director and selecting a job?
DSXchange
A short text to describe your forum
http://dsxchange.com./
Simple encryption result is displaying in log
Page 1 of 1
Posted: Mon Jun 11, 2007 2:47 pm
I don't believe so.
Posted: Tue Jun 12, 2007 8:14 am
Thanks.ray.wurlod wrote:I don't believe so. ...
I am going to open a case because it took me only a few minutes to determine the function and that an inverse function exists.
Posted: Tue Jun 12, 2007 8:27 am
Hmmm!!Ultramundane wrote:it took me only a few minutes to determine the function and that an inverse function exists.
gateleys
Posted: Wed Jun 13, 2007 2:33 pm
Which of course yields the database passwords from the last run.gateleys wrote:Hmmm!!Ultramundane wrote:it took me only a few minutes to determine the function and that an inverse function exists.
gateleys
If you want to get the default password for a job, and you can read the job, you can copy it (or edit without saving), delete the old job contents except the parameters, and use the command
echo #I_GOT_YOUR_PASSWORD#
Posted: Wed Jun 13, 2007 2:46 pm
I don't know what you were trying to say in the above quote.Ultramundane wrote: Which of course yields the database passwords from the last run.
If you want to get the default password for a job, and you can read the job, you can copy it (or edit without saving), delete the old job contents except the parameters, and use the command
echo #I_GOT_YOUR_PASSWORD#
Anyhow, did you get to talk to your support folks? Do drop in a line if they give you a 'YES, you can restrict the encrypted password from appearing in the job log' response.
gateleys
Posted: Wed Jun 13, 2007 2:51 pm
I don't know what you were trying to say in the above quote.
If you can read someone's job, you can open it and replace the contents with an External Source stage (for example) and run the OS command "echo" against any encrypted parameter that they have specified a default for and you can see their default value.
Anyhow, did you get to talk to your support folks? Do drop in a line if they give you a 'YES, you can restrict the encrypted password from appearing in the job log' response.
Yep. We have a case open and they are going to fix the issue of the encrypted strings showing up in the status files and when you double click on the job log in director.
If you can read someone's job, you can open it and replace the contents with an External Source stage (for example) and run the OS command "echo" against any encrypted parameter that they have specified a default for and you can see their default value.
Anyhow, did you get to talk to your support folks? Do drop in a line if they give you a 'YES, you can restrict the encrypted password from appearing in the job log' response.
Yep. We have a case open and they are going to fix the issue of the encrypted strings showing up in the status files and when you double click on the job log in director.
Posted: Wed Jun 13, 2007 3:02 pm
Really!! I didn't know that (and of course, so many other things). I will give that a try...., but am sure my DBAs will not like that. Could be a SOX issue.
gateleys
gateleys
Posted: Wed Jun 13, 2007 3:06 pm
Yes, those are all SOX issues. They are also PCI and HIPAA issues.gateleys wrote:Really!! I didn't know that (and of course, so many other things). I will give that a try...., but am sure my DBAs will not like that. Could be a SOX issue.
gateleys