technote:security_linux
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| technote:security_linux [2025/10/03 02:35] – created Scott Cunliffe | technote:security_linux [2025/10/03 03:00] (current) – [TapeTrack Server: Anti-Throttle and Anti-Hacking Measures] Scott Cunliffe | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== | + | ====== Server: Anti-Throttle and Anti-Hacking ====== |
| ===== Protocol Overview ===== | ===== Protocol Overview ===== | ||
| - | TapeTrack uses a **compressed and encrypted binary protocol** to communicate between clients and servers. | + | TapeTrack uses a compressed and encrypted binary protocol to communicate between clients and servers. |
| - | When a TapeTrack Server is exposed to the internet, it is common for **unauthorized connection attempts** to occur. These are typically | + | When a TapeTrack Server is exposed to the internet, it is common for unauthorized connection attempts to occur. These are typically automated scans from hackers who are unaware they’re targeting a TapeTrack service. For example, a server running on port 5000 may be mistaken for: |
| - | * A **UPnP service** | + | * A UPnP service |
| - | * An **SSL server** on a non-standard port | + | * An SSL server on a non-standard port |
| - | Although unauthorized access is extremely difficult due to TapeTrack’s protocol and encryption, | + | Although unauthorized access is extremely difficult due to TapeTrack’s protocol and encryption, repeated connection attempts can consume server resources. |
| ===== Connection Handling Strategy ===== | ===== Connection Handling Strategy ===== | ||
| TapeTrack implements a lightweight defense mechanism to reduce impact from non-compliant clients: | TapeTrack implements a lightweight defense mechanism to reduce impact from non-compliant clients: | ||
| - | | + | |
| - | | + | |
| - | | + | |
| - | **Summary**: | + | Once an IP address (or gateway) sends a non-TapeTrack packet, all future connections from that IP during the time-out period will be accepted but terminated immediately. |
| ===== Advanced Linux Integration: | ===== Advanced Linux Integration: | ||
| - | On Linux systems, TapeTrack can integrate with **eBPF** for kernel-level IP blocking. | + | On Linux systems, TapeTrack can integrate with eBPF for kernel-level IP blocking. |
| To enable this: | To enable this: | ||
| * Start the server with the `-B` argument and a pointer to a preloaded eBPF table. | * Start the server with the `-B` argument and a pointer to a preloaded eBPF table. | ||
| - | * TapeTrack will dynamically | + | * TapeTrack will dynamically add/remove IPs from the table during the time-out period. |
| - | * If enabled, connections from banned IPs will be **blocked at the kernel level**, preventing any interaction with the TapeTrack Server. | + | * If enabled, connections from banned IPs will be blocked at the kernel level, preventing any interaction with the TapeTrack Server. |
| ===== Further Reading ===== | ===== Further Reading ===== | ||
| - | For setup instructions and eBPF integration steps, refer to the [[technote: | + | For setup instructions and eBPF integration steps, refer to the [[technote: |
| - | {{tag>tapetrack | + | {{tag> |
technote/security_linux.1759458910.txt.gz · Last modified: 2025/10/03 02:35 by Scott Cunliffe
