Is there a way to turn off SSLv3 on the Greenbone Security Assistant?
___
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
wrote:
*** Daniel Malament wrote:
I don't seem to be finding the CVEs from this:
https://www.openssl.org/news/secadv_20140605.txt
in the CVE DB on my OpenVAS install, and I don't see anything more recent
than a month ago as far as OpenSSL-related vulnerabilities. Is there
currently a way
Missed that. D'oh. Thanks. Still wondering about those other two CVEs,
though:
CVE-2014-0198
CVE-2010-5298
On Mon, Jun 16, 2014 at 11:25 AM, Michael Meyer michael.me...@greenbone.net
wrote:
*** Daniel Malament wrote:
I have all three syncs running every night. I don't see any
I don't seem to be finding the CVEs from this:
https://www.openssl.org/news/secadv_20140605.txt
in the CVE DB on my OpenVAS install, and I don't see anything more recent
than a month ago as far as OpenSSL-related vulnerabilities. Is there
currently a way to scan for these vulnerabilities?
for
different directories, or do I have to just make symlinks from e.g.
/usr/local/var to /var?
On Tue, May 20, 2014 at 11:04 AM, Daniel Malament
daniel.j.malam...@gmail.com wrote:
Indeed. I was waiting to thank you until I got through the rest of the
upgrade, and then Things Intervened and I'm hoping
Since there aren't packages for OpenVAS 7 yet, I decided to just build it
from source. However, the first compilation is failing with all sorts of
ssh-related errors. This is on an up-to-date Ubuntu 14.04 box. Anyone
have any ideas?
--
cd openvas-libraries-7.0.1/
mkdir build
cd build
Since there aren't packages for OpenVAS 7 yet, I decided to just build it
from source. However, the first compilation is failing with all sorts of
ssh-related errors. This is on an up-to-date Ubuntu 14.04 box. Anyone
have any ideas?
--
cd openvas-libraries-7.0.1/
mkdir build
cd build
Thanks for the info. I have found that --update takes about 2.5 hours on
this system, whereas --rebuild takes 20 seconds. So I was planning to go
with this as my sync procedure:
openvas-nvt-sync
openvas-scapdata-sync
openvasmd --rebuild
/etc/init.d/openvas-scanner restart
(Sound ok?)
I have been having a strangely hard time finding solid answers online to a
pretty simple question: what is the proper way to fully update the NVTs in
an OpenVAS installation? That is, I'm running openvas-nvt-sync, but it
sounds like you're supposed to run openvasmd --update or openvasmd
--rebuild
That seems to have fixed it, but I'm now seeing a bunch of alerts that
weren't there before. Could that be related, or were a lot of NVTs
just updated / created in the last week or so?
On Sat, Feb 1, 2014 at 3:26 AM, Michael Meyer
michael.me...@greenbone.net wrote:
*** Daniel Malament wrote
We are evaluating OpenVAS at work, and we got several false positives for
this:
--
NVT: Multiple IP Video/Camera Server Web Interface Default Admin
Credentials (OID: 1.3.6.1.4.1.25623.1.0.103887)
It was possible to login using the following credentials:
3sadmin/27988303
root/root
11 matches
Mail list logo
