Unix File Permission Supplicant Utility - A simple utility that indexes directories and records their Unix permission and ownership data.
Go to file
2025-01-13 18:15:10 -06:00
docs Basic implementation of automatic documentation using Sphinx 2024-12-15 11:50:34 -06:00
libufps A lot. Really basic and unmanaged (aside from the logic in libufps) functionality 2025-01-13 18:15:10 -06:00
tests Begin tracking ufpsutil 2024-12-15 11:52:31 -06:00
.gitignore Created createIndex method to create an index and started work on restore method. 2024-12-15 15:42:58 -06:00
create.py A lot. Really basic and unmanaged (aside from the logic in libufps) functionality 2025-01-13 18:15:10 -06:00
LICENSE Initial commit 2024-12-14 22:56:32 -06:00
README.md A lot. Really basic and unmanaged (aside from the logic in libufps) functionality 2025-01-13 18:15:10 -06:00
requirements-lib.txt Begin work on libufps 2024-12-15 11:49:51 -06:00
requirements.txt Begin tracking ufpsutil 2024-12-15 11:52:31 -06:00
restore.py A lot. Really basic and unmanaged (aside from the logic in libufps) functionality 2025-01-13 18:15:10 -06:00
setup.py Begin work on libufps 2024-12-15 11:49:51 -06:00
ufpsutil.py A lot. Really basic and unmanaged (aside from the logic in libufps) functionality 2025-01-13 18:15:10 -06:00

ufpsutil

Unix File Permission Supplicant Utility - A simple utility that indexes directories and records their Unix permission and ownership data.

Purpose

The purpose of this project is to recursively delve into subdirectories and record their Unix file permissions and ownership information.

Most offsite backup solutions (such as Backblaze) don't store file permissions or ownership information. This means that in the event that data needs to be restored from them, time will need to be taken in order to update permissions and owners, which adds additional downtime.

Naturally, enterprises have solutions to this, but self hosters may not. This project aims to remedy that.

The idea is to record all of this information to a text file, which is backed up off-site as a normal file. This file can then be read by the utility to restore permissions, thereby making the restored backup as close as possible to how it was before it crashed. If mounted to the same locations, this solves any permissions issues a self hoster could face getting back up and running after a catastrophe.

Status

  • Recurse a directory (index)
  • Store Unix file permissions and ownership data
  • Restore Unix file permissions and ownership data using index file as an input
  • Diff index file and restored backup and inform the user of file inconsistencies
    • Sort of. It only detects when a file doesn't exist.
  • Index file encryption with bcrypt