On Wed, Apr 3, 2024 at 10:39 AM Rob Berendt <robertowenberendt@xxxxxxxxx> wrote:
Item 1: PTF Groups disabling heritage navigator
[...] The individual PTF's you will need are listed at
https://www.ibm.com/support/pages/node/1164076
You can check for the existence of those PTF's.
I suppose you can really ramp up IFS and other object auditing and see what
gets whacked when you apply those PTFs.
Or dump an ifs file listing and compare before/after.
Great link. That page actually also includes artifacts!
First, the PTFs: Neither of the ones listed for us show up on our
system, as far as I can tell. Which suggests we did not apply them,
which suggests heritage Nav was not removed via PTF.
Then it says:
<blockquote>
When the PTF is applied (Temporarily or Permanently), the following
steps are completed:
a. Save file "QGPL/QINAVSAVF" created.
b. Directory "/QIBM/ProdData/OS400/Navigator/appdata" saved to
"QGPL/QINAVSAVF"
-- All jar files for Heritage Navigator, plugins, jt400, etc are in
this directory.
c. Directory "/QIBM/ProdData/OS400/Navigator/appdata" will be removed.
d. Empty directories "/QIBM/ProdData/OS400/Navigator/appdata" and
"/QIBM/ProdData/OS400/Navigator/appdata/iWebNav.eba" will be created.
-- These two empty directories are to avoid PGM CHKPRDOPT reporting an
error if they don't exist.
Heritage Navigator can be restored by restoring the appdata directory
with this command:
QSYS/RST DEV('/QSYS.LIB/QGPL.LIB/QINAVSAVF.FILE') OBJ('/QIBM/ProdData/OS400/Navigator/appdata')
Then start ADMIN2.
</blockquote>
Artifacts (a, b): No such object exists, which is another sign
heritage Nav was not removed via PTF.
Artifacts (c, d): That directory exists, and contains more than just
the iWebNav.eba subdirectory, which also happens to not be empty. More
than not being removed, this suggests heritage Navigator is still
installed.
Item 2: Artifacts
Right now it looks like lines within a file are all that I see documented
at https://www.ibm.com/support/pages/node/6570961
All those files exist, and none of them have those lines. That
suggests that heritage Navigator is no longer configured. It seems
likely that this was done via applying the relevant group PTFs. I
don't know how to identify "March 2023" or "June 2023" group PTFs, but
it's hard to imagine this was done manually and intentionally by the
admins here. To underscore this piece of evidence, we still have a
system that was not updated over the weekend, and heritage Navigator
still works on that system. The three config files on the un-updated
system do contain those lines.
Can you figure out what jar files are removed by the following?
https://www.ibm.com/support/pages/security-bulletin-ibm-i-components-are-affected-cve-2021-4104-log4j-version-1x
I cannot, and I don't think it is worth doing. I've seen enough signs
pointing to heritage Navigator still being installed but
de-configured.
The last line on your second link (node 6570961) says:
<blockquote>
To add heritage IBM Navigator for i back to run under ADMIN2, add the
removed lines back and restart the ADMIN2 server.
</blockquote>
So there you have it. If my employers insist on making heritage Nav
available on the updated systems (not sure that they will, but if they
do...), that's how.
Related question, hopefully small, simple, and quick enough not to
necessitate starting another thread:
Do the latest versions of ACS "point to" new Navigator for i? Our shop
is using 1.1.8.8, and if I try to start Navigator, a browser window
opens with the URL ending in :2004/ibm/console, which I realize is for
the heritage Navigator. On the updated systems, this says "Not Found".
If we update our ACS, we'll get the new Nav by default, yes?
John Y.
midrange.com
