Technology Insights

Dell OMSA Repo Install Error On CentOS: Command line error: no such option: –disableplugin

I wrote another article recently about an issue when attempting to install the srvadmin-all RPM package provided by the Dell OMSA repository. It is likely that when you are installing the OMSA repository that you will receive an error on CentOS and possibly on other versions of Linux. The yum OMSA repository is installed via a file available from Dell called bootstrap.cgi. Below I describe the issue when installing the OMSA repository and provide a couple methods to resolve the problem.

Technology Errors

make: *** No rule to make target -largtable2, needed by ../../bin/linux/release/CUDA-Multiforcer. Stop.

When attempting to compile the CUDA Multiforcer on CentOS Linux I ran into an error because the argtable2 package was not installed on the server. The CUDA Multiforcer application is a security audit tool used to check the strength of MD4, MD5, NTLM, and SHA1 password hashes. The CUDA Multiforcer attempts to brute force one of those types of hashes by attempting every combination of characters specified such as lowercase only characters, lowercase characters and numbers, etc. This tool can be extremely beneficial for checking the strength of user passwords for various operating systems and/or applications that store their passwords in a MD4, MD5, NTLM, or SHA1 hash. As you can see in the below error the issue appears to be with argtable2 which is not a package available with the default yum repositories on CentOS. Below I display the error and describe what repository to install to be able to use yum to install the argtable2 RPM package.

Technology Errors

/usr/include/gnu/stubs.h:7:27: error: gnu/stubs-32.h: No such file or directory

When compiling an application called pyrit on a new CentOS Linux server I ran into an issue with some libraries. Pyrit is an application used to perform dictionary attacks against WPA handshakes and can be really useful for security auditing. The error below is easily resolved on any version of Linux by simply installing the glibc-devel RPM package. Below I display the error in detail as well as how to resolve the error on CentOS by installing the glibc-devel RPM using the Yum package manager.