CentOS 5 and the BigFix Client

Installing this was a bit more difficult compared to the easy as pie SuSE and the Fedora 14 installs…

Following the instructions for the RedHat install, but downloading the CentOS client from the BigFix website (http://support.bigfix.com/bes/install/besclients-nonwindows.html)

Couldn’t get it to start and unlike Fedora 14, I received no indication as to what the problem was…
After solving the Fedora 14 install problem, I figured I’d try the same solution and I was successful…

Using the “setsebool -P allow_execstack 1” command, i was able to get it working finally… see (https://danielheth.com/2010/11/13/red-hat-fedora-14-and-bigfix-client-software/) for details.

Also reference (http://forum.bigfix.com/viewtopic.php?pid=25813#p25813) for additional information…

Red Hat Fedora 14 and BigFix Client Software

Finally got the client working on my Fedora 14 test box…

basically following the instructions on the bigfix website: http://support.bigfix.com/bes/install/besclients-nonwindows.html

Ran into a problem with the basic instructions though… a fresh install of Fedora 14 apparently has additional restrictions and would not allow the libBEScrypto library to function properly… i got the following error while attempting to launch the BESClient:

[root@fedora1 BESClient]# /etc/init.d/besclient start Starting BESClient: /opt/BESClient/bin/BESClient: error while loading shared libraries: libBEScrypto_1_0_0_1.so: cannot enable executable stack as shared object requires: Permission denied
[FAILED]

As it turns out the solution was simple… and i’m working via the BigFix forum thread (http://forum.bigfix.com/viewtopic.php?pid=25812#p25812) to explain to me why it worked… but basically to get the client started and working I had to run the following command:

setsebool -P allow_execstack 1

then using the “/etc/init.d/besclient start”, the client started right up…

Installing BigFix Client onto SuSE 11

Here is how to install BigFix onto SuSE 11…

wget http://software.bigfix.com/download/bes/80/BESAgent-8.0.627.0-suse80.i386.rpm
wget ftp://ftp.isu.edu.tw/pub/Linux/OpenSuSE/distribution/10.3/repo/oss/suse/i586/compat-2007.4.18-31.i586.rpm
wget ftp://ftp.isu.edu.tw/pub/Linux/OpenSuSE/distribution/10.3/repo/oss/suse/i586/compat-libstdc++-5.0.7-86.i586.rpm

rpm -ivh compat-2007.4.18-31.i586.rpm
rpm -ivh compat-libstdc++-5.0.7-86.i586.rpm
rpm -ivh BESAgent-8.0.627.0-suse80.i386.rpm

then wget your masthead and put into /etc/opt/BESClient/actionsite.afxm

then start it with /etc/init.d/besclient start

reference: http://support.bigfix.com/bes/install/besclients-nonwindows.html

OpenSuSE: Disable firewall

Disable firewall completelyI was wondering… why I can’t connect through ssh. sshd daemon is running fine, so I found out that OpenSuSE installs its stikin’ firewall by default and blocks everything. I’m pretty well protected behind enough high end security devices, and don’t need to micro-manage my connection. Here is how I disabled the firewall altogether:

/sbin/SuSEfirewall2 offTo start the firewall:

/sbin/SuSEfirewall2 onIf you want to temporarily disable your firewall:

/etc/init.d/SuSEfirewall2_setup stopEnter the above line without “stop” and you will see all available switches.

TRACKBACK: http://insanelabs.com/linux/opensuse-disable-firewall-completely/