On Jul 26, 2007, at 3:44 PM, Paul Gilmartin wrote:
On Thu, 26 Jul 2007 13:55:32 -0500, Ed Gould wrote:
Sigh... This was BEFORE that option was available. Please just
remember it JUST WASN"T ICKDSF it was a host of other "no-no"
programs that were in sys1.linklib. It was amaspzap and others.
No.
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf
Of Paul Gilmartin
Sent: Thursday, July 26, 2007 3:44 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Secure clist
On Thu, 26 Jul 2007 13:55:32 -0500, Ed Gould wrote:
>
>Sigh... This was BEFOR
On Thu, 26 Jul 2007 13:55:32 -0500, Ed Gould wrote:
>
>Sigh... This was BEFORE that option was available. Please just
>remember it JUST WASN"T ICKDSF it was a host of other "no-no"
>programs that were in sys1.linklib. It was amaspzap and others.
>
This has been discussed many times on this list. T
t was a host of other "no-no"
programs that were in sys1.linklib. It was amaspzap and others.
Ed
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Ed Gould
Sent: 25 July 2007 19:00
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Secure c
On Wed, 25 Jul 2007 14:17:55 -0500, Anthony Saul Babonas
<[EMAIL PROTECTED]> wrote:
>ummm, so what if someone copies it into their own clist lib, modifies the id
>check code, then runs it?
>
>Been there..had to be there actually. we had an oldie where the
>original developer went off to othe
@BAMA.UA.EDU
Subject: Re: Secure clist
On Jul 25, 2007, at 12:42 PM, Phil Kingston wrote:
> Then should you not protect ICKDSF itself?
How... at the time there was no security bult into ICKDSF.
>
> If your authorised to run it in batch, then why not through TSO.
They weren't authorize
On Jul 25, 2007, at 2:01 PM, Mark H. Young wrote:
On Tue, 24 Jul 2007 08:40:09 -0400, Carroll, William
<[EMAIL PROTECTED]> wrote:
Is there any way to secure certain clist from unauthorized use?
For example if I don't want applications to get into the wlm,
Application, how would I do it? If it
keep honest people out.
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf
Of Mark H. Young
Sent: Wednesday, July 25, 2007 2:01 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Secure clist
On Tue, 24 Jul 2007 08:40:09 -0400, Carroll, William
<[EM
On Tue, 24 Jul 2007 08:40:09 -0400, Carroll, William
<[EMAIL PROTECTED]> wrote:
>Is there any way to secure certain clist from unauthorized use?
>For example if I don't want applications to get into the wlm,
>Application, how would I do it? If it can be done.
>Thanks In Advance.
>
>
>
>
>Bill Ca
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Secure clist
On Jul 25, 2007, at 9:56 AM, Wayne Driscoll wrote:
But what was purpose of this? Was there a security exposure
identified?
If so, what was it? Or was it a case of "well, it's always been done
this way."
Wayne Driscoll
Produc
21
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Secure clist
On Jul 25, 2007, at 9:56 AM, Wayne Driscoll wrote:
But what was purpose of this? Was there a security exposure
identified?
If so, what was it? Or was it a case of "well, it's always been done
this way."
Wayne Driscoll
Product De
List [mailto:[EMAIL PROTECTED] On
Behalf Of Ed Gould
Sent: 25 July 2007 18:21
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Secure clist
On Jul 25, 2007, at 9:56 AM, Wayne Driscoll wrote:
> But what was purpose of this? Was there a security exposure
> identified?
> If so, what was it? Or was
DASDVOL profiles can help here..
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf
Of Ed Gould
Sent: Wednesday, July 25, 2007 12:21 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Secure clist
On Jul 25, 2007, at 9:56 AM, Wayne Driscoll wrote
On Jul 25, 2007, at 9:56 AM, Wayne Driscoll wrote:
But what was purpose of this? Was there a security exposure
identified?
If so, what was it? Or was it a case of "well, it's always been done
this way."
Wayne Driscoll
Product Developer
JME Software LLC
NOTE: All opinions are strictly my ow
On Wed, 25 Jul 2007 10:51:11 -0500, Walt Farrell wrote:
>On Wed, 25 Jul 2007 09:39:03 -0400, Lizette Koehler
>>Under RACF I have placed a CLIST in a secured data set and had RACF set to
>>EXEC rather than READ on the data set.
>>Seemed to work and it did not impact the usage of the CLIST.
>
>I can
I can believe that would work for a data set in SYSPROC, but I believe it
would not work for SYSEXEC.
It still has the problem that Binyamin noted, though. You really need to
protect access to the data or functions the CLIST performs, as otherwise the
u
On Wed, 25 Jul 2007 09:39:03 -0400, Lizette Koehler
<[EMAIL PROTECTED]> wrote:
>Under RACF I have placed a CLIST in a secured data set and had RACF set to
>EXEC rather than READ on the data set.
>
>Seemed to work and it did not impact the usage of the CLIST.
I can believe that would work for a da
: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Ed Gould
Sent: Tuesday, July 24, 2007 11:41 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Secure clist
On Jul 24, 2007, at 10:36 PM, Wayne Driscoll wrote:
> All programs in the linklist are accessible directly, what is the
&
Under RACF I have placed a CLIST in a secured data set and had RACF set to
EXEC rather than READ on the data set.
Seemed to work and it did not impact the usage of the CLIST.
Lizette
>
> Unfortunately, read only access doesn't prevent someone
> from copying the CLIST and removing any userid che
M Mainframe Discussion List
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Secure clist
Date: Wed, 25 Jul 2007 14:10:56 +0100
Bill,
An easy way Could you not place the CLIST in a read only dataset,
and check the userid within the CLIST against a pre-defined table
defined within the code?
Or a more i
On Wed, 25 Jul 2007 14:10:56 +0100 Phil Kingston
<[EMAIL PROTECTED]> wrote:
:>An easy way Could you not place the CLIST in a read only dataset,
:>and check the userid within the CLIST against a pre-defined table
:>defined within the code?
:>Or a more involved way... you could write a quick as
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Carroll, William
Sent: 24 July 2007 13:40
To: IBM-MAIN@BAMA.UA.EDU
Subject: Secure clist
Is there any way to secure certain clist from unauthorized use?
For example if I don't want applicatio
On Jul 24, 2007, at 10:36 PM, Wayne Driscoll wrote:
All programs in the linklist are accessible directly, what is the
possible value of protecting (from read, update protection is
mandatory)
a linklist dataset? I mean if I can execute tso iefbr14, what is the
drawback of me executing tso cal
DU
Subject: Re: Secure clist
On Jul 24, 2007, at 7:44 AM, McKown, John wrote:
>> -Original Message-
>> From: IBM Mainframe Discussion List
>> [mailto:[EMAIL PROTECTED] On Behalf Of Carroll, William
>> Sent: Tuesday, July 24, 2007 7:40 AM
>> To: IBM-M
On Jul 24, 2007, at 7:44 AM, McKown, John wrote:
-Original Message-
From: IBM Mainframe Discussion List
[mailto:[EMAIL PROTECTED] On Behalf Of Carroll, William
Sent: Tuesday, July 24, 2007 7:40 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Secure clist
Is there any way to secure certain clist
On Tue, 24 Jul 2007 08:35:43 -0500, Kelman, Tom
<[EMAIL PROTECTED]> wrote:
>I'm not sure how you would secure a specific CLIST and a couple of
>people have responded with suggestions. However, if it is access to WLM
>you want to secure you can do that in RACF via the use of the facility
>class MV
Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Carroll, William
Sent: Tuesday, July 24, 2007 7:40 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Secure clist
Is there any way to secure certain clist from unauthorized use?
For example if I don't want applications to get into the wlm,
On Tue, 24 Jul 2007 07:44:28 -0500, McKown, John
<[EMAIL PROTECTED]> wrote:
>> -Original Message-
>> From: IBM Mainframe Discussion List
>> [mailto:[EMAIL PROTECTED] On Behalf Of Carroll, William
>> Sent: Tuesday, July 24, 2007 7:40 AM
>> To: IBM-MAIN@
> -Original Message-
> From: IBM Mainframe Discussion List
> [mailto:[EMAIL PROTECTED] On Behalf Of Carroll, William
> Sent: Tuesday, July 24, 2007 7:40 AM
> To: IBM-MAIN@BAMA.UA.EDU
> Subject: Secure clist
>
>
> Is there any way to secure certain clist f
Is there any way to secure certain clist from unauthorized use?
For example if I don't want applications to get into the wlm,
Application, how would I do it? If it can be done.
Thanks In Advance.
Bill Carroll
EMAIL DISCLAIMER:
The information contained in this message may be
privileged or c
30 matches
Mail list logo
