×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Hello Rob,
Am 20.05.2020 um 21:47 schrieb Rob Berendt <rob@xxxxxxxxx>:
Basically my goal is to secure the data with *public *exclude.
Maybe this helps: How I administer access rights in Linux.
Most often, it's all about allowing access read-write or not at all. So I'm creating directories and user-groups named alike. Directories stay with the user root but I change the group ownership to the mentioned group. User gets rwx, and group gets rws. Then I add users into the proper group(s). The s-bit will be passed down to newly created files and directories(, no matter if the user is in that particular group or not).
Interesting part is: It doesn't matter what access-rights the directories and files below have, because the barrier is the one directory.
I'm using a similar approach on my midrange-machines. The data library itself will be CHGOBJOWNed to the group with AUT *ALL, PUBLIC is set to *EXCLUDE. Users are added to the group as needed.
Basically like that.
:wq! PoC
PGP-Key: DDD3 4ABF 6413 38DE -
https://www.pocnet.net/poc-key.asc
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.
midrange.com
