× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. September 2014

Re: Shellshock

Paul,

You searched the ENTIRE IFS for anything named 'bash'. Wow.. that must've taken a long time to run!!

I wonder why you didn't restrict your search a bit? I mean, searching optical drives, network drives, and IBM i libraries (and the objects in them) seems like a huge amount of overkill for searching for a Unix tool. I'd just restrict it to the areas it's likely to be in... /bin, /usr/bin, /QopenSys/usr/bin, and maybe /usr/local/bin

The errors mean that the Unix-type APIs that are used to get information about a file got some errors when accessing those objects. Not sure why that would happen... but, at any rate, it's not relevant to the search for 'bash', since those all in native libraries (both locally, and on another network-accessed system named PENCOR06). So not relevant to the problem-at-hand.

-SK


On 9/29/2014 8:45 PM, Steinmetz, Paul wrote:
Mike,

Running CALL QP2TERM
cd /
find . -name bash

Returned the below results, not sure what this implies?


find: 0652-019 The status on ./QSYS.LIB/ICGTWYP1D.LIB/ICGWYINI.FILE/SEMAPHORE.MBR is not valid.
find: 0652-019 The status on ./QSYS.LIB/IVSD.LIB/IVOICEDISP.DTAARA is not valid.
find: 0652-019 The status on ./QSYS.LIB/MPLUS.LIB/MCCSYSS.DTAQ is not valid.
find: 0652-019 The status on ./QSYS.LIB/MPLUS.LIB/MPLUS.DTAQ is not valid.
find: 0652-019 The status on ./QSYS.LIB/MPLUS.LIB/PENCOR05.DTAQ is not valid.
find: 0652-019 The status on ./QSYS.LIB/MPLUS.LIB/PENCOR06.DTAQ is not valid.
find: 0652-019 The status on ./QSYS.LIB/MPLUS.LIB/PAGERQ.DTAARA is not valid.
find: 0652-019 The status on ./QSYS.LIB/SPYVIEW.LIB/MAG101.PGM is not valid.
find: 0652-019 The status on ./QFileSvr.400/PENCOR06/QSYS.LIB/COMPGM200.LIB is not valid.
....
find: 0652-019 The status on ./QFileSvr.400/PENCOR06/QSYS.LIB/QDSNX.LIB is not valid.
find: 0652-019 The status on ./QFileSvr.400/PENCOR06/QSYS.LIB/QFNTCPL.LIB is not valid.
find: 0652-019 The status on ./QFileSvr.400/PENCOR06/QSYS.LIB/QFNTWT.LIB is not valid.
find: 0652-019 The status on ./QFileSvr.400/PENCOR06/QSYS.LIB/QFNT00.LIB is not valid.
find: 0652-019 The status on ./QFileSvr.400/PENCOR06/QSYS.LIB/QFNT15.LIB is not valid.
find: 0652-019 The status on ./QFileSvr.400/PENCOR06/QSYS.LIB/QGDDM.LIB is not valid.
find: 0652-019 The status on ./QFileSvr.400/PENCOR06/QSYS.LIB/QGPL.LIB is not valid.
find: 0652-019 The status on ./QFileSvr.400/PENCOR06/QSYS.LIB/QGPLTEMP.LIB is not valid.
find: 0652-019 The status on ./QFileSvr.400/PENCOR06/QSYS.LIB/QGY.LIB is not valid.
find: 0652-019 The status on ./QFileSvr.400/PENCOR06/QSYS.LIB/QHASM.LIB is not valid.
find: 0652-019 The status on ./QFileSvr.400/PENCOR06/QSYS.LIB/QHLPSYS.LIB is not valid.
find: 0652-019 The status on ./QFileSvr.400/PENCOR06/QSYS.LIB/QHTTP.LIB is not valid.
find: 0652-019 The status on ./QFileSvr.400/PENCOR06/QSYS.LIB/QHTTPSVR.LIB is not valid.
find: 0652-019 The status on ./QFileSvr.400/PENCOR06/QSYS.LIB/QIBMSSD.LIB is not valid.
find: 0652-019 The status on ./QFileSvr.400/PENCOR06/QSYS.LIB/QIBS.LIB is not valid.
find: 0652-031 ./QFileSvr.400/PENCOR06/QSYS.LIB is not a valid directory.
$

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Sue Baker
Sent: Monday, September 29, 2014 7:49 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Shellshock

Mike Cunningham <mike.cunningham@xxxxxxx> wrote on Mon, 29 Sep
2014 22:31:22 GMT:

Has anyone confirmed for sure if ibm i os needs to worry about the
shellshock bug?

Only if you have explicity installed GNU bash or you have installed another service which included GNU bash.

From Terry Ford, an expert on IBM i security in Lab Services who reached out to someone in development:

If you wish to check your IBM i systems, the easiest way is to search for the 'bash' binary by doing the following:

CALL QP2TERM (i.e. invoke an interactive PASE session)

Run the following commands from PASE. Note the find command will probably take some time to run.

cd /
find . -name bash

On my particular system the find command returned this result:

./QOpenSys/usr/bin/bash

I then ran the following command to verify where the bash binary was installed:

ls -l
/QOpenSys/usr/bin/bash

lrwxrwxrwx 1 rwatkin 0 54 May 25 2011
/QOpenSys/usr/bin/bash -> ../../opt/freeware/bin/bash

End result: Bash is installed here /opt/freeware/bin/bash. From personal experience I know that this is the location used when installing some of the open source binaries using one of the methods documented on the Yips website...

www.youngiprofessionals.com/wiki/index.php/PASE/OpenSourceBinari
es

--
Sue
IBM Americas Advanced Technical Sales Support (ATS) Power Systems Rochester, MN
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.