in001w">Code [lin001w]
Code [lin002i]
A program installed in your system has probably been not installed been installed by the administrator note that /usr/local/ is the
by a package of your Linux packaging system. If this binary hasCode [lin002i]
Code [lin002i]
Installed processes listening on Internet interfaces must be Installed processes listening on Internet interfaces must be place for this files. place for this files. place for this files. been installed by the administrator note that /usr/local/ is the been installed by the administrator note that /usr/local/ is the
been installed by the administrator note that /usr/local/ is the
by a package of your Linux packaging system. If this binary has
Code [lin001w]
Installed processes listening on Internet interfaces must be
tightly controlled since they are the "open doors" to the
been installed by the administrator note that /usr/local/ is the
Code [lin002i]
place for this files.
Code [lin002i]
Code [lin001w]
place for this files.
place for this files.
Code [lin002i]
Installed processes listening on Internet interfaces must be
place for this files.
tightly controlled since they are the "open doors" to the
outside.
Code [lin002i]
Code [lin002i]
outside.
Code [lin002i]
Code [lin002i]
Code [lin002i]
Code [lin002i]
Installed processes listening on Internet interfaces must be
Code [lin002i]
Code [lin003w]
Code [lin002i]
Code [lin002i]
Code [lin002i]
Code [lin002i]
Code [lin003w]
Code [lin003w]
tightly controlled since they are the "open doors" to the
outside.
Code [lin002i]
tightly controlled since they are the "open doors" to the
tightly controlled since they are the "open doors" to the
Installed processes listening on Internet interfaces must be
Installed processes listening on Internet interfaces must be
tightly controlled since they are the "open doors" to the
Code [lin002i]
Installed processes listening on Internet interfaces must be
outside.
Processes that have not been run by root are listening on
been installed by the administrator note that /usr/local/ is the
Code [lin002i]
Code [lin002i]
Installed processes listening on Internet interfaces must be
Code [lin002i]
Code [lin002i]
Code [lin002i]
Installed processes listening on Internet interfaces must be
tightly controlled since they are the "open doors" to the
Code [lin002i]
Code [lin002i]
Code [lin002i]
Code [lin002i]
Installed processes listening on Internet interfaces must be
Code [lin002i]
Code [lin002i]
Code [lin002i]
Code [lin002i]
place for this files.
Code [lin003w]
Processes that have not been run by root are listening on
Processes that have not been run by root are listening on
Installed processes listening on Internet interfaces must be
outside.
Installed processes listening on Internet interfaces must be
Code [lin003w]
tightly controlled since they are the "open doors" to the
tightly controlled since they are the "open doors" to the
Code [lin003w]
outside.
Code [lin002i]
tightly controlled since they are the "open doors" to the
interfaces open to the outside. This processes might have been
run by root and changed uids or might be rogue processes.
outside.
run by root and changed uids or might be rogue processes.
Processes that have not been run by root are listening on
Code [lin003w]
Code [lin003w]
Code [lin003w]
Code [lin003w]
outside.
Code [lin002i]
Code [lin003w]
Code [lin003w]
Processes that have not been run by root are listening on
Code [lin003w]
Code [lin003w]
Code [lin003w]
interfaces open to the outside. This processes might have been
Code [lin003w]
Code [lin003w]
Code [lin003w]
Code [lin003w]
interfaces open to the outside. This processes might have been
interfaces open to the outside. This processes might have been
interfaces open to the outside. This processes might have been
Processes that have not been run by root are listening on
Code [lin003w]
Processes that have not been run by root are listening on
tightly controlled since they are the "open doors" to the
Processes that have not been run by root are listening on
Processes that have not been run by root are listening on
run by root and changed uids or might be rogue processes.
Code [lin003w]
Code [lin003w]
Code [lin003w]
Code [lin003w]
Code [lin003w]
Code [lin003w]
Code [lin003w]
interfaces open to the outside. This processes might have been
Code [lin003w]
Code [lin003w]
Code [lin003w]
receive DNS requests, if you receive reports on open UDP services
Code [lin003w]
Processes that have not been run by root are listening on
outside.
Processes that have not been run by root are listening on
Code [lin003w]
Code [lin003w]
Confirm if their presence is necessary.
run by root and changed uids or might be rogue processes.
Notice that sometimes services open sporadic UDP listeners to
receive DNS requests, if you receive reports on open UDP services
Processes that have not been run by root are listening on
Processes that have not been run by root are listening on
receive DNS requests, if you receive reports on open UDP services
run by root and changed uids or might be rogue processes.
run by root and changed uids or might be rogue processes.
interfaces open to the outside. This processes might have been
run by root and changed uids or might be rogue processes.
interfaces open to the outside. This processes might have been
Confirm if their presence is necessary.
Processes that have not been run by root are listening on
outside.
Processes that have not been run by root are listening on
interfaces open to the outside. This processes might have been
Processes that have not been run by root are listening on
Processes that have not been run by root are listening on
Processes that have not been run by root are listening on
interfaces open to the outside. This processes might have been
Processes that have not been run by root are listening on
Processes that have not been run by root are listening on
run by root and changed uids or might be rogue processes.
Processes that have not been run by root are listening on
Processes that have not been run by root are listening on
Processes that have not been run by root are listening on
Processes that have not been run by root are listening on
Code [lin003w]
Confirm if their presence is necessary.
interfaces open to the outside. This processes might have been
interfaces open to the outside. This processes might have been
interfaces open to the outside. This processes might have been
run by root and changed uids or might be rogue processes.
interfaces open to the outside. This processes might have been
interfaces open to the outside. This processes might have been
interfaces open to the outside. This processes might have been
run by root and changed uids or might be rogue processes.
interfaces open to the outside. This processes might have been
Code [lin003w]
run by root and changed uids or might be rogue processes.
Confirm if their presence is necessary.
Notice that sometimes services open sporadic UDP listeners to
Confirm if their presence is necessary.
receive DNS requests, if you receive reports on open UDP services
Code [lin004i]
run by root and changed uids or might be rogue processes.
Confirm if their presence is necessary.
run by root and changed uids or might be rogue processes.
run by root and changed uids or might be rogue processes.
Confirm if their presence is necessary.
run by root and changed uids or might be rogue processes.
run by root and changed uids or might be rogue processes.
Confirm if their presence is necessary.
run by root and changed uids or might be rogue processes.
run by root and changed uids or might be rogue processes.
receive DNS requests, if you receive reports on open UDP services
that later on are closed this might be a false positive.
Code [lin004i]
Code [lin004i]
receive DNS requests, if you receive reports on open UDP services
Notice that sometimes services open sporadic UDP listeners to
that later on are closed this might be a false positive.
Confirm if their presence is necessary.
Confirm if their presence is necessary.
Confirm if their presence is necessary.
Confirm if their presence is necessary.
interfaces open to the outside. This processes might have been
Confirm if their presence is necessary.
receive DNS requests, if you receive reports on open UDP services
Confirm if their presence is necessary.
Confirm if their presence is necessary.
Notice that sometimes services open sporadic UDP listeners to
Netstat can be used instead of lsof in order to provide information
Confirm if their presence is necessary.
Notice that sometimes services open sporadic UDP listeners to
Confirm if their presence is necessary.
Confirm if their presence is necessary.
Notice that sometimes services open sporadic UDP listeners to
Confirm if their presence is necessary.
Confirm if their presence is necessary.
that later on are closed this might be a false positive.
Confirm if their presence is necessary.
Confirm if their presence is necessary.
Notice that sometimes services open sporadic UDP listeners to
Code [lin004i]
Code [lin004i]
Notice that sometimes services open sporadic UDP listeners to
Notice that sometimes services open sporadic UDP listeners to
Code [lin004i]
on listening processes, however it will provide less info since it
Code [lin004i]
receive DNS requests, if you receive reports on open UDP services
that later on are closed this might be a false positive.
receive DNS requests, if you receive reports on open UDP services
on listening processes, however it will provide less info since it
cannot determine the process (or PID) associated with the open socket
Confirm if their presence is necessary.
Netstat can be used instead of lsof in order to provide information
Code [lin004i]
that later on are closed this might be a false positive.
Code [lin004i]
cannot determine the process (or PID) associated with the open socket
that later on are closed this might be a false positive.
Code [lin004i]
that later on are closed this might be a false positive.
that later on are closed this might be a false positive.
Code [lin004i]
that later on are closed this might be a false positive.
that later on are closed this might be a false positive.
that later on are closed this might be a false positive.
that later on are closed this might be a false positive.
Code [lin004i]
Netstat can be used instead of lsof in order to provide information
Code [lin004i]
Code [lin004i]
Netstat can be used instead of lsof in order to provide information
Code [lin004i]
Code [lin004i]
on listening processes, however it will provide less info since it
Code [lin004i]
Code [lin004i]
Code [lin004i]
on listening processes, however it will provide less info since it
receive DNS requests, if you receive reports on open UDP services
Code [lin004i]
Netstat can be used instead of lsof in order to provide information
Code [lin004i]
Code [lin004i]
Code [lin004i]
on listening processes, however it will provide less info since it
Netstat can be used instead of lsof in order to provide information
Netstat can be used instead of lsof in order to provide information
Code [lin004i]
on listening processes, however it will provide less info since it
Code [lin004i]
Code [lin004i]
that later on are closed this might be a false positive.
Code [lin004i]
on listening processes, however it will provide less info since it
Netstat can be used instead of lsof in order to provide information
Code [lin004i]
Code [lin004i]
Code [lin004i]
Code [lin004i]
Code [lin004i]
Code [lin005f]
cannot determine the process (or PID) associated with the open socket
Netstat can be used instead of lsof in order to provide information
or the user that runs it.
Code [lin005f]
Code [lin004i]
Netstat can be used instead of lsof in order to provide information
Code [lin005f]
Netstat can be used instead of lsof in order to provide information
that later on are closed this might be a false positive.
cannot determine the process (or PID) associated with the open socket
Netstat can be used instead of lsof in order to provide information
or the user that runs it.
Netstat can be used instead of lsof in order to provide information
Netstat can be used instead of lsof in order to provide information
on listening processes, however it will provide less info since it
cannot determine the process (or PID) associated with the open socket
Netstat can be used instead of lsof in order to provide information
Netstat can be used instead of lsof in order to provide information
Netstat can be used instead of lsof in order to provide information
on listening processes, however it will provide less info since it
cannot determine the process (or PID) associated with the open socket
cannot determine the process (or PID) associated with the open socket
Netstat can be used instead of lsof in order to provide information
on listening processes, however it will provide less info since it
Netstat can be used instead of lsof in order to provide information
Code [lin005f]
Netstat can be used instead of lsof in order to provide information
Code [lin004i]
cannot determine the process (or PID) associated with the open socket
on listening processes, however it will provide less info since it
or the user that runs it.
on listening processes, however it will provide less info since it
on listening processes, however it will provide less info since it
In Debian systems, checksums are stored in /var/lib/dpkg/info/
cannot determine the process (or PID) associated with the open socket
on listening processes, however it will provide less info since it
on listening processes, however it will provide less info since it
on listening processes, however it will provide less info since it
on listening processes, however it will provide less info since it
on listening processes, however it will provide less info since it
Code [lin005f]
if the md5sum of a file differs from the checksum of installed packages
cannot determine the process (or PID) associated with the open socket
Code [lin004i]
if the md5sum of a file differs from the checksum of installed packages
cannot determine the process (or PID) associated with the open socket
Code [lin005f]
Code [lin005f]
or the user that runs it.
it might be due to changes made by the system administrator (for
it might be due to changes made by the system administrator (for
or the user that runs it.
In Debian systems, checksums are stored in /var/lib/dpkg/info/
or the user that runs it.
or the user that runs it.
it might be due to changes made by the system administrator (for
Code [lin005f]
or the user that runs it.
Code [lin005f]
Code [lin005f]
or the user that runs it.
or the user that runs it.
on listening processes, however it will provide less info since it
or the user that runs it.
Code [lin005f]
Code [lin005f]
Code [lin005f]
Code [lin005f]
In Debian systems, checksums are stored in /var/lib/dpkg/info/
Code [lin005f]
Code [lin005f]
Code [lin005f]
Code [lin005f]
cannot determine the process (or PID) associated with the open socket
Code [lin005f]
(who might have placed a trojan instead of the checked file)
Code [lin005f]
if the md5sum of a file differs from the checksum of installed packages
(who might have placed a trojan instead of the checked file)
it might be due to changes made by the system administrator (for
if the md5sum of a file differs from the checksum of installed packages
Code [lin005f]
(who might have placed a trojan instead of the checked file)
Code [lin005f]
Code [lin005f]
In Debian systems, checksums are stored in /var/lib/dpkg/info/
In Debian systems, checksums are stored in /var/lib/dpkg/info/
Code [lin005f]
if the md5sum of a file differs from the checksum of installed packages
if the md5sum of a file differs from the checksum of installed packages
Code [lin005f]
or the user that runs it.
In Debian systems, checksums are stored in /var/lib/dpkg/info/
In Debian systems, checksums are stored in /var/lib/dpkg/info/
if the md5sum of a file differs from the checksum of installed packages
Code [lin005f]
In Debian systems, checksums are stored in /var/lib/dpkg/info/
Code [lin005f]
Code [lin005f]
Code [lin005f]
Code [lin005f]
Code [lin005f]
Code [lin005f]
Code [lin005f]
In Debian systems, checksums are stored in /var/lib/dpkg/info/
(who might have placed a trojan instead of the checked file)
In Debian systems, checksums are stored in /var/lib/dpkg/info/
or the user that runs it.
example, files in /etc) by everyday use of by a possible intruder
Be forewarned, an attacker might have modified this info files
In Debian systems, checksums are stored in /var/lib/dpkg/info/
example, files in /etc) by everyday use of by a possible intruder
it might be due to changes made by the system administrator (for
In Debian systems, checksums are stored in /var/lib/dpkg/info/
Be forewarned, an attacker might have modified this info files
In Debian systems, checksums are stored in /var/lib/dpkg/info/
In Debian systems, checksums are stored in /var/lib/dpkg/info/
it might be due to changes made by the system administrator (for
In Debian systems, checksums are stored in /var/lib/dpkg/info/
if the md5sum of a file differs from the checksum of installed packages
if the md5sum of a file differs from the checksum of installed packages
Be forewarned, an attacker might have modified this info files
In Debian systems, checksums are stored in /var/lib/dpkg/info/
it might be due to changes made by the system administrator (for
it might be due to changes made by the system administrator (for
Code [lin005f]
example, files in /etc) by everyday use of by a possible intruder
it might be due to changes made by the system administrator (for
if the md5sum of a file differs from the checksum of installed packages
example, files in /etc) by everyday use of by a possible intruder
it might be due to changes made by the system administrator (for
if the md5sum of a file differs from the checksum of installed packages
if the md5sum of a file differs from the checksum of installed packages
if the md5sum of a file differs from the checksum of installed packages
it might be due to changes made by the system administrator (for
if the md5sum of a file differs from the checksum of installed packages
if the md5sum of a file differs from the checksum of installed packages
if the md5sum of a file differs from the checksum of installed packages
if the md5sum of a file differs from the checksum of installed packages
it might be due to changes made by the system administrator (for
if the md5sum of a file differs from the checksum of installed packages
Code [lin005f]
it might be due to changes made by the system administrator (for
(they are not protected against this)
it might be due to changes made by the system administrator (for
Be forewarned, an attacker might have modified this info files
Code [lin006w]
example, files in /etc) by everyday use of by a possible intruder
In Debian systems, checksums are stored in /var/lib/dpkg/info/
Code [lin006w]
(they are not protected against this)
example, files in /etc) by everyday use of by a possible intruder
(who might have placed a trojan instead of the checked file)
Be forewarned, an attacker might have modified this info files
example, files in /etc) by everyday use of by a possible intruder
Code [lin006w]
(who might have placed a trojan instead of the checked file)
example, files in /etc) by everyday use of by a possible intruder
Be forewarned, an attacker might have modified this info files
example, files in /etc) by everyday use of by a possible intruder
Be forewarned, an attacker might have modified this info files
if the md5sum of a file differs from the checksum of installed packages
example, files in /etc) by everyday use of by a possible intruder
Be forewarned, an attacker might have modified this info files
(who might have placed a trojan instead of the checked file)
(who might have placed a trojan instead of the checked file)
example, files in /etc) by everyday use of by a possible intruder
example, files in /etc) by everyday use of by a possible intruder
(who might have placed a trojan instead of the checked file)
example, files in /etc) by everyday use of by a possible intruder
example, files in /etc) by everyday use of by a possible intruder
example, files in /etc) by everyday use of by a possible intruder
example, files in /etc) by everyday use of by a possible intruder
(who might have placed a trojan instead of the checked file)
example, files in /etc) by everyday use of by a possible intruder
Code [lin006w]
example, files in /etc) by everyday use of by a possible intruder
(who might have placed a trojan instead of the checked file)
A file installed by a package no longer exists in the system and
if the md5sum of a file differs from the checksum of installed packages
Code [lin006w]
(who might have placed a trojan instead of the checked file)
Be forewarned, an attacker might have modified this info files
A file installed by a package no longer exists in the system and
it might be due to changes made by the system administrator (for
Be forewarned, an attacker might have modified this info files
(who might have placed a trojan instead of the checked file)
cannot be checked for. An administrator should not remove files from
Code [lin006w]
Be forewarned, an attacker might have modified this info files
cannot be checked for. An administrator should not remove files from
(they are not protected against this)
Code [lin006w]
example, files in /etc) by everyday use of by a possible intruder
Code [lin006w]
the system, they should be removed uninstalling the packages that
Be forewarned, an attacker might have modified this info files
A file installed by a package no longer exists in the system and
(they are not protected against this)
the system, they should be removed uninstalling the packages that
Code [lin006w]
Code [lin006w]
(they are not protected against this)
(who might have placed a trojan instead of the checked file)
Code [lin006w]
the system, they should be removed uninstalling the packages that
Code [lin006w]
the system, they should be removed uninstalling the packages that
cannot be checked for. An administrator should not remove files from
Code [lin006w]
A file installed by a package no longer exists in the system and
Code [lin006w]
Code [lin006w]
Code [lin006w]
Code [lin006w]
Code [lin006w]
Code [lin006w]
Code [lin006w]
cannot be checked for. An administrator should not remove files from
Code [lin006w]
Code [lin006w]
Code [lin006w]
cannot be checked for. An administrator should not remove files from
(they are not protected against this)
Code [lin006w]
Code [lin006w]
Code [lin006w]
Code [lin006w]
Code [lin006w]
A file installed by a package no longer exists in the system and
Code [lin006w]
Code [lin006w]
Code [lin006w]
A file installed by a package no longer exists in the system and
Code [lin006w]
provided them. This is an unusual behavior.
A file installed by a package no longer exists in the system and
(they are not protected against this)
Code [lin006w]
Code [lin007w]
the system, they should be removed uninstalling the packages that
Code [lin007w]
cannot be checked for. An administrator should not remove files from
provided them. This is an unusual behavior.
A file installed by a package no longer exists in the system and
the system, they should be removed uninstalling the packages that
A file installed by a package no longer exists in the system and
the system, they should be removed uninstalling the packages that
Code [lin007w]
A file installed by a package no longer exists in the system and
A file installed by a package no longer exists in the system and
A file installed by a package no longer exists in the system and
cannot be checked for. An administrator should not remove files from
A file installed by a package no longer exists in the system and
cannot be checked for. An administrator should not remove files from
A file installed by a package no longer exists in the system and
A file installed by a package no longer exists in the system and
A file installed by a package no longer exists in the system and
the system, they should be removed uninstalling the packages that
cannot be checked for. An administrator should not remove files from
Code [lin007w]
A file installed by a package no longer exists in the system and
In the default configuration of many GNU/Linux distributions users can
cannot be checked for. An administrator should not remove files from
provided them. This is an unusual behavior.
provided them. This is an unusual behavior.
cannot be checked for. An administrator should not remove files from
Code [lin006w]
cannot be checked for. An administrator should not remove files from
the system, they should be removed uninstalling the packages that
cannot be checked for. An administrator should not remove files from
cannot be checked for. An administrator should not remove files from
provided them. This is an unusual behavior.
the system, they should be removed uninstalling the packages that
Code [lin007w]
cannot be checked for. An administrator should not remove files from
cannot be checked for. An administrator should not remove files from
In the default configuration of many GNU/Linux distributions users can
provided them. This is an unusual behavior.
reboot the machine pressing Ctrl+Alt+Delete while in console mode. This can
cannot be checked for. An administrator should not remove files from
the system, they should be removed uninstalling the packages that
the system, they should be removed uninstalling the packages that
Code [lin006w]
A file installed by a package no longer exists in the system and
Code [lin007w]
provided them. This is an unusual behavior.
the system, they should be removed uninstalling the packages that
Code [lin007w]
Code [lin007w]
reboot the machine pressing Ctrl+Alt+Delete while in console mode. This can
the system, they should be removed uninstalling the packages that
provided them. This is an unusual behavior.
Code [lin007w]
In the default configuration of many GNU/Linux distributions users can
Code [lin007w]
be considered a security risk if an attacker can easily taken down the
provided them. This is an unusual behavior.
provided them. This is an unusual behavior.
provided them. This is an unusual behavior.
provided them. This is an unusual behavior.
Code [lin007w]
Code [lin007w]
be considered a security risk if an attacker can easily taken down the
In the default configuration of many GNU/Linux distributions users can
provided them. This is an unusual behavior.
Code [lin007w]
the system, they should be removed uninstalling the packages that
server from console.
cannot be checked for. An administrator should not remove files from
In the default configuration of many GNU/Linux distributions users can
Code [lin007w]
Code [lin007w]
Code [lin007w]
Code [lin007w]
Code [lin007w]
reboot the machine pressing Ctrl+Alt+Delete while in console mode. This can
In the default configuration of many GNU/Linux distributions users can
Code [lin007w]
Code [lin007w]
In the default configuration of many GNU/Linux distributions users can
the system, they should be removed uninstalling the packages that
reboot the machine pressing Ctrl+Alt+Delete while in console mode. This can
Code [lin007w]
Code [lin007w]
Code [lin007w]
Code [lin007w]
be considered a security risk if an attacker can easily taken down the
Code [lin007w]
Code [lin007w]
In the default configuration of many GNU/Linux distributions users can
Code [lin007w]
Code [lin007w]
reboot the machine pressing Ctrl+Alt+Delete while in console mode. This can
In the default configuration of many GNU/Linux distributions users can
Code [lin007w]
Code [lin007w]
Code [lin007w]
Code [lin007w]
server from console.
be considered a security risk if an attacker can easily taken down the
be considered a security risk if an attacker can easily taken down the
Code [lin007w]
In the default configuration of many GNU/Linux distributions users can
Code [lin008e]
In the default configuration of many GNU/Linux distributions users can
In the default configuration of many GNU/Linux distributions users can
reboot the machine pressing Ctrl+Alt+Delete while in console mode. This can
provided them. This is an unusual behavior.
Code [lin008e]
Code [lin008e]
In the default configuration of many GNU/Linux distributions users can
In the default configuration of many GNU/Linux distributions users can
In the default configuration of many GNU/Linux distributions users can
In the default configuration of many GNU/Linux distributions users can
reboot the machine pressing Ctrl+Alt+Delete while in console mode. This can
server from console.
be considered a security risk if an attacker can easily taken down the
reboot the machine pressing Ctrl+Alt+Delete while in console mode. This can
In the default configuration of many GNU/Linux distributions users can
reboot the machine pressing Ctrl+Alt+Delete while in console mode. This can
In the default configuration of many GNU/Linux distributions users can
In the default configuration of many GNU/Linux distributions users can
be considered a security risk if an attacker can easily taken down the
In the default configuration of many GNU/Linux distributions users can
In the default configuration of many GNU/Linux distributions users can
reboot the machine pressing Ctrl+Alt+Delete while in console mode. This can
In the default configuration of many GNU/Linux distributions users can
In the default configuration of many GNU/Linux distributions users can
Code [lin008e]
Code [lin007w]
reboot the machine pressing Ctrl+Alt+Delete while in console mode. This can
reboot the machine pressing Ctrl+Alt+Delete while in console mode. This can
be considered a security risk if an attacker can easily taken down the
Code [lin008e]
The /proc pseudo-filesystem is needed to check the network configuration
reboot the machine pressing Ctrl+Alt+Delete while in console mode. This can
Code [lin007w]
be considered a security risk if an attacker can easily taken down the
server from console.
be considered a security risk if an attacker can easily taken down the
be considered a security risk if an attacker can easily taken down the
settings in the kernel and determine insecure setups. /proc is available
Code [lin008e]
be considered a security risk if an attacker can easily taken down the
Code [lin008e]
tightly controlled since they are the "open doors" to the
outside.
been installed by the administrator note that /usr/local/ is the
been installed by the administrator note that /usr/local/ is the
been installed by the administrator note that /usr/local/ is the
place for this files.
been installed by the administrator note that /usr/local/ is the
been installed by the administrator note that /usr/local/ is the
been installed by the administrator note that /usr/local/ is the
been installed by the administrator note that /usr/local/ is the
place for this files.
been installed by the administrator note that /usr/local/ is the
been installed by the administrator note that /usr/local/ is the
been installed by the administrator note that /usr/local/ is the
been installed by the administrator note that /usr/local/ is the
been installed by the administrator note that /usr/local/ is the
been installed by the administrator note that /usr/local/ is the
been installed by the administrator note that /usr/local/ is the
place for this files.
been installed by the administrator note that /usr/local/ is the
A program installed in your system has probably been not installed
A program installed in your system has probably been not installed
place for this files.
Installed processes listening on Internet interfaces must be
place for this files.
place for this files.
place for this files.
place for this files.
place for this files.
place for this files.
place for this files.
place for this files.
place for this files.
place for this files.
place for this files.
place for this files.
place for this files.
place for this files.
by a package of your Linux packaging system. If this binary has
outside.
Installed processes listening on Internet interfaces must be
Installed processes listening on Internet interfaces must be
tightly controlled since they are the "open doors" to the
Installed processes listening on Internet interfaces must be
by a package of your Linux packaging system. If this binary has
tightly controlled since they are the "open doors" to the
Installed processes listening on Internet interfaces must be
been installed by the administrator note that /usr/local/ is the
outside.
outside.
tightly controlled since they are the "open doors" to the
outside.
tightly controlled since they are the "open doors" to the
Installed processes listening on Internet interfaces must be
tightly controlled since they are the "open doors" to the
Installed processes listening on Internet interfaces must be
place for this files.
Installed processes listening on Internet interfaces must be
tightly controlled since they are the "open doors" to the
interfaces open to the outside. This processes might have been
Installed processes listening on Internet interfaces must be
Installed processes listening on Internet interfaces must be
Installed processes listening on Internet interfaces must be
Installed processes listening on Internet interfaces must be
Installed processes listening on Internet interfaces must be
Installed processes listening on Internet interfaces must be
Installed processes listening on Internet interfaces must be
tightly controlled since they are the "open doors" to the
tightly controlled since they are the "open doors" to the
Installed processes listening on Internet interfaces must be
outside.
Installed processes listening on Internet interfaces must be
Installed processes listening on Internet interfaces must be
Installed processes listening on Internet interfaces must be
Processes that have not been run by root are listening on
interfaces open to the outside. This processes might have been
interfaces open to the outside. This processes might have been
outside.
outside.
outside.
tightly controlled since they are the "open doors" to the
tightly controlled since they are the "open doors" to the
run by root and changed uids or might be rogue processes.
tightly controlled since they are the "open doors" to the
tightly controlled since they are the "open doors" to the
tightly controlled since they are the "open doors" to the
tightly controlled since they are the "open doors" to the
tightly controlled since they are the "open doors" to the
tightly controlled since they are the "open doors" to the
outside.
tightly controlled since they are the "open doors" to the
tightly controlled since they are the "open doors" to the
tightly controlled since they are the "open doors" to the
tightly controlled since they are the "open doors" to the
outside.
tightly controlled since they are the "open doors" to the
Processes that have not been run by root are listening on
outside.
outside.
Confirm if their presence is necessary.
outside.
outside.
outside.
outside.
outside.
outside.
outside.
outside.
outside.
outside.
Installed processes listening on Internet interfaces must be
outside.
outside.
run by root and changed uids or might be rogue processes.
interfaces open to the outside. This processes might have been
Confirm if their presence is necessary.
Processes that have not been run by root are listening on
Confirm if their presence is necessary.
Processes that have not been run by root are listening on
Processes that have not been run by root are listening on
Installed processes listening on Internet interfaces must be
Processes that have not been run by root are listening on
Notice that sometimes services open sporadic UDP listeners to
tightly controlled since they are the "open doors" to the
run by root and changed uids or might be rogue processes.
Notice that sometimes services open sporadic UDP listeners to
Confirm if their presence is necessary.
interfaces open to the outside. This processes might have been
Notice that sometimes services open sporadic UDP listeners to
Processes that have not been run by root are listening on
interfaces open to the outside. This processes might have been
that later on are closed this might be a false positive.
interfaces open to the outside. This processes might have been
Processes that have not been run by root are listening on
Processes that have not been run by root are listening on
Notice that sometimes services open sporadic UDP listeners to
Confirm if their presence is necessary.
that later on are closed this might be a false positive.
receive DNS requests, if you receive reports on open UDP services
interfaces open to the outside. This processes might have been
interfaces open to the outside. This processes might have been
Confirm if their presence is necessary.
that later on are closed this might be a false positive.
Confirm if their presence is necessary.
Confirm if their presence is necessary.
run by root and changed uids or might be rogue processes.
run by root and changed uids or might be rogue processes.
Notice that sometimes services open sporadic UDP listeners to
interfaces open to the outside. This processes might have been
interfaces open to the outside. This processes might have been
interfaces open to the outside. This processes might have been
interfaces open to the outside. This processes might have been
run by root and changed uids or might be rogue processes.
interfaces open to the outside. This processes might have been
interfaces open to the outside. This processes might have been
run by root and changed uids or might be rogue processes.
interfaces open to the outside. This processes might have been
Notice that sometimes services open sporadic UDP listeners to
receive DNS requests, if you receive reports on open UDP services
that later on are closed this might be a false positive.
Notice that sometimes services open sporadic UDP listeners to
Notice that sometimes services open sporadic UDP listeners to
run by root and changed uids or might be rogue processes.
run by root and changed uids or might be rogue processes.
run by root and changed uids or might be rogue processes.
run by root and changed uids or might be rogue processes.
run by root and changed uids or might be rogue processes.
run by root and changed uids or might be rogue processes.
Processes that have not been run by root are listening on
Notice that sometimes services open sporadic UDP listeners to
Confirm if their presence is necessary.
run by root and changed uids or might be rogue processes.
run by root and changed uids or might be rogue processes.
receive DNS requests, if you receive reports on open UDP services
receive DNS requests, if you receive reports on open UDP services
Confirm if their presence is necessary.
Confirm if their presence is necessary.
Processes that have not been run by root are listening on
Notice that sometimes services open sporadic UDP listeners to
Netstat can be used instead of lsof in order to provide information
interfaces open to the outside. This processes might have been
Notice that sometimes services open sporadic UDP listeners to
that later on are closed this might be a false positive.
Netstat can be used instead of lsof in order to provide information
receive DNS requests, if you receive reports on open UDP services
Notice that sometimes services open sporadic UDP listeners to
that later on are closed this might be a false positive.
Notice that sometimes services open sporadic UDP listeners to
that later on are closed this might be a false positive.
Notice that sometimes services open sporadic UDP listeners to
receive DNS requests, if you receive reports on open UDP services
Notice that sometimes services open sporadic UDP listeners to
Notice that sometimes services open sporadic UDP listeners to
Notice that sometimes services open sporadic UDP listeners to
that later on are closed this might be a false positive.
receive DNS requests, if you receive reports on open UDP services
Notice that sometimes services open sporadic UDP listeners to
run by root and changed uids or might be rogue processes.
Notice that sometimes services open sporadic UDP listeners to
Notice that sometimes services open sporadic UDP listeners to
Notice that sometimes services open sporadic UDP listeners to
receive DNS requests, if you receive reports on open UDP services
Notice that sometimes services open sporadic UDP listeners to
on listening processes, however it will provide less info since it
receive DNS requests, if you receive reports on open UDP services
Notice that sometimes services open sporadic UDP listeners to
Notice that sometimes services open sporadic UDP listeners to
receive DNS requests, if you receive reports on open UDP services
Netstat can be used instead of lsof in order to provide information
on listening processes, however it will provide less info since it
receive DNS requests, if you receive reports on open UDP services
run by root and changed uids or might be rogue processes.
that later on are closed this might be a false positive.
receive DNS requests, if you receive reports on open UDP services
receive DNS requests, if you receive reports on open UDP services
receive DNS requests, if you receive reports on open UDP services
receive DNS requests, if you receive reports on open UDP services
receive DNS requests, if you receive reports on open UDP services
that later on are closed this might be a false positive.
receive DNS requests, if you receive reports on open UDP services
receive DNS requests, if you receive reports on open UDP services
that later on are closed this might be a false positive.
Confirm if their presence is necessary.
receive DNS requests, if you receive reports on open UDP services
receive DNS requests, if you receive reports on open UDP services
receive DNS requests, if you receive reports on open UDP services
that later on are closed this might be a false positive.
receive DNS requests, if you receive reports on open UDP services
receive DNS requests, if you receive reports on open UDP services
that later on are closed this might be a false positive.
cannot determine the process (or PID) associated with the open socket
receive DNS requests, if you receive reports on open UDP services
Netstat can be used instead of lsof in order to provide information
that later on are closed this might be a false positive.
that later on are closed this might be a false positive.
that later on are closed this might be a false positive.
Notice that sometimes services open sporadic UDP listeners to
or the user that runs it.
that later on are closed this might be a false positive.
that later on are closed this might be a false positive.
that later on are closed this might be a false positive.
that later on are closed this might be a false positive.
Netstat can be used instead of lsof in order to provide information
cannot determine the process (or PID) associated with the open socket
on listening processes, however it will provide less info since it
that later on are closed this might be a false positive.
or the user that runs it.
Notice that sometimes services open sporadic UDP listeners to
Netstat can be used instead of lsof in order to provide information
or the user that runs it.
on listening processes, however it will provide less info since it
Netstat can be used instead of lsof in order to provide information
receive DNS requests, if you receive reports on open UDP services
cannot determine the process (or PID) associated with the open socket
or the user that runs it.
cannot determine the process (or PID) associated with the open socket
on listening processes, however it will provide less info since it
Netstat can be used instead of lsof in order to provide information
Netstat can be used instead of lsof in order to provide information
Netstat can be used instead of lsof in order to provide information
Netstat can be used instead of lsof in order to provide information
In Debian systems, checksums are stored in /var/lib/dpkg/info/
Netstat can be used instead of lsof in order to provide information
on listening processes, however it will provide less info since it
Netstat can be used instead of lsof in order to provide information
or the user that runs it.
In Debian systems, checksums are stored in /var/lib/dpkg/info/
on listening processes, however it will provide less info since it
In Debian systems, checksums are stored in /var/lib/dpkg/info/
on listening processes, however it will provide less info since it
on listening processes, however it will provide less info since it
on listening processes, however it will provide less info since it
or the user that runs it.
on listening processes, however it will provide less info since it
or the user that runs it.
on listening processes, however it will provide less info since it
cannot determine the process (or PID) associated with the open socket
on listening processes, however it will provide less info since it
on listening processes, however it will provide less info since it
cannot determine the process (or PID) associated with the open socket
or the user that runs it.
cannot determine the process (or PID) associated with the open socket
on listening processes, however it will provide less info since it
cannot determine the process (or PID) associated with the open socket
if the md5sum of a file differs from the checksum of installed packages
cannot determine the process (or PID) associated with the open socket
cannot determine the process (or PID) associated with the open socket
cannot determine the process (or PID) associated with the open socket
or the user that runs it.
cannot determine the process (or PID) associated with the open socket
cannot determine the process (or PID) associated with the open socket
or the user that runs it.
Netstat can be used instead of lsof in order to provide information
or the user that runs it.
cannot determine the process (or PID) associated with the open socket
or the user that runs it.
cannot determine the process (or PID) associated with the open socket
cannot determine the process (or PID) associated with the open socket
cannot determine the process (or PID) associated with the open socket
or the user that runs it.
if the md5sum of a file differs from the checksum of installed packages
cannot determine the process (or PID) associated with the open socket
cannot determine the process (or PID) associated with the open socket
cannot determine the process (or PID) associated with the open socket
cannot determine the process (or PID) associated with the open socket
cannot determine the process (or PID) associated with the open socket
Netstat can be used instead of lsof in order to provide information
In Debian systems, checksums are stored in /var/lib/dpkg/info/
or the user that runs it.
or the user that runs it.
or the user that runs it.
it might be due to changes made by the system administrator (for
or the user that runs it.
or the user that runs it.
or the user that runs it.
or the user that runs it.
or the user that runs it.
if the md5sum of a file differs from the checksum of installed packages
or the user that runs it.
on listening processes, however it will provide less info since it
In Debian systems, checksums are stored in /var/lib/dpkg/info/
example, files in /etc) by everyday use of by a possible intruder
example, files in /etc) by everyday use of by a possible intruder
if the md5sum of a file differs from the checksum of installed packages
example, files in /etc) by everyday use of by a possible intruder
In Debian systems, checksums are stored in /var/lib/dpkg/info/
In Debian systems, checksums are stored in /var/lib/dpkg/info/
In Debian systems, checksums are stored in /var/lib/dpkg/info/
cannot determine the process (or PID) associated with the open socket
example, files in /etc) by everyday use of by a possible intruder
it might be due to changes made by the system administrator (for
In Debian systems, checksums are stored in /var/lib/dpkg/info/
if the md5sum of a file differs from the checksum of installed packages
it might be due to changes made by the system administrator (for
if the md5sum of a file differs from the checksum of installed packages
In Debian systems, checksums are stored in /var/lib/dpkg/info/
In Debian systems, checksums are stored in /var/lib/dpkg/info/
if the md5sum of a file differs from the checksum of installed packages
In Debian systems, checksums are stored in /var/lib/dpkg/info/
In Debian systems, checksums are stored in /var/lib/dpkg/info/
In Debian systems, checksums are stored in /var/lib/dpkg/info/
In Debian systems, checksums are stored in /var/lib/dpkg/info/
In Debian systems, checksums are stored in /var/lib/dpkg/info/
In Debian systems, checksums are stored in /var/lib/dpkg/info/
if the md5sum of a file differs from the checksum of installed packages
Be forewarned, an attacker might have modified this info files
if the md5sum of a file differs from the checksum of installed packages
(who might have placed a trojan instead of the checked file)
if the md5sum of a file differs from the checksum of installed packages
(they are not protected against this)
if the md5sum of a file differs from the checksum of installed packages
example, files in /etc) by everyday use of by a possible intruder
(who might have placed a trojan instead of the checked file)
if the md5sum of a file differs from the checksum of installed packages
if the md5sum of a file differs from the checksum of installed packages
example, files in /etc) by everyday use of by a possible intruder
it might be due to changes made by the system administrator (for
(they are not protected against this)
if the md5sum of a file differs from the checksum of installed packages
(they are not protected against this)
it might be due to changes made by the system administrator (for
example, files in /etc) by everyday use of by a possible intruder
if the md5sum of a file differs from the checksum of installed packages
it might be due to changes made by the system administrator (for
(who might have placed a trojan instead of the checked file)
(who might have placed a trojan instead of the checked file)
it might be due to changes made by the system administrator (for
Be forewarned, an attacker might have modified this info files
it might be due to changes made by the system administrator (for
example, files in /etc) by everyday use of by a possible intruder
it might be due to changes made by the system administrator (for
example, files in /etc) by everyday use of by a possible intruder
(who might have placed a trojan instead of the checked file)
it might be due to changes made by the system administrator (for
example, files in /etc) by everyday use of by a possible intruder
(who might have placed a trojan instead of the checked file)
example, files in /etc) by everyday use of by a possible intruder
it might be due to changes made by the system administrator (for
In Debian systems, checksums are stored in /var/lib/dpkg/info/
(who might have placed a trojan instead of the checked file)
it might be due to changes made by the system administrator (for
example, files in /etc) by everyday use of by a possible intruder
it might be due to changes made by the system administrator (for
it might be due to changes made by the system administrator (for
example, files in /etc) by everyday use of by a possible intruder
it might be due to changes made by the system administrator (for
it might be due to changes made by the system administrator (for
it might be due to changes made by the system administrator (for
it might be due to changes made by the system administrator (for
it might be due to changes made by the system administrator (for
(they are not protected against this)
example, files in /etc) by everyday use of by a possible intruder
Be forewarned, an attacker might have modified this info files
example, files in /etc) by everyday use of by a possible intruder
(who might have placed a trojan instead of the checked file)
(they are not protected against this)
A file installed by a package no longer exists in the system and
Be forewarned, an attacker might have modified this info files
(who might have placed a trojan instead of the checked file)
(they are not protected against this)
(who might have placed a trojan instead of the checked file)
A file installed by a package no longer exists in the system and
Be forewarned, an attacker might have modified this info files
(they are not protected against this)
(who might have placed a trojan instead of the checked file)
(who might have placed a trojan instead of the checked file)
it might be due to changes made by the system administrator (for
(who might have placed a trojan instead of the checked file)
(they are not protected against this)
(they are not protected against this)
Be forewarned, an attacker might have modified this info files
(who might have placed a trojan instead of the checked file)
Be forewarned, an attacker might have modified this info files
(who might have placed a trojan instead of the checked file)
Be forewarned, an attacker might have modified this info files
(who might have placed a trojan instead of the checked file)
(who might have placed a trojan instead of the checked file)
(who might have placed a trojan instead of the checked file)
(who might have placed a trojan instead of the checked file)
Be forewarned, an attacker might have modified this info files
(who might have placed a trojan instead of the checked file)
Be forewarned, an attacker might have modified this info files
cannot be checked for. An administrator should not remove files from
Be forewarned, an attacker might have modified this info files
(they are not protected against this)
Be forewarned, an attacker might have modified this info files
example, files in /etc) by everyday use of by a possible intruder
Be forewarned, an attacker might have modified this info files
(they are not protected against this)
Be forewarned, an attacker might have modified this info files
(they are not protected against this)
Be forewarned, an attacker might have modified this info files
(they are not protected against this)
Be forewarned, an attacker might have modified this info files
Be forewarned, an attacker might have modified this info files
Be forewarned, an attacker might have modified this info files
(they are not protected against this)
Be forewarned, an attacker might have modified this info files
A file installed by a package no longer exists in the system and
(they are not protected against this)
cannot be checked for. An administrator should not remove files from
Be forewarned, an attacker might have modified this info files
Be forewarned, an attacker might have modified this info files
(they are not protected against this)
(they are not protected against this)
(they are not protected against this)
(they are not protected against this)
(they are not protected against this)
(they are not protected against this)
(they are not protected against this)
(they are not protected against this)
(they are not protected against this)
(they are not protected against this)
cannot be checked for. An administrator should not remove files from
A file installed by a package no longer exists in the system and
(who might have placed a trojan instead of the checked file)
provided them. This is an unusual behavior.
(they are not protected against this)
(they are not protected against this)
(they are not protected against this)
A file installed by a package no longer exists in the system and
provided them. This is an unusual behavior.
A file installed by a package no longer exists in the system and
Be forewarned, an attacker might have modified this info files
provided them. This is an unusual behavior.
A file installed by a package no longer exists in the system and
the system, they should be removed uninstalling the packages that
Be forewarned, an attacker might have modified this info files
cannot be checked for. An administrator should not remove files from
cannot be checked for. An administrator should not remove files from
the system, they should be removed uninstalling the packages that
A file installed by a package no longer exists in the system and
A file installed by a package no longer exists in the system and
provided them. This is an unusual behavior.
A file installed by a package no longer exists in the system and
cannot be checked for. An administrator should not remove files from
A file installed by a package no longer exists in the system and
cannot be checked for. An administrator should not remove files from
the system, they should be removed uninstalling the packages that
A file installed by a package no longer exists in the system and
A file installed by a package no longer exists in the system and
A file installed by a package no longer exists in the system and
cannot be checked for. An administrator should not remove files from
A file installed by a package no longer exists in the system and
A file installed by a package no longer exists in the system and
the system, they should be removed uninstalling the packages that
provided them. This is an unusual behavior.
In the default configuration of many GNU/Linux distributions users can
cannot be checked for. An administrator should not remove files from
In the default configuration of many GNU/Linux distributions users can
cannot be checked for. An administrator should not remove files from
cannot be checked for. An administrator should not remove files from
the system, they should be removed uninstalling the packages that
cannot be checked for. An administrator should not remove files from
the system, they should be removed uninstalling the packages that
cannot be checked for. An administrator should not remove files from
cannot be checked for. An administrator should not remove files from
cannot be checked for. An administrator should not remove files from
provided them. This is an unusual behavior.
cannot be checked for. An administrator should not remove files from
the system, they should be removed uninstalling the packages that
the system, they should be removed uninstalling the packages that
reboot the machine pressing Ctrl+Alt+Delete while in console mode. This can
reboot the machine pressing Ctrl+Alt+Delete while in console mode. This can
the system, they should be removed uninstalling the packages that
provided them. This is an unusual behavior.
the system, they should be removed uninstalling the packages that
the system, they should be removed uninstalling the packages that
provided them. This is an unusual behavior.
provided them. This is an unusual behavior.
the system, they should be removed uninstalling the packages that
the system, they should be removed uninstalling the packages that
the system, they should be removed uninstalling the packages that
the system, they should be removed uninstalling the packages that
provided them. This is an unusual behavior.
the system, they should be removed uninstalling the packages that
the system, they should be removed uninstalling the packages that
In the default configuration of many GNU/Linux distributions users can
the system, they should be removed uninstalling the packages that
the system, they should be removed uninstalling the packages that
be considered a security risk if an attacker can easily taken down the
provided them. This is an unusual behavior.
cannot be checked for. An administrator should not remove files from
A file installed by a package no longer exists in the system and
provided them. This is an unusual behavior.
be considered a security risk if an attacker can easily taken down the
provided them. This is an unusual behavior.
provided them. This is an unusual behavior.
provided them. This is an unusual behavior.
provided them. This is an unusual behavior.
provided them. This is an unusual behavior.
provided them. This is an unusual behavior.
provided them. This is an unusual behavior.
reboot the machine pressing Ctrl+Alt+Delete while in console mode. This can
provided them. This is an unusual behavior.
In the default configuration of many GNU/Linux distributions users can
server from console.
reboot the machine pressing Ctrl+Alt+Delete while in console mode. This can
In the default configuration of many GNU/Linux distributions users can
server from console.
In the default configuration of many GNU/Linux distributions users can
be considered a security risk if an attacker can easily taken down the
reboot the machine pressing Ctrl+Alt+Delete while in console mode. This can
server from console.
provided them. This is an unusual behavior.
reboot the machine pressing Ctrl+Alt+Delete while in console mode. This can
In the default configuration of many GNU/Linux distributions users can
In the default configuration of many GNU/Linux distributions users can
reboot the machine pressing Ctrl+Alt+Delete while in console mode. This can
be considered a security risk if an attacker can easily taken down the
In the default configuration of many GNU/Linux distributions users can
server from console.
server from console.
be considered a security risk if an attacker can easily taken down the
In the default configuration of many GNU/Linux distributions users can
The /proc pseudo-filesystem is needed to check the network configuration
reboot the machine pressing Ctrl+Alt+Delete while in console mode. This can
server from console.
The /proc pseudo-filesystem is needed to check the network configuration
reboot the machine pressing Ctrl+Alt+Delete while in console mode. This can
reboot the machine pressing Ctrl+Alt+Delete while in console mode. This can
The /proc pseudo-filesystem is needed to check the network configuration
reboot the machine pressing Ctrl+Alt+Delete while in console mode. This can
be considered a security risk if an attacker can easily taken down the
server from console.
reboot the machine pressing Ctrl+Alt+Delete while in console mode. This can
be considered a security risk if an attacker can easily taken down the
be considered a security risk if an attacker can easily taken down the
reboot the machine pressing Ctrl+Alt+Delete while in console mode. This can
reboot the machine pressing Ctrl+Alt+Delete while in console mode. This can
server from console.
reboot the machine pressing Ctrl+Alt+Delete while in console mode. This can
reboot the machine pressing Ctrl+Alt+Delete while in console mode. This can
be considered a security risk if an attacker can easily taken down the
reboot the machine pressing Ctrl+Alt+Delete while in console mode. This can
reboot the machine pressing Ctrl+Alt+Delete while in console mode. This can
reboot the machine pressing Ctrl+Alt+Delete while in console mode. This can
reboot the machine pressing Ctrl+Alt+Delete while in console mode. This can
In the default configuration of many GNU/Linux distributions users can
settings in the kernel and determine insecure setups. /proc is available
server from console.
be considered a security risk if an attacker can easily taken down the
settings in the kernel and determine insecure setups. /proc is available
be considered a security risk if an attacker can easily taken down the
server from console.
server from console.
be considered a security risk if an attacker can easily taken down the
server from console.
be considered a security risk if an attacker can easily taken down the
be considered a security risk if an attacker can easily taken down the
be considered a security risk if an attacker can easily taken down the
server from console.
be considered a security risk if an attacker can easily taken down the
be considered a security risk if an attacker can easily taken down the
be considered a security risk if an attacker can easily taken down the
be considered a security risk if an attacker can easily taken down the
The /proc pseudo-filesystem is needed to check the network configuration