(E)CSA for an amount large enough to send data both ways?

On Sun, Dec 8, 2024 at 4:44 PM Richard Zierdt
<[email protected]> wrote:
>
> Thank you, Peter.   Others have also responded - thank you - suggesting Unix 
> Pipes and TCP/IP.   Those environments being new to me, I will try to solve 
> my problem using only MVS for now, but if not, then Unix, here I come.
>
> I believe the only way to run authorized is to link (Bind) AC(1), which I'm 
> trying to avoid.
>
> I may be overly sensitive here, but I am not trying to get around security.  
> I am, however, trying to understand how two unauthorized address spaces using 
>  XM POST between them, apparently not allowed, would pose a security risk if 
> they could.
>
> OK — I'll take a shot at answering my own question, based on a comment by 
> Charles Mills: "random" address spaces.  If unauthorized XM POSTs were 
> allowed without restriction, then one AS could "POST" to any other AS, 
> possibly interrupting a program or destroying data.  Yeah, that'd be bad.  
> But then it would help if a set of MVS OS services were developed that could 
> "handshake" together two (or more) specific, not random, unauthorized ASs so 
> they could communicate between themselves.
>
> Thanks again --
> Richard Zierdt
>
> ________________________________
> From: IBM Mainframe Discussion List <[email protected]> on behalf of 
> Peter Relson <[email protected]>
> Sent: Sunday, December 8, 2024 8:39 AM
> To: [email protected] <[email protected]>
> Subject: Re: IEAMSXMP - Cross Memory POST - Supervisor State required?
>
> This Message Is From an External Sender
> This message came from outside your organization.
>
>
> You do not need to be supervisor state to use plain XM Post (POST with ASCB). 
> But you do need to be authorized (any of supervisor state, system key, 
> APF-authorization works).
> You do need to be supervisor state to use IEAMSXMP.
>
> Back in the days of B1 security, the "communication" to another address space 
> that POST can be considered to do would have been a security violation.
> Nowadays a POST like that is simply unacceptable. It was not allowed then, it 
> is not allowed now.
>
> Peter Relson
> z/OS Core Technology Design
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN
>
>
> Confidentiality Warning/Avertissement de confidentialité:
>
> This message is intended only for the named recipients. This message may 
> contain information that is privileged or confidential. If you are not the 
> named recipient, its employee or its agent, please notify us immediately and 
> permanently destroy this message and any copies you may have. Ce message est 
> destiné uniquement aux destinataires dûment nommés. Il peut contenir de 
> l'information privilégiée ou confidentielle. Si vous n'êtes pas le 
> destinataire dûment nommé, son employé ou son mandataire, veuillez nous 
> aviser sans tarder et supprimer ce message ainsi que toute copie qui peut en 
> avoir été faite.
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN



-- 
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to