🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: bit.listserv.asm370
Article #310

Re: Authorizing Address Space

#310
From: Binyamin Dissen
Date: Mon, 05 Sep 2005 15:06
66 lines
3656 bytes
On Mon, 5 Sep 2005 10:46:21 -0700 Paul V DAngelo <essteam@juno.com> wrote:

:>I have a client who would like me to develop a presentation on an
:>Authorizing Address Space.
:>I suggested simply writting an SVC that switches Authorizations instead
:>of and address space.
:>That Suggestion was fround upon.
:>They are building this facility to alow   Vendor Products and As well As
:>IBM products
:>to issues Authorized Services where I the Vendor does not usually/easily
:>permit it.

Such as?

:>The customer would like to develop a cross memory environment;
:>issue  a Program Call Instruction form a vendor product address space to
:>thecustomers
:>Authorizing  Server Address Space and allow the caller to be in
:>Supervisor State key xx or APF Authorized.

Why can't they simply APF authorize those programs that require it?

:>I believe an SVC could be developed to accomplished this, but I suspect
:>theres more to this that
:>what they are telling  me.

Could be done as a PC as well.

But......

:>My first question  is when the Cross Memory Program is executed, it would
:>Sets the  APF Authorization bit
:>and return.  WHo IS in the APF state, The entire Calling Address Space or
:>only  the invoking TCB ?

APF applies to a job step task.

But........

:>Can anyone on the list speak to the pros vs cons of developing an
:>Authorizing SVC
:>against an Authorizing Address Space.

It is usually very wrong to set APF from an uncontrolled environment (not
loaded from APF authorized libraries).

The service should be encapsulated.

:>I also suspect that Some Security Checking would be done in this Address
:>Space,
:>since that was the first concept they had me explore.

How will they verify an uncontrolled environment?

--
Binyamin Dissen <bdissen@dissensoftware.com>
http://www.dissensoftware.com

Director, Dissen Software, Bar & Grill - Israel


Should you use the mailblocks package and expect a response from me,
you should preauthorize the dissensoftware.com domain.

I very rarely bother responding to challenge/response systems,
especially those from irresponsible companies.
Technical Details
Message-ID: <5enoh1homppql4b378fh9ebt9otpo67tkr@4ax.com>
Path: arc1-ca.pugleaf.net!g2news1.google.com!news3.google.com!news.glorb.com!news.alt.net!sn-xit-04!sn-xit-12!sn-xit-06!sn-xit-14!supernews.com!149.173.6.116.MISMATCH!foggy!vm.sas.com!dissensoftware.com!bdissen
References: <20050905.104623.-344155.0.essteam@juno.com>

Show Full Headers
Complete Article Headers
X-Google-Thread: fcdcb,605a50893b34558
X-Google-Attributes: gidfcdcb,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: arc1-ca.pugleaf.net!g2news1.google.com!news3.google.com!news.glorb.com!news.alt.net!sn-xit-04!sn-xit-12!sn-xit-06!sn-xit-14!supernews.com!149.173.6.116.MISMATCH!foggy!vm.sas.com!dissensoftware.com!bdissen
From: Binyamin Dissen <bdissen@dissensoftware.com>
Newsgroups: bit.listserv.asm370
Subject: Re: Authorizing Address Space
Date: Mon, 5 Sep 2005 18:06:12 +0300
Organization: DISSEN Software, Bar & Grill - Israel  Ltd.
Lines: 66
Sender: IBM Mainframe Assembler List <ASSEMBLER-LIST@LISTSERV.UGA.EDU>
Message-ID: <5enoh1homppql4b378fh9ebt9otpo67tkr@4ax.com>
References: <20050905.104623.-344155.0.essteam@juno.com>
NNTP-Posting-Host: mozart.unx.sas.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Trace: foggy.unx.sas.com 1125933117 26713 10.19.150.41 (5 Sep 2005 15:11:57 GMT)
X-Complaints-To: usenet@unx.sas.com
NNTP-Posting-Date: Mon, 5 Sep 2005 15:11:57 +0000 (UTC)
Comments: Gated by NETNEWS@VM.SAS.COM
Return-Path: <owner-assembler-list@LISTSERV.UGA.EDU>
X-Mailer: Forte Agent 2.0/32.652
Approved-By: Binyamin Dissen <bdissen@DISSENSOFTWARE.COM>
In-Reply-To: <20050905.104623.-344155.0.essteam@juno.com>
Return-Path: owner-assembler-list@LISTSERV.UGA.EDU
X-OriginalArrivalTime: 05 Sep 2005 15:11:54.0451 (UTC)
                       FILETIME=[26856A30:01C5B22C]
Originator: daemon@mozart.unx.sas.com