| Risk | Mitigation | |-------|-------------| | | Anyone can read/write if server permits. Use --create only when necessary. | | No encryption | Credentials (if any fake ones) and data are plaintext. Use IPSec or VPN if needed. | | Directory traversal | --secure chroots the TFTP root. Avoid symbolic links pointing outside. | | DoS / Amplification | Rate-limit UDP/69. Use tftp-max-blocksize to cap resources. | | Firmware poisoning | Serve signed firmware images; validate hash on client. |
A is a software application or embedded system service that listens for incoming file transfer requests using the Trivial File Transfer Protocol (TFTP). Unlike its more famous cousin, FTP (File Transfer Protocol), TFTP is designed to be minimal.
Low-RAM microcontroller boards (e.g., ancient ARM9, MIPS routers) use TFTP to load FPGA bitstreams or application code bootloaders.
| Risk | Mitigation | |-------|-------------| | | Anyone can read/write if server permits. Use --create only when necessary. | | No encryption | Credentials (if any fake ones) and data are plaintext. Use IPSec or VPN if needed. | | Directory traversal | --secure chroots the TFTP root. Avoid symbolic links pointing outside. | | DoS / Amplification | Rate-limit UDP/69. Use tftp-max-blocksize to cap resources. | | Firmware poisoning | Serve signed firmware images; validate hash on client. |
A is a software application or embedded system service that listens for incoming file transfer requests using the Trivial File Transfer Protocol (TFTP). Unlike its more famous cousin, FTP (File Transfer Protocol), TFTP is designed to be minimal.
Low-RAM microcontroller boards (e.g., ancient ARM9, MIPS routers) use TFTP to load FPGA bitstreams or application code bootloaders.
