This document describes the way to secure your esp-link device. The security we imply is access over the network, not physical security : protection of your data against an intruder with access to the hardware is not our scope. Therefore, we consider the network port (the ESP's WiFi interface) as the interface to be secured, not the connection between the ESP and the attached microcontroller.

• telnet bridge
• web configuration
• OTA programming interface
• esp-link web server
• application interfaces provided by the maker

As from esp-link 3.0, the telnet bridge can be secured in various ways. All of the measures below can be applied to either of the two ports, independently.

• the port number can be changed (default port numbers are 23 and 2323)
• a port can be disabled
• it can be password protected
• access can be encrypted via SSL (this doesn't work yet at the time of this writing)

The esp-link source code has had builtin support for securing its web configuration for a long time.

It was now extended with simple code that'll read a CSV file called "webaccess.txt" from the local file system. You can upload a file with your credentials via the web server interface.

Until you've done so, assume that a default file with this content is present

	admin,s3cr3t

This means you need to enter "admin" as userid, and "s3cr3t" as password, when your browser session requests you to logon to esp-link.