Re: Authorizing Address Space

Article View: bit.listserv.asm370

Article #314

Back to bit.listserv.asm370 Previous Next

#314

From: Binyamin Dissen
Date: Mon, 05 Sep 2005 16:12

35 lines
2801 bytes

On Mon, 5 Sep 2005 11:45:48 -0400 "Edward E. Jaffe"
<edjaffe@phoenixsoftware.com> wrote:

:>Paul V DAngelo wrote:

:>>If the product does not allow An apf Authoried service to be used the
:>>installation needs to build there own environment, hence an Authorizing SVC.

:>A "generic" authorizing SVC/PC is a bad idea. Proper procedure is to
:>encapsulate the authorized function(s) within the SVC/PC routine itself.
:>Even then, there are serious considerations when running authorized code
:>within an otherwise unauthorized address space: exhaustive parameter
:>validation, using protected (key 0-7) storage only, making the other
:>TCBs in the address space (still running unauthorized code)
:>non-dispatchable,

If running as an SVC/PC, why?

What can they do?

:>                  establishing appropriate error recovery, protecting
:>against unexpected usage of the SVC/PC routine, etc.

--
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: <2iroh112482okgspk1d9jbkfud0d9vc92i@4ax.com>

Path:

arc1-ca.pugleaf.net!g2news1.google.com!news4.google.com!sn-xit-04!sn-xit-11!sn-xit-06!sn-xit-14!supernews.com!149.173.6.116.MISMATCH!foggy!vm.sas.com!dissensoftware.com!bdissen

References: <20050905.112220.-344155.1.essteam@juno.com> <431C682C.8060707@phoenixsoftware.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!news4.google.com!sn-xit-04!sn-xit-11!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 19:12:39 +0300
Organization: DISSEN Software, Bar & Grill - Israel  Ltd.
Lines: 35
Sender: IBM Mainframe Assembler List <ASSEMBLER-LIST@LISTSERV.UGA.EDU>
Message-ID: <2iroh112482okgspk1d9jbkfud0d9vc92i@4ax.com>
References: <20050905.112220.-344155.1.essteam@juno.com>
            <431C682C.8060707@phoenixsoftware.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 1125937173 28297 10.19.150.41 (5 Sep 2005 16:19:33 GMT)
X-Complaints-To: usenet@unx.sas.com
NNTP-Posting-Date: Mon, 5 Sep 2005 16:19:33 +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: <431C682C.8060707@phoenixsoftware.com>
Return-Path: owner-assembler-list@LISTSERV.UGA.EDU
X-OriginalArrivalTime: 05 Sep 2005 16:19:31.0029 (UTC)
                       FILETIME=[986E1850:01C5B235]
Originator: daemon@mozart.unx.sas.com

Reply to Parent Message