*** Eero Volotinen wrote:
Please stop trolling and just disable it.
The only reason that OpenVAS suggest to disable selinux is, that no one
ever take care about what's the problem. So at the end Brandon is right.
Micha
--
Michael Meyer OpenPGP Key: 0xAF069E9152A6EFA6
you should also disable selinux permanently
--
Eero
2015-05-11 23:13 GMT+03:00 Brian Chabot bcha...@millennialmedia.com:
Correction:
# systemctl status firewalld
should be:
# systemctl stop firewalld
# systemctl disable firewalld
On Mon, May 11, 2015 at 4:02 PM, Brian Chabot
well, you need to use epel 7, not epel 5 (el5) packages
eero
Sent from my iPad
On 11 May 2015, at 16:18, Brian Chabot bcha...@millennialmedia.com wrote:
Thanks! That cleared up a lot of issues but not all.
Whoever maintains the OpenVAS documentation may like to add installing
the EPEL
Message-
From: Openvas-discuss [mailto:openvas-discuss-boun...@wald.intevation.org] On
Behalf Of Brian Chabot
Sent: Tuesday, May 12, 2015 6:21 AM
To: openvas-discuss@wald.intevation.org
Subject: Re: [Openvas-discuss] Install from Binary Packages on CentOS
I'm not sold on the need to disable
Right. I got things working almost 100%. PDF export seems to not
work, but HTML does and that's fine for the moment.
For those it may benefit, here's my instructions list for installing
OpenVAS on a fresh CentOS 7 server:
Install CentOS7, minimal from ISO. Set passwords. Add DNS and DHCP
Please stop trolling and just disable it.
Eero
12.5.2015 4.12 ip. Brandon Perry bperry.volat...@gmail.com kirjoitti:
Right, but *why*? I never disable SELinux and have never had an issue.
Also, disabling it completely is likely not correct. If there is a
specific process that SELinux doesn't
Why should he do that? That seems a bit overkill?
On Tue, May 12, 2015 at 2:02 AM, Eero Volotinen eero.voloti...@iki.fi
wrote:
you should also disable selinux permanently
--
Eero
2015-05-11 23:13 GMT+03:00 Brian Chabot bcha...@millennialmedia.com:
Correction:
# systemctl status
Am 12.05.2015 um 15:05 schrieb Brandon Perry:
Why should he do that? That seems a bit overkill?
because OpenVAS should *always* run on a dedicated host / VM and
deisable SELinux was mentioned a magnitude of times by the OpenVAS
developers on that list?
On Tue, May 12, 2015 at 2:02 AM,
2015-05-12 23:07 GMT+03:00 Brian Chabot bcha...@millennialmedia.com:
Right. I got things working almost 100%. PDF export seems to not
work, but HTML does and that's fine for the moment.
follow this instructions how to get pdf's working:
The doc/redis_config.txt (from openvas-scanner) has some tips and
information on how OpenVAS expects redis to be set up (and also example
configs for 2.4 and 2.6).
What you are probably missing are:
unixsocket /tmp/redis.sock
unixsocketperm 700
You will also probably want to turn of
Right, but *why*? I never disable SELinux and have never had an issue.
Also, disabling it completely is likely not correct. If there is a specific
process that SELinux doesn't play nice with, you can lower SELinux
restrictiveness on a per-process level.
What process in OpenVAS does SELinux
I'm not sold on the need to disable SELinux here, but that may help.
At this point, I have the installation of OpenVAS up and running, but
when I ran my first scan, it completed with the following error:
WARNING: Cannot connect to KB at '/tmp/redis.sock': Connection refused'
So off to
OpenVAS will not work with selinux correctly.
You need to correctly configure redis as documented .
--
Eero
2015-05-12 16:20 GMT+03:00 Brian Chabot bcha...@millennialmedia.com:
I'm not sold on the need to disable SELinux here, but that may help.
At this point, I have the installation of
Hi,
Am I looking in the wrong place? I see no reference to redis NOR any
reference to SELinux in:
try to use the latest version of the openvas-check-setup like suggested.
This is suggesting that you should disable SELinux and is also checking if your
redis-setup is correctly configured.
On Tue, May 12, 2015 at 8:24 AM, Eero Volotinen eero.voloti...@iki.fi
wrote:
OpenVAS will not work with selinux correctly.
I want to know what this means. I have run hundreds of OpenVAS instances,
never disabled SELinux, and never had any issues.
I get that we think it won't work correctly,
Am I looking in the wrong place? I see no reference to redis NOR any
reference to SELinux in:
http://www.openvas.org/install-packages-v7.html (Installation guide)
https://wiki.openvas.org/index.php/Main_Page (site Wiki)
http://www.openvas.org/documentation.html (Documentation link)
These seem
Hello,
I inherited a set of OpenVAS installations and am in the process of
setting up a process to install and maintain OpenVAS on new systems.
I am currently testing the concept on virtual machines, but will be
performing the final roll-out on some much beefier physical boxes.
I have tried
Well, looks like you need to install epel 7 rpm repository to your machine,
before installing packages.
--
Eero
2015-05-08 18:48 GMT+03:00 Brian Chabot bcha...@millennialmedia.com:
Hello,
I inherited a set of OpenVAS installations and am in the process of
setting up a process to install and
Thanks! That cleared up a lot of issues but not all.
Whoever maintains the OpenVAS documentation may like to add installing
the EPEL repo to the binary installation instructions.
I still see:
Error: Package: python-httplib2-0.7.7-1.el5.noarch (epel)
Requires: python(abi) = 2.4
Yup. I got it working in CentOS7 with epel 7.
Does anyone know if/when RPMs for OpenVAS 8 will be available?
On Mon, May 11, 2015 at 10:54 AM, Eero Volotinen
eero.t.voloti...@gmail.com wrote:
well, you need to use epel 7, not epel 5 (el5) packages
eero
Sent from my iPad
On 11 May 2015,
That should be OpenVAS 8. Glad to see this thread, have been having the
same issue. We may want to add these details to the openvas install binary
packages page. EPEL7 isn't there by default.
On Mon, May 11, 2015 at 7:56 AM, Brian Chabot bcha...@millennialmedia.com
wrote:
Yup. I got it working
So I got it installed... Here's what I have:
Install CentOS7 Minimum. Connect to network/internet.
# yum install wget
# rpm -Uvh
http://download.fedoraproject.org/pub/epel/7/x86_64/e/epel-release-7-5.noarch.rpm
# wget -q -O - http://www.atomicorp.com/installers/atomic |sh
# yum upgrade -y
#
Correction:
# systemctl status firewalld
should be:
# systemctl stop firewalld
# systemctl disable firewalld
On Mon, May 11, 2015 at 4:02 PM, Brian Chabot
bcha...@millennialmedia.com wrote:
So I got it installed... Here's what I have:
Install CentOS7 Minimum. Connect to network/internet.
#
23 matches
Mail list logo
