On Tue, 17 Nov 2020 13:58:23 +0000 Seymour J Metz <sme...@gmu.edu> wrote:
:>Indeed, OS/360 had some code that was reentrant but not refreshable; AFAIK IBM has cleaned up all such abominations, and the binder does not allow you to create a load module or program object marked as reentrant but not refreshaable. You are asserting that RENT now forces REFR? :>________________________________________ :>From: IBM Mainframe Assembler List <ASSEMBLER-LIST@LISTSERV.UGA.EDU> on behalf of Binyamin Dissen <bdis...@dissensoftware.com> :>Sent: Tuesday, November 17, 2020 2:35 AM :>To: ASSEMBLER-LIST@LISTSERV.UGA.EDU :>Subject: Re: security with storage allocation under z.OS :> :>On Mon, 16 Nov 2020 18:35:29 -0700 Paul Gilmartin :><00000014e0e4a59b-dmarc-requ...@listserv.uga.edu> wrote: :> :>:>On 2020-11-16, at 17:47:10, Dan Greiner wrote: :>:>> ... :>:>> So, the facility only applies to virtual addresses on newer models. As I recall, the development of this facility was requested by z/Linux in order to help avoid classic stack-overflow exposures; but, it obviously has applicability to other environments. (It was also introduced in order to "keep up with the Joneses er ... I mean the Intels.) :>:>> :>:>Conversely, there's REFRPROT to prevent storing into programs :>:>marked REFR. Dismayingly, I believe REFRPROT is global and :>:>intrduces incompatibility with "dusty deck" programs erroneously :>:>marked REFR. :> :>That is a good thing. However, RENT alone does not (conceptually) require a :>module to be refreshable. -- Binyamin Dissen <bdis...@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.
