RE: File protection basics -- MIDRANGE-L

Subject: RE: File protection basics
From: Rob Berendt <rob@xxxxxxxxx>
Date: Tue, 13 Oct 2020 13:15:30 +0000
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@lists.midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.lists.midrange.com>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

I'm really not big on group profiles and have leaned more towards authorization lists. There's several advantages. One of the most beneficial is that once you've assigned the authorization list to the object you can customize it without getting another lock on the object.

But in either case, you are still giving your users *ALLOBJ, just indirectly. Especially with the group profile. This doesn't solve anything unless your auditors are complete idiots and just want to ensure that individual users do not have *ALLOBJ.

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: File protection basics , Dave

This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.