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


  1.  Home
  2. MIDRANGE-L
  3. December 2009

Re: STG(*FREE) on SAV* commands...

CRPence wrote:
Graap, Kenneth wrote:

Being able to save objects that a programmer or operator doesn't have direct authority to, may be a useful function that Special Authority *SAVSYS addresses, but the security risk associated
with STG(*FREE) makes giving this authority to anyone extremely
risky.

The bigger security problem for the Save System special authority is actually for the ability to *restore* objects.

And that's (IMO) a very underrated exposure. The way I learned it was "He who can save an object, can restore the object." That was followed by an example scenario that very clearly illustrated the problem.

*SAVSYS is a /special/ authority for good reason. It is not to be assigned lightly.

Thank you, Chuck, for what may be taken as an authoritative assessment.

Tom Liotta


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.