Jack, I understand. But consider the engineering that would be needed to pull that off. One needs to intercept one of the downloads, alter the binary, and then only if the object signing is passed (doubtful at that point) would the code get loaded onto a machine. Doable sure, but why? How do you make money on it?
It's just not worth the effort.
OH well, it's not a major impediment to my world so I really don't care, but it's going to bust a lot of software written over the years to automate downloading and preparing for PTF group application.
I guess we get to find out how well Python integrates into a fix package environment. That project after the web services I'm building.
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Jack Woehr via MIDRANGE-L
Sent: Wednesday, June 30, 2021 9:19 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Cc: Jack Woehr <jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: Attention all IBM i shops. You may not be aware of it, but FTP is changing to FTPS/SFTP (secure) before the end of June or in early July 2021.
On Wed, Jun 30, 2021 at 8:14 AM <midrangel@xxxxxxxxxxxxxxxxx> wrote:
What's to protect with a bunch
of binary downloads that can't be used unless you have a copy of IBM i
available, and anonymous log in?
MITM interception and alteration resulting in trojanized binaries running at LIC level .. who could POSSIBLY be concerned about that?! 😀😀😀
The interesting question is not why IBM is switching to encrypted delivery.
The interesting question is why IBM i shops weren't screaming for this 15 years ago.
--
Jack Woehr, IBM Champion 2021
<
https://www.youracclaim.com/badges/528d23d6-087f-4698-8d17-d59688106ac4/public_url>
Absolute Performance, Inc.
12303 Airport Way, Suite 100
Broomfield, CO 80021
NON-DISCLOSURE NOTICE: This communication including any and all attachments is for the intended recipient(s) only and may contain confidential and privileged information. If you are not the intended recipient of this communication, any disclosure, copying further distribution or use of this communication is prohibited. If you received this communication in error, please contact the sender and delete/destroy all copies of this communication immediately.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
midrange.com
