ft_shield

The problem

A system service has to start on its own, survive the terminal that launched it being closed, accept network connections, and leave a usable trace of what it does, all while rejecting unauthorised clients.

What I built

• Daemonisation: detaching from the terminal and integrating with systemd for service startup and supervision.
• TCP server: network listening and handling of several simultaneous connections; the subject requires 3 clients, the architecture is not limited to that number.
• Password authentication before any interaction with the service.
• Process management: spawning and tracking processes launched by the service.
• Logging: events available through journalctl.

Skills demonstrated

Linux systems programming, daemon lifecycle, systemd, TCP sockets and concurrent connections, access control, logging and observability.