|
1 | | -# Backend Component - Linux ACL Management Interface |
| 1 | +<div align="center"> |
2 | 2 |
|
3 | | -Securing Linux Storage with ACLs: An Open-Source Web Management Interface for Enhanced Data Protection. |
| 3 | +# Linux ACL Management Interface - Backend Component |
4 | 4 |
|
5 | | -Progress Docs: https://pythonhacker24.github.io/linux-acl-management/ |
| 5 | +<img width="600" hegith="600" src="https://github.com/user-attachments/assets/a1625f58-0cd8-4df9-babc-31547b18d55a"> |
6 | 6 |
|
7 | | -## Documentation |
| 7 | +A robust web-based management interface for Linux Access Control Lists (ACLs), designed to enhance data protection and simplify ACL administration. This project provides a modern, user-friendly solution for managing file system permissions in Linux environments. |
8 | 8 |
|
9 | | -To be written ... |
| 9 | +[](https://opensource.org/licenses/MIT) |
10 | 10 |
|
| 11 | +[View Documentation](https://pythonhacker24.github.io/linux-acl-management/) |
11 | 12 |
|
12 | | -## Progress Report |
| 13 | +</div> |
13 | 14 |
|
14 | | -To be written ... |
| 15 | +## Project Summary |
| 16 | + |
| 17 | +Institutional departments, such as the Biomedical Informatics (BMI) Department of Emory University School of Medicine, manage vast amounts of data, often reaching petabyte scales across multiple Linux-based storage servers. Researchers storing data in these systems need a streamlined way to modify ACLs to grant or revoke access for collaborators. Currently, the IT team at BMI is responsible for manually handling these ACL modifications, which is time-consuming, error-prone, and inefficient, especially as data volume and user demands grow. To address this challenge at BMI and similar institutions worldwide, a Web Management Interface is needed to allow users to modify ACLs securely. This solution would eliminate the burden on IT teams by enabling on-demand permission management while ensuring security and reliability. The proposed system will feature a robust and highly configurable backend, high-speed databases, orchestration daemons for file storage servers, and an intuitive frontend. The proposal includes an in-depth analysis of required components, high-level and low-level design considerations, technology selection, and the demonstration of a functional prototype as proof of concept. The goal is to deliver a production-ready, secure, scalable, and reliable system for managing ACLs across multiple servers hosting filesystems such as NFS, BeeGFS, and others. This solution will streamline access control management and prepare it for deployment at BMI and other institutions worldwide, significantly reducing the manual workload for IT teams. |
| 18 | + |
| 19 | +## Features |
| 20 | + |
| 21 | +- Intuitive web interface for ACL management |
| 22 | +- High-performance backend written in Go |
| 23 | +- Real-time ACL updates |
| 24 | +- Comprehensive ACL reporting and visualization |
| 25 | +- Integration with OpenLDAP for authentication |
| 26 | + |
| 27 | +## Quick Start |
| 28 | + |
| 29 | +### Prerequisites |
| 30 | + |
| 31 | +- Go 1.20 or higher |
| 32 | +- Docker (optional) |
| 33 | +- Redis |
| 34 | +- OpenLDAP server |
| 35 | + |
| 36 | +### Local Installation |
| 37 | + |
| 38 | +1. Clone the repository: |
| 39 | + ```bash |
| 40 | + git clone https://github.com/PythonHacker24/linux-acl-management.git |
| 41 | + cd linux-acl-management |
| 42 | + ``` |
| 43 | + |
| 44 | +2. Install dependencies: |
| 45 | + ```bash |
| 46 | + go mod download |
| 47 | + ``` |
| 48 | + |
| 49 | +3. Build the application: |
| 50 | + ```bash |
| 51 | + go build -o acl-manager |
| 52 | + ``` |
| 53 | + |
| 54 | +### Production Build |
| 55 | + |
| 56 | +For production build, it is recommended to use the Makefile. This allows you to build the complete binary on locally for security purposes. Since the project is in development mode, complete local build is not possible since dependencies are managed via GitHub and external vendors. Tarball based complete local builds will be developed in later stages. |
| 57 | + |
| 58 | +1. Clone the repository: |
| 59 | + ```bash |
| 60 | + git clone https://github.com/yourusername/linux-acl-management.git |
| 61 | + cd linux-acl-management |
| 62 | + ``` |
| 63 | + |
| 64 | +2. Use make: |
| 65 | + ```bash |
| 66 | + make build |
| 67 | + ``` |
| 68 | + |
| 69 | +3. Execute the binary |
| 70 | + ```bash |
| 71 | + ./bin/laclm --config config.yaml |
| 72 | + ``` |
| 73 | + |
| 74 | +### Docker Testbench Deployment |
| 75 | + |
| 76 | +A simulated environment has been developed on docker-compose for testing and experimenting purposes. It's not a production level build but a training ground for testing your config.yaml file for specific scenario. |
| 77 | +
|
| 78 | +```bash |
| 79 | +docker-compose up -d |
| 80 | +``` |
| 81 | +
|
| 82 | +A complete optional Docker based deployment option will be developed in later stages of development |
| 83 | +
|
| 84 | +## Usage |
| 85 | +
|
| 86 | +1. Configure your settings in `config.yaml` |
| 87 | +
|
| 88 | +2. Start the server: |
| 89 | + ```bash |
| 90 | + ./laclm --config <config.yaml> |
| 91 | + ``` |
| 92 | +
|
| 93 | +3. Access the api at `http://<ip-address>:<port>` |
| 94 | +
|
| 95 | +For detailed usage instructions, please refer to our [documentation](https://pythonhacker24.github.io/linux-acl-management/). |
| 96 | +
|
| 97 | +## Project Structure |
| 98 | +
|
| 99 | +``` |
| 100 | +. |
| 101 | +├── cmd/ # Application entry points |
| 102 | +├── internal/ # Private application code |
| 103 | +├── pkg/ # Public library code |
| 104 | +├── api/ # API definitions and handlers |
| 105 | +├── docs/ # Documentation |
| 106 | +└── deployments/ # Deployment configurations |
| 107 | +``` |
| 108 | +
|
| 109 | +## Development |
| 110 | +
|
| 111 | +### Branches |
| 112 | +
|
| 113 | +- `main`: Production-ready code |
| 114 | +- `development-v<version>`: Development branches for specific versions |
| 115 | +
|
| 116 | +### Contributing |
| 117 | +
|
| 118 | +1. Fork the repository |
| 119 | +2. Create your feature branch (`git checkout -b feature/amazing-feature`) |
| 120 | +3. Commit your changes (`git commit -m 'Add some amazing feature'`) |
| 121 | +4. Push to the branch (`git push origin feature/amazing-feature`) |
| 122 | +5. Open a Pull Request |
| 123 | +
|
| 124 | +Please read [CONTRIBUTING.md](CONTRIBUTING.md) for details on our code of conduct and development process. |
15 | 125 |
|
16 | 126 | ## About |
17 | 127 |
|
18 | | -- **Organization:** Department of Biomedical Informatics, Emory University |
19 | | -- **Program:** Google Summer of Code 2025 |
20 | | -- **Contributor:** Aditya Patil |
21 | | -- **Mentors:** Robert Tweedy, Mahmoud Zeydabadinezhad, PhD |
| 128 | +This project is developed as part of Google Summer of Code 2025, in collaboration with the Department of Biomedical Informatics at Emory University. |
22 | 129 |
|
23 | | -This project is part of Google Summer of Code 2025, undertaken with the Department of Biomedical Informatics at Emory University. |
| 130 | +### Team |
24 | 131 |
|
25 | | -## Technologies Used |
| 132 | +- **Contributor:** Aditya Patil |
| 133 | +- **Mentors:** |
| 134 | + - Robert Tweedy |
| 135 | + - Mahmoud Zeydabadinezhad, PhD |
| 136 | +
|
| 137 | +### Technologies |
26 | 138 |
|
27 | | -- **Programming Languages:** Golang |
28 | | -- **Frameworks/Libraries:** net/http |
29 | | -- **Standards/Protocols:** gRPC, REST |
30 | | -- **Tools:** Tarball, Redis, Docker, OpenLDAP |
| 139 | +- **Backend:** Golang, net/http |
| 140 | +- **API:** gRPC, REST |
| 141 | +- **Infrastructure:** Docker, Redis, OpenLDAP |
| 142 | +- **Packaging:** Tarball |
31 | 143 |
|
32 | 144 | ## License |
33 | 145 |
|
34 | | -This project is licensed under the MIT License - see the LICENSE file for details. |
| 146 | +This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details. |
| 147 | +
|
| 148 | +## Acknowledgments |
| 149 | +
|
| 150 | +- Department of Biomedical Informatics, Emory University |
| 151 | +- Google Summer of Code Program |
| 152 | +- Open Source Community |
0 commit comments