That's an excellent question and another one I've asked is how will IBM handle co-req and pre-req PTF's in other LPP's when someone updates an open source product through Yum/RPM.

Paul Fenstermacher | Sys Admin, Sr | Technology Operations | Jack Henry & Associates, Inc.
2135 E. Primrose | Springfield, MO 65804 | 417-235-4114 x177389 |
pfenstermacher@xxxxxxxxxxxxx

-----Original Message-----
From: OpenSource [mailto:opensource-bounces@xxxxxxxxxxxx] On Behalf Of Justin Taylor
Sent: Monday, July 2, 2018 7:57 AM
To: OpenSource-Midrange. com (opensource@xxxxxxxxxxxx) <opensource@xxxxxxxxxxxx>
Subject: [IBMiOSS] Yum & security vulnerabilities

The e-mail below is from an external source. Please do not open attachments or click links from an unknown or suspicious origin.

Over the weekend, I got a notice from IBM about a vulnerability in 5733OPS 10. They listed the PTF for the fix. That got me thinking. How's IBM going to handle this with in Yum/RPM?

Anyone heard mention of this?
--
This is the IBMi Open Source Roundtable (OpenSource) mailing list To post a message email: OpenSource@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/opensource
or email: OpenSource-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at https://archive.midrange.com/opensource.

NOTICE: This electronic mail message and any files transmitted with it are intended
exclusively for the individual or entity to which it is addressed. The message,
together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution
is strictly prohibited. If you have received this message in error, please
immediately advise the sender by reply email and delete all copies.


This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].