× 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.


  • Subject: RE: security AGGRAVATION: renaming *devd
  • From: "Ed Fishel" <edfishel@xxxxxxxxxx>
  • Date: Wed, 8 Aug 2001 16:06:06 -0500


Dan,

I tried to check the archives to read the full text of your first post on
this subject but cannot get to them. Hopefully this response will be
helpful.

Think of *IOSYSCFG as a privilege. It is not intended to give anyone
authority to any objects. A user with just *IOSYSCFG special authority
still needs authority to the various command and API interfaces to create,
change, or delete a device description. If you look at Appendix D of the
Security Reference Manual you will see that in addition to needing
*IOSYSCFG, a user must have *CHANGE plus *OBJMGT authority to change a
device description. Also to rename any object a user needs *OBJMGT
authority to the object.

This brings me to the next point. If your device description objects are
created with public *CHANGE authority then the public should not be able to
rename or change those objects because the public does not have *OBJMGT
authority.


Ed Fishel,
edfishel@US.IBM.COM


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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.