search

telekom-security / tpotce

🍯 T-Pot - The All In One Multi Honeypot Platform 🐝
GNU General Public License v3.0
6.66k stars 1.06k forks source link

no sensors found, Tpotce 18.11 #291

Closed AizazZaidee closed 5 years ago

AizazZaidee commented 5 years ago

Hello Support, When I run dps.sh it prints that no sensors are found.

No sensors found! Make sure you loaded all the kernel drivers you need. Try sensors-detect to find out which these are.

I can see Kibana running and it is being updated but I am unable to find SSH interaction logs, I am using Glutton. Glutton provide SSH and a TCP proxy. SSH proxy works as a MITM between attacker and server to log everything in plain text, but they are nowhere to be found. is this because sensors are not loaded?

I ran sensors-detect command and following is the output of this command.

# sensors-detect revision 6284 (2015-05-31 14:00:33 +0200)
# System: DigitalOcean Droplet [20171212]
# Kernel: 4.15.0-45-generic x86_64
# Processor: Intel(R) Xeon(R) Gold 6140 CPU @ 2.30GHz (6/85/4)

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): YES
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   No
AMD Family 10h thermal sensors...                           No
AMD Family 11h thermal sensors...                           No
AMD Family 12h and 14h thermal sensors...                   No
AMD Family 15h thermal sensors...                           No
AMD Family 16h thermal sensors...                           No
AMD Family 15h power sensors...                             No
AMD Family 16h power sensors...                             No
Intel digital thermal sensor...                             No
Intel AMB FB-DIMM thermal sensor...                         No
Intel 5500/5520/X58 thermal sensor...                       No
VIA C7 thermal sensor...                                    No
VIA Nano thermal sensor...                                  No

Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): YES
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      No
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      No

Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no): YES
Probing for `IPMI BMC KCS' at 0xca0...                      No
Probing for `IPMI BMC SMIC' at 0xca8...                     No

Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (YES/no): YES
Probing for `National Semiconductor LM78' at 0x290...       No
Probing for `National Semiconductor LM79' at 0x290...       No
Probing for `Winbond W83781D' at 0x290...                   No
Probing for `Winbond W83782D' at 0x290...                   No

Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): YES
Using driver `i2c-piix4' for device 0000:00:01.3: Intel 82371AB PIIX4 ACPI
modprobe: FATAL: Module i2c-piix4 not found in directory /lib/modules/4.15.0-45-generic
Failed to load module i2c-piix4.

Sorry, no sensors were detected.
Either your system has no sensors, or they are not supported, or
they are connected to an I2C or SMBus adapter that is not
supported. If you find out what chips are on your board, check
http://www.lm-sensors.org/wiki/Devices for driver status.

Thanks.

Basic support information

NAME STATUS PORTS adbhoney Up 8 hours 0.0.0.0:5555->5555/tcp ciscoasa Up 8 hours conpot_guardian_ast Up 8 hours 0.0.0.0:10001->10001/tcp conpot_iec104 Up 8 hours 0.0.0.0:161->161/tcp, 0.0.0.0:2404->2404/tcp conpot_ipmi Up 8 hours 0.0.0.0:623->623/tcp conpot_kamstrup_382 Up 8 hours 0.0.0.0:1025->1025/tcp, 0.0.0.0:50100->50100/tcp cowrie Up 8 hours 0.0.0.0:22-23->22-23/tcp cyberchef Up 8 hours (healthy) 127.0.0.1:64299->8000/tcp dionaea Up 8 hours elasticpot Up 8 hours 0.0.0.0:9200->9200/tcp elasticsearch Up 8 hours (healthy) 127.0.0.1:64298->9200/tcp ewsposter Up 8 hours glutton Up 8 hours head Up 8 hours (healthy) 127.0.0.1:64302->9100/tcp heralding Up 8 hours 0.0.0.0:110->110/tcp, 0.0.0.0:143->143/tcp, 0.0.0.0:993->993/tcp, 0.0.0.0:995->995/tcp, 0.0.0.0:5432->5432/tcp, 0.0.0.0:5900->5900/tcp kibana Up 8 hours (healthy) 127.0.0.1:64296->5601/tcp logstash Up 8 hours (healthy) mailoney Up 8 hours 0.0.0.0:25->25/tcp medpot Up 8 hours 0.0.0.0:2575->2575/tcp nginx Up 8 hours p0f Up 8 hours rdpy Up 8 hours 0.0.0.0:3389->3389/tcp snare Up 8 hours 0.0.0.0:80->80/tcp spiderfoot Up 8 hours (healthy) 127.0.0.1:64303->8080/tcp suricata Up 8 hours tanner Up 8 hours tanner_api Up 8 hours tanner_phpox Up 8 hours tanner_redis Up 8 hours 6379/tcp tanner_web Up 8 hours

t3chn0m4g3 commented 5 years ago

This is with regard to the temp sensors of the motherboard, since you are using T-Pot in a VM environment this is normal behaviour. Only Cowrie is configured to be a SSH honeypot.