Am 07.10.2014 um 12:13 schrieb Christiaan DeVries christiaan.devr...@hetg.ie:
Hi everybody,
I’m getting false positives in my scan reports. In this case, I get reports
of a potential Trojan but it’s a HP ILO interface (op port 80) that’s
redirecting to port 443 (which is also reported
Am 26.09.2014 um 09:09 schrieb Chris fisch@gmx.de:
Is it CVE-2014-6271 detection available now?
yes since yesterday:
http://lists.wald.intevation.org/pipermail/openvas-nvts-commits/2014-September/000693.html
Does it really work? If I let it run against a webserver:
openvas-nasl -d
Am 26.09.2014 um 11:49 schrieb Christiaan DeVries christiaan.devr...@hetg.ie:
After running all synchronisations, am still don't have the shellshock
detection, any hints as to what could be wrong with my system?
Same here. I grabbed it directly from
Am 26.09.2014 um 11:44 schrieb Rainer Sokoll open...@sokoll.com:
Am 26.09.2014 um 09:09 schrieb Chris fisch@gmx.de:
Is it CVE-2014-6271 detection available now?
yes since yesterday:
http://lists.wald.intevation.org/pipermail/openvas-nvts-commits/2014-September/000693.html
Am 26.09.2014 um 14:05 schrieb Christiaan DeVries christiaan.devr...@hetg.ie:
I’m new as well, so take all cum grano salis ;-)
What exactly do you mean by the NVT needs a script to test? Basically, I'm
trying to come up with a way I can (mass) scan our networks but as I'm quite
new to
Am 26.09.2014 um 16:34 schrieb Xinhuan Zheng xzh...@christianbook.com:
Today I am trying to get the latest bash shellshock vulnerability plugin
via openvas rsync feed but I don¹t see it in my system.
[…]
I ran /usr/local/scripts/openvas-nvt-sync.sh. How do I get this plugin?
By reading
Hi,
a report gives me:
wapiti report filename is empty. that could mean that
wrong version of wapiti is used or tmp dir is not accessible.
Make sure to have wapiti 2.x as wapiti 1.x is not supported.
I’m on FC20, and yum info wapiti returns:
Name: wapiti
Arch: noarch
Version
Am 19.09.2014 um 13:06 schrieb Rainer Sokoll open...@sokoll.com:
my system: Fedora 20 with OpenVAS from atomiccorp. Everything seems to be
fine - except gsad eating all CPU right after logging in.
For the records:
After yum update gsad works as expected. No CPU issues anyone :-)
Rainer
Am 23.09.2014 um 13:47 schrieb Eero Volotinen eero.voloti...@iki.fi:
Atomiccorp repo works at least on centos 7, rhea 7
And Fedora 20 (beside gsad eating all CPU)
Rainer
___
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
Hi,
my system: Fedora 20 with OpenVAS from atomiccorp. Everything seems to be fine
- except gsad eating all CPU right after logging in.
By searching the web, I only found older posts saying libmicrohttpd is the
culprit, but, as said, these posts are quite old.
Am 14.09.2014 um 10:11 schrieb Michael Meyer michael.me...@greenbone.net:
Both with OV6 from Suses?s
I'm not sure about v6 and OpenSuse, but v6 and debian works. Why you
are using v6 and not v7?
Because I’m lazy and http://www.openvas.org/install-packages.html claims that
there are no
Hi,
I know this is a known issue. Once a browser connects to gsad, the daemon eats
all CPU.
What I do not understand:
~# ps x | grep gsad
23037 ?Sl31:38 /usr/sbin/gsad --listen=0.0.0.0 --port=9392
--mlisten=127.0.0.1 --mport=9390
~# strace -p 23037
Process 23037 attached
Am 13.09.2014 um 09:43 schrieb Michael Meyer michael.me...@greenbone.net:
*** Rainer Sokoll wrote:
It took me days to got OpenVAS running, well, sort of.
OpenSuse: no luck.
Works for me.
Debian: no luck.
Works for me,
Both with OV6 from Suses’s OBS?
Rainer
Hi,
I’ve searched the web, found some discussions regarding my problem, but nothing
helped.
So I’m asking here.
Platform: Fedora 20, openvas installed per instructions at
http://www.openvas.org/install-packages-v6.html#openvas_fedora_atomic.
Everything went smooth, but when I try to log in, all
Am 12.09.2014 um 16:47 schrieb Rainer Sokoll open...@sokoll.com:
Hi,
I’ve searched the web, found some discussions regarding my problem, but
nothing helped.
So I’m asking here.
Platform: Fedora 20, openvas installed per instructions at
http://www.openvas.org/install-packages-v6.html
Hi,
I started for testing purposes an immediate scan of one of my servers.
The scan finished, a report got created.
But when I look at the process list, dirb is still running and I can see it
hammering my web server:
GET /settings/guest.mdb HTTP/1.1 404 1038 - Mozilla/4.0 (compatible; MSIE
Am 12.09.2014 um 20:52 schrieb Reindl Harald h.rei...@thelounge.net:
[dirb still running after task completion]
that issue now exists for years
just forget dirb or overwrite the binary with a
symlink to /bin/true, maybe somebody cares in
a future release, i doubt
You sound frustrated.
17 matches
Mail list logo