Your guess is not universal. I for one embrace open source as the future for the z ecosystem.
How to successfully manage that "new" environment for potentially dangerous dependencies is certainly an issue, but not an unsolvable one. Certainly I think IBM itself needs to assist to help solve such issues to maintain the z RAS level. My guess is that one cannot prohibit open source, it is far too prevalent and necessary for many if not most organizations actively using z/OS to run their business (e.g., the Apache / Tomcat web server software delivered as part of z/OS is also open source - Would you prohibit that too?). IMHO it is foolish to attempt to prohibit what you don't like or understand. Seek first to understand it and then how to manage the risks. Peter -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Kirk Wolf Sent: Tuesday, January 18, 2022 11:42 AM To: [email protected] Subject: Re: More of LOG4J Since I would guess that a majority of ibm-mainers would agree that open source is confusing and dangerous, here's a question: Let's say that an organization wanted to prohibit open source. How would you go about it? Kirk Wolf Dovetailed Technologies -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
