![]() Run the following commands: ~]# cd ~]# mkdir ~]# dropbearkey -t rsa -f ~/.ssh/id_rsaĪfter the last command you will see an output like this: Generating key, this may take a while. Log into your gateway using either SSH or the Wirgrid. Setup the gateway to dial SSH on startup # We will also need to know the username you use to log into this server. As an example let’s say the hostname is. This will allow you to connect to the server even when the IP address changes.įor the next step you will need to know the hostname of this server. You should create a hostname to point to this server and use the hostname to ssh to the server. ![]() This server needs to be accesible via a public IP address on the internet. You will need a server or other computer running Linux or any other operating system which can be accessed via SSH. This can be used to dial another SSH connection from the server to the client via an existing SSH connection from the client to the server. SSH also has the ability of forwarding ports over this secure connection, creating in essense a simple VPN. This is however often blocked by firewalls and NATs. As long as the two devices can see each other on the internet the SSH connection can also be made from the server to the client. Depending on how invasive your vulnerability scanner is, you might get a lot of false positives for DoS on such a constrained platform.SSH is a secure connection between a client and server over which commands can be executed on the server. I have seen this kind of false positive specially on DoS vulnerabilities when a vulnerability scan is testing a vulnerability and the server becomes unresponsive. ![]() You might get some false positives on your lua webserver reacting like other known webservers when exploits are applied. Depending on if there is encryption, you might also see weak encryption findings. Vulnerability Scan results might show things like unencrypted http traffic, credentials transmitted in cleartext (if you have any credentials fields in the pages served by the web server) etc. ![]() If your server is running on esp8266, i would imagine that there is no much room for authentication and encryption of http traffic, but correct me if i am wrong). I do my vulnerability scanning with OpenVAS (I assume this is what you mean by pentesting?). So if someone just have a short answer what to expect in a DAST scan/pentest, it would be much appreciated. I could of course SAST test it instead, or too, but I think it will be hard to find a static code analyzer for the NodeMCU libraries and NUA scripting language easily ? I found some references here though: but it seems to be a long read.I might use ZAP or Burpsuite or similar DAST security test tool. Maybe it is possible to crash or reset the IoT device? Buffer overruns, XXS, call own code ? The test report might just conclude what I can foresee be that the the "user input needs to be sanitized"?Īnyone have any idea what such pentest of a generic IoT device generally reports? I ponder it might be a totally pointless exercise since the esp8266 www server (or rather its LUA programming libraries) might not have any security built into it, so basically it is "open doors" and everything with it is unsafe ? I have not, but shall DAST* security test, out of curiosity, an IoT device Nodemcu esp8266 With it I can for example show images captured in the camera I even think it has some image recognition built in, and I can switch on and off a relay for electrical current to a light bulb (110/220v A/C power)īefore I start pentest I though I better start thinking of what types of exploits one would be able to find and detect? Which sinister exploits I will be able to find, or rather ought be able to find given a proper pentest exercise? (And if I do not find exploits, my approach to the pentest of the Iot might be wrong)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |