|
> >What I have done is to run a simple MI program that sets > >a workstation message queue in break mode with a break > >handling program 'on-the-fly': > > Just wondering, what security would I need to run that? > > I'm thinking that as Joe-Programmer I could create the program object (I > don't think I need any special security to create an MI program). > > Now, you're modifying the workstation message queue, which is probably > *Public *change, so I could change any queue, right? > > So, if I ran that against a Queue that was in use by QSECOFR, and my > break handling program ran the "message" as a command I could run any > command in the context of QSECOFR, correct? > The message queue *is* public change, but it is system domain, so the MI program needs to be system state.
As an Amazon Associate we earn from qualifying purchases.
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.