You don't need to be authorized to use z/OS UNIX shared memory segments.
You do need access to the file system and the memory segments are
protected using the normal UNIX permissions. Semaphores and pthread
mutexes can also reside in shared memory for inter-process locking.
The /tmp TFS is backed by memory so the easiest solution may be to us
files in the TFS.
On 3/12/2017 11:20 PM, Peter Relson wrote:
Given that an unauthorized user has access only to unauthorized subpools
and that all unauthorized subpools are freed between steps, some less
direct approach would be necessary, involving authorized code putting the
data into some other kind of storage (be that an authorized subpool,
common storage, shared storage, etc) and providing some means by which the
new step could access that. Perhaps z/OS Unix does so. "Normal" MVS would
likely never do that as it could be considered a violation of B1 security
(to the extent that anyone still cares about B1 security), at least for
the case where the subsequent step might be started in a different address
space, such as in a restart scenario.
Peter Relson
z/OS Core Technology Design
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
