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



<snip>
It doesn't permit anyone to do
something that native (i.e., "green screen") security
prohibits, so if you can do it via Access for Web and think
you shouldn't have been able to do that, there's a hole in
your security anyway.
</snip>

And there's the rub. You're dropping 30 years back in the past Dave.
You're trying security by "menu" security. Instead of securing the data
you're trying to secure, you're attempting to secure but one of the myriad
of applications that allow you to access that data.

Here, very few users have *SPLCTL. Those who have a need to share output
will use a joint output queue with *DTAAUT specify on the output queue.
Even the "default" printer does not share spool files. Why? Because
we've noticed too many secure spool files on this output queue, after all,
it is the "default". When someone comes up to me and wants access to
these spool files a good spanking and sending them out of the room to fix
the application to go to the right output queue ensues.

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.