Re: authorization

["Leif Svalgaard" <leif@xxxxxxxx>]

----- Original Message -----
From: brian <brian@black.yi.org>
To: <mi400@midrange.com>
Sent: Wednesday, January 03, 2001 2:12 PM
Subject: authorization


> I'm seeing references in old AS/400 publications to a process described as
> using a pointer to an object to which you're authorized to access an
> object to which you're not.  What's the scoop?  Thank you.

An example that comes to mind is this::

        SETSPFP   .FORGED, .SEPT(ENTRY_NBR); /* FORGE POINTER */
        MATPTR    .INFO, .FORGED;

If you simply try to materialize the entry point, that is:

        MATPTR   .INFO, .SEPT(ENTRY_NBR);

you get an exception ('Object domain or hardware storage protection violation
'). By setting another system pointer, .FORGED, from the entry point (the
SETSPFP instruction) you essentially forge a new pointer from the old. This
new pointer can be materialized in some cases, bypassing the security
integrity check for the SEPT object itself.

Another example is CPYBWP a pointer from materialized data to one of your
pointers. The resulting pointer still has the original authority permissions
set.

I'm not really sure where you want to go.
Could you share the article and tell me more?
Leif



+---
| This is the MI Programmers Mailing List!
| To submit a new message, send your mail to MI400@midrange.com.
| To subscribe to this list send email to MI400-SUB@midrange.com.
| To unsubscribe from this list send email to MI400-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: dr2@cssas400.com
+---