Re: iSeries Command Log - Possible Security Flaw?

[Brian <iserieslists@xxxxxxxxx>]

Violaine,

Thanks for initiating the APAR. Even though the iSeries Command Log is not
accessible outside of the PC that WDSC is running on, the password still
needs to be blocked from the view of those that might be looking over one's
shoulder. I am currently weening myself off the 5250 interface and
trying to use WDSC exclusively so this APAR and its resulting fix
will remove one more obstacle from my path.

Do you have a response for the second part of my post regarding the command
entry combo box being made available without first having to enter a
"priming" command? It would be nice to be able to go to one place to enter
commands without having to remember that you have to go to a separate place
to enter the first one for a session. For now, I've put a workaround in
place by setting an initial command in the connection properties to act as
my "priming" command.

Thanks again,

BJ



On 12/27/06, Violaine Batthish <batthish@xxxxxxxxxx> wrote:
> Hi BJ,
>
> On the iSeries, job logs are visible to other users, so for security
> issues, hidden parameters of CL commands do not appear.
> The iSeries command log view is not accessible outside of the PC that WDSC
> is running on (the job logs that WDSC produces do not display the hidden
> parameters)
> However, the behaviour should imitate that of the iSeries, so I have
> opened
> APAR SE27679 to track the issue.
>
> thanks,
>
> Violaine Batthish
> WebSphere Development Studio Client, IBM Toronto Lab