// the take
A single-file C console app from a university Programming Fundamentals course that simulates a multi-user file manager with login, roles, and an audit trail. It's for someone learning basic C and OS-adjacent concepts like access control and logging, not for anyone who actually needs to secure files.
Account lockout after 3 failed attempts is a sensible anti-bruteforce touch for a beginner project. Password masking correctly handles backspace, which a lot of conio.h tutorials get wrong. Audit logging with timestamps on every sensitive action (login, password change, user deletion) shows the author thought about traceability, not just happy-path CRUD.
The 'encryption' is a custom character-shifting scheme, not a real cipher — it's almost certainly trivially reversible and should never be described as encryption to anyone who might reuse this code. There's no real filesystem being managed: files are an in-memory struct array that gets dumped to users.txt/auditlog.txt, so 'file management' here means pretend files inside one process, not actual disk files. Windows-only via conio.h and system("cls") rules out any portability, and storing usernames plus weakly-obscured passwords in a flat text file with no hashing or salting is the kind of thing that would fail a real security review instantly. At 1 star and a single source file, this is unmaintained coursework rather than something anyone else is depending on.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →