Re: Security questions

[rob@xxxxxxxxx]

Actually, Oliver, you created the loophole yourself by not securing all 
the files and using adopted authority on the 5250 programs.  You, or your 
vendor, were the ones who created the file with the bogus *PUBLIC access.

Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 




oliver.wenzel@xxxxxxxxxxxxxxxxxxxxxxx
Sent by: midrange-l-bounces@xxxxxxxxxxxx
03/20/2003 08:55 AM
Please respond to Midrange Systems Technical Discussion
 
        To:     Midrange Systems Technical Discussion 
<midrange-l@xxxxxxxxxxxx>
        cc: 
        Fax to: 
        Subject:        Re: Security questions



Vern,

>I'd be inclined to have
>*PUBLIC *EXCLUDE to all production data, then use your menu approach. 
This

>is better, still not bulletproof.

How do you handle query access, then?

We have lots of user queries and CAX-downloads and all that stuff. How
complicated
does setting up and maintaining these security tools get?

So, without exit-point programming or buying some security product, I
cannot fix these
loopholes? Thanks a lot, IBM..

Thanks,

Oliver

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.