Am 27.02.2013 21:21, schrieb Eero Volotinen: > 2013/2/27 Reindl Harald <[email protected]>: >> you simply need to exclude "libmicrohttpd" from ANY >> repo which is NOT atomic and "yum downgrade libmicrohttpd" > > Failed to set locale, defaulting to C > Loaded plugins: fastestmirror, refresh-packagekit > Loading mirror speeds from cached hostfile > * atomic: www7.atomicorp.com > * base: centos.mirror.triple-it.nl > * extras: mirror.1000mbps.com > * updates: centos.mirror.triple-it.nl > Installed Packages > Name : libmicrohttpd > Arch : x86_64 > Version : 0.9.7 > Release : 1.el6.art > Size : 95 k > Repo : installed >>From repo : atomic > Summary : Lightweight library for embedding a webserver in applications > URL : http://www.gnu.org/software/libmicrohttpd/ > License : LGPLv2+
and you have surely restarted any involved service after the downgrade? sorry, but CentOS6+atomic is the most reliebale combination you will find since openVAS is a diva like no other software and this combination works well here since months since i was giving up on Fedora after nearly a year except broken NVTupdates making nmap unusebale well, "WARNING: Your version of nmap is not fully supported: 6.25" is not a compliment, not for OpebnVAS and not for atomic which are dumb enough to ignore this fat and pack a newer nmap to override the RHEL defaults.... but it works _____________________ [root@openvas:~]$ openvas-check-setup openvas-check-setup 2.2.0 Test completeness and readiness of OpenVAS-5 Please report us any non-detected problems and help us to improve this check routine: http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss Send us the log-file (/tmp/openvas-check-setup.log) to help analyze the problem. Use the parameter --server to skip checks for client tools like GSD and OpenVAS-CLI. Step 1: Checking OpenVAS Scanner ... OK: OpenVAS Scanner is present in version 3.3.1. OK: OpenVAS Scanner CA Certificate is present as /var/lib/openvas/CA/cacert.pem. OK: NVT collection in /var/lib/openvas/plugins contains 29831 NVTs. OK: Signature checking of NVTs is enabled in OpenVAS Scanner. Step 2: Checking OpenVAS Manager ... OK: OpenVAS Manager is present in version 3.0.5. OK: OpenVAS Manager client certificate is present as /var/lib/openvas/CA/clientcert.pem. OK: OpenVAS Manager database found in /var/lib/openvas/mgr/tasks.db. OK: Access rights for the OpenVAS Manager database are correct. OK: sqlite3 found, extended checks of the OpenVAS Manager installation enabled. OK: OpenVAS Manager database is at revision 56. OK: OpenVAS Manager expects database at revision 56. OK: Database schema is up to date. OK: OpenVAS Manager database contains information about 29724 NVTs. OK: xsltproc found. Step 3: Checking OpenVAS Administrator ... OK: OpenVAS Administrator is present in version 1.2.1. OK: At least one user exists. OK: At least one admin user exists. Step 4: Checking Greenbone Security Assistant (GSA) ... OK: Greenbone Security Assistant is present in version 3.0.3. Step 5: Checking OpenVAS CLI ... OK: OpenVAS CLI version 1.1.5. Step 6: Checking Greenbone Security Desktop (GSD) ... OK: Greenbone Security Desktop is present in Version 1.2.2. Step 7: Checking if OpenVAS services are up and running ... OK: netstat found, extended checks of the OpenVAS services enabled. OK: OpenVAS Scanner is running and listening only on the local interface. OK: OpenVAS Scanner is listening on port 9391, which is the default port. WARNING: OpenVAS Manager is running and listening only on the local interface. This means that you will not be able to access the OpenVAS Manager from the outside using GSD or OpenVAS CLI. SUGGEST: Ensure that OpenVAS Manager listens on all interfaces. OK: OpenVAS Manager is listening on port 9390, which is the default port. OK: OpenVAS Administrator is running and listening only on the local interface. OK: OpenVAS Administrator is listening on port 9393, which is the default port. OK: Greenbone Security Assistant is running and listening on all interfaces. OK: Greenbone Security Assistant is listening on port 443, which is the default port. Step 8: Checking nmap installation ... WARNING: Your version of nmap is not fully supported: 6.25 SUGGEST: You should install nmap 5.51. Step 9: Checking presence of optional tools ... OK: pdflatex found. OK: PDF generation successful. The PDF report format is likely to work. OK: ssh-keygen found, LSC credential generation for GNU/Linux targets is likely to work. OK: rpm found, LSC credential package generation for RPM based targets is likely to work. WARNING: Could not find alien binary, LSC credential package generation for DEB based targets will not work. SUGGEST: Install alien. OK: nsis found, LSC credential package generation for Microsoft Windows targets is likely to work. It seems like your OpenVAS-5 installation is OK. If you think it is not OK, please report your observation and help us to improve this check routine: http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss Please attach the log-file (/tmp/openvas-check-setup.log) to help us analyze the problem.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Openvas-discuss mailing list [email protected] https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
