Notus Scanner detects vulnerable products in a system environment. The scanning
method is to evaluate internal system information. It does this very fast and
even detects currently inactive products because it does not need to interact
with each of the products.
To report about vulnerabilities, Notus Scanner receives collected system
information on the one hand and accesses the vulnerability information from the
feed service on the other. Both input elements are in table form: the system
information is specific to each environment and the vulnerability information
is specific to each system type.
Notus Scanner integrates into the Greenbone Vulnerability Management framework
which allows to let it scan entire networks within a single task. Any
vulnerability test in the format of .notus files inside the Greenbone Feed will
be considered and automatically matched with the scanned environments.
NOTE: If this package has multiple flavors (see below), then use one of them instead of the name specified above. NOTE: This is a Python port. Instead of py312-notus-scanner listed in the above command, you can pick from the names under the Packages section.
security/gvm: Update to 26.0.0
security/gsa: Update to 25.0.0 (Only amd64 and aarch64)
security/gsad: Update to 24.3.0
security/openvas: Update to 23.30.1
security/gvmd: Update to 26.0.0
security/gvm-libs: 22.22.0
security/py-notus-scanner: Update to 22.7.2
security/py-ospd-openvas: Update to 22.9.0
security/py-python-gvm: Update to 26.2.1
python.mk: rename PYTHON_EXT_SUFFIX to PYTHON_TAG, document, etc
EXT_SUFFIX, according to PEP 3149, refers to the full tag and
extension for compiled extension module objects, eg .cpython-311.so,
.cpython-313t.so, etc. We do not use the correct semantic meaning,
and this usage becomes ambiguous and confusing when tags do not
match between bytecode and compiled extension module objects.
Rename our PYTHON_EXT_SUFFIX to PYTHON_TAG to align with PEP 3147's
specification of a magic tag, which consists of implementation name
and shorthand version only. This is meant for bytecode and other
files containing this tag in their filename that do not depend on
a specific Python ABI for the same version. Chase all existing
consumers.
(Only the first 15 lines of the commit message are shown above )
security/gvm: Update to 24.1.2
databases/pg-gvm: Update to 22.6.6
security/gsa: Update to 24.1.0 (Only amd64 and aarch64)
security/gsad: Update to 24.1.0
security/openvas: Update to 23.14.0
security/gvmd: Update to 24.1.2
security/gvm-libs: 22.15.0
security/py-notus-scanner: Update to 22.6.5
security/py-greenbone-feed-sync: Update to 24.9.0
security/py-ospd-openvas: Bump PORTREVISION
security/py-gvm-tools: Update to 24.12.1
security/py-python-gvm: Update to 24.12.0
security/gvm: update to 23.5.2
- databases/pg-gvm: update to 22.6.5
- security/gsa: update to 23.0.0
- security/gsad: update to 22.9.1
- security/gvm-libs: update to 22.9.1
- security/gvmd: update to 23.5.2
- security/openvas: update to 23.0.1
- security/py-gvm-tools: update to 24.3.0
- security/py-notus-scanner: update to 22.6.3
- security/py-ospd-openvas: update to 22.7.1
- security/py-python-gvm: update to 24.3.0
- security/py-greenbone-feed-sync: update to 24.3.0
security/gvm: update to 23.2.0
- databases/pg-gvm: update to 22.6.4
- security/gsa: update to 23.0.0
- security/gsad: update to 22.9.0
- security/gvm-libs: update to 22.8.0
- security/gvmd: update to 23.2.0
- security/openvas: update to 22.7.9
- security/py-gvm-tools: update to 24.1.0
- security/py-notus-scanner: update to 22.6.2
- security/py-ospd-openvas: update to 22.6.2
- security/py-python-gvm: update to 24.1.0
- security/py-greenbone-feed-sync: update to 23.10.0
security/gvm: update to 22.9.0
- databases/pg-gvm: update to 22.6.1
- security/gsa: update to 22.7.1
- security/gsad: update to 22.6.0
- security/gvm-libs: update to 22.7.1
- security/gvmd: update to 22.9.0
- security/openvas: update to 22.7.5
- security/py-gvm-tools: update to 23.9.0
- security/py-notus-scanner: update to 22.6.0
- security/py-ospd-openvas: update to 22.6.0
- security/py-python-gvm: update to 23.5.1
all: remove explicit versions in USES=python for "3.x+"
The logic in USES=python will automatically convert this to 3.8+ by
itself.
Adjust two ports that only had Python 3.7 mentioned but build fine
on Python 3.8 too.
finance/quickfix: mark BROKEN with PYTHON
libtool: compile: c++ -DHAVE_CONFIG_H -I. -I../.. -I -I. -I.. -I../.. -I../C++
-DLIBICONV_PLUG -DPYTHON_MAJOR_VERSION=3 -Wno-unused-variable
-Wno-maybe-uninitialized -O2 -pipe -DLIBICONV_PLUG -fstack-protector-strong
-fno-strict-aliasing -DLIBICONV_PLUG -Wall -ansi
-Wno-unused-command-line-argument -Wpointer-arith -Wwrite-strings
-Wno-overloaded-virtual -Wno-deprecated-declarations -Wno-deprecated -std=c++0x
-MT _quickfix_la-QuickfixPython.lo -MD -MP -MF
.deps/_quickfix_la-QuickfixPython.Tpo -c QuickfixPython.cpp -fPIC -DPIC -o
.libs/_quickfix_la-QuickfixPython.o
warning: unknown warning option '-Wno-maybe-uninitialized'; did you mean
'-Wno-uninitialized'? [-Wunknown-warning-option]
QuickfixPython.cpp:175:11: fatal error: 'Python.h' file not found
^~~~~~~~~~
1 warning and 1 error generated.
Reviewed by: portmgr, vishwin, yuri
Differential Revision: <https://reviews.freebsd.org/D40568>
security/py-notus-scanner: Bump PORTREVISION because a package with incomplete
files was built
PR: 270893
Reported by: Trond.Endrestol __at___ ximalas.info
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
security/py-notus-scanner: New port: scanner for creating results from local
security checks
Notus Scanner detects vulnerable products in a system environment. The scanning
method is to evaluate internal system information. It does this very fast and
even detects currently inactive products because it does not need to interact
with each of the products.
To report about vulnerabilities, Notus Scanner receives collected system
information on the one hand and accesses the vulnerability information from the
feed service on the other. Both input elements are in table form: the system
information is specific to each environment and the vulnerability information
is specific to each system type.
Notus Scanner integrates into the Greenbone Vulnerability Management framework
which allows to let it scan entire networks within a single task. Any
vulnerability test in the format of .notus files inside the Greenbone Feed will
be considered and automatically matched with the scanned environments.
WWW: https://github.com/greenbone/notus-scanner
