|
Tim McCarthy wrote: > > Apologies if I appeared big-headed, I didn't intend it to come across that > way! :-) I was TRYING to indicate that QTEMP IS VERY accessible to outside > jobs. A few weeks ago I posted a program to some list-ers that can access > another job's LDA/PDA/GDA. The principle is the same. If you'd like I can > send you some sample MI code that gets info about all objects in a job's > QTEMP. The sample program doesn't actually do anything with the info but > you could code that in yourself. > > Tim I meant that in a lighthearted way :-) What I was trying to find out is what is the actual exposure. Can you update/add things to another job's QTEMP. Can you bypass the object level security of items in QTEMP ? If an object is set to exclude your access and is in QTEMP does that open it up? How detectable is this type of hack? How preventable? Thanks John Hall +--- | 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 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.