Merge dev/v0.0.2 into master for release v0.0.2

Author: g3noce

.gitignore

@@ -1,2 +1,28 @@
-/target
-/secure_volume
+# Generated by Cargo
+# will have compiled files and executables
+debug/
+target/
+
+# Remove Cargo.lock from gitignore if creating an executable, leave it for libraries
+# More information here https://doc.rust-lang.org/cargo/guide/cargo-toml-vs-cargo-lock.html
+# Cargo.lock
+
+# These are backup files generated by rustfmt
+**/*.rs.bk
+
+# MSVC Windows builds of rustc generate these, which store debugging information
+*.pdb
+
+# DSPV Specific
+secure_volume/
+dspv.meta
+*.enc
+
+# OS generated files
+.DS_Store
+.DS_Store?
+._*
+.Spotlight-V100
+.Trashes
+ehthumbs.db
+Thumbs.db

CONTRIBUTING.md

@@ -0,0 +1,28 @@
+# Contributing to DSPV
+
+First off, thank you for considering contributing to the Dynamic Secure Portable Volume! We welcome contributions from everyone.
+
+## How Can I Contribute?
+
+### Reporting Bugs
+* Ensure the bug was not already reported by searching on GitHub under Issues.
+* If you're unable to find an open issue addressing the problem, open a new one. Be sure to include a title and clear description, as much relevant information as possible, and a code sample or an executable test case demonstrating the expected behavior that is not occurring.
+
+### Suggesting Enhancements
+* Open a new issue with a detailed description of the proposed feature.
+* Explain *why* this enhancement would be useful to most users.
+
+### Submitting Pull Requests
+1. **Fork the repository** and create your branch from `main`.
+2. **Clone** your fork locally.
+3. **Branch** out: `git checkout -b my-feature-branch`.
+4. **Develop** your feature or fix.
+5. **Test** your code: Ensure all existing tests pass (`cargo test`) and write new tests for your specific additions, especially if they touch cryptography (`mod crypto`) or file I/O (`mod storage`).
+6. **Lint** your code: Run `cargo fmt` and `cargo clippy` to ensure your code matches the project's style guidelines.
+7. **Commit** your changes with clear, descriptive commit messages.
+8. **Push** to your fork and **submit a pull request** to the `main` branch.
+
+## Code Standards
+* **Security First:** Any changes to the cryptographic implementation must be thoroughly documented and backed by tests verifying boundary conditions (e.g., bit-flipping attacks, extreme offsets).
+* **Error Handling:** Use the custom structured Enums (e.g., `VaultError`, `ChunkIoError`) instead of generic IO errors to maintain clear logging and predictable failure states.
+* **Memory Safety:** If you introduce new structures holding sensitive data (keys, plain-text buffers), ensure they implement the `Zeroize` and `ZeroizeOnDrop` traits.

Cargo.lock

@@ -25,3 +25,4 @@ dashmap = "6.1.0"
 # --- Utilitaires OS ---
 fs4 = "0.13.1"
 rpassword = "7.4.0"
+clap = { version = "4.5", features = ["derive"] }

Cargo.toml

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 [Votre Nom ou Pseudo GitHub]
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

LICENSE

@@ -0,0 +1,67 @@
+# 🔐 Dynamic Secure Portable Volume (DSPV)
+
+[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
+[![Rust](https://img.shields.io/badge/Rust-1.70%2B-orange)](https://www.rust-lang.org/)
+[![GitHub release](https://img.shields.io/github/v/release/g3noce/Dynamic-Secure-Portable-Volume)](https://github.com/g3noce/Dynamic-Secure-Portable-Volume/releases)
+
+> A portable, cross-platform encrypted container that creates a secure workspace on any USB drive or local folder without leaving traces on the host machine.
+
+## ✨ Overview
+
+DSPV transforms any standard folder into an **encrypted vault**. By placing the executable in a directory or USB drive, all files placed inside the designated secure folder are encrypted on disk. 
+
+Access is provided transparently via a local WebDAV server. You interact with your files through your OS's native file explorer, and DSPV handles the encryption and decryption on the fly in memory.
+
+## 🛡️ Core Features
+
+* **True Portability:** Single standalone executable. No drivers or administrative privileges required on the host machine.
+* **On-the-Fly Cryptography:** Uses **AES-256-XTS** for robust disk encryption, identical to standards used by VeraCrypt and BitLocker.
+* **Strong Key Derivation:** Master keys are derived using **Argon2id** with a random 32-byte salt to thwart brute-force attacks.
+* **Secure Memory Management:** Cryptographic keys and plain-text buffers are managed with strict `Zeroize` traits, ensuring sensitive data is securely wiped from RAM immediately after use.
+* **Chunk-Based I/O:** Files are not fully loaded into RAM. Read/Write operations are streamed and encrypted in chunks, allowing for the manipulation of massive files with minimal memory footprint.
+
+## 🚀 Usage Workflow
+
+### 1. Initialization
+1. Copy the `dspv` executable to the root of your USB drive or desired folder.
+2. Launch the executable.
+3. You will be prompted to enter a **volume encryption key**.
+4. A folder named `secure_volume` (or a custom name) is automatically created and locked with a `dspv.meta` file.
+
+### 2. Accessing Files
+Once unlocked, DSPV hosts a local WebDAV server acting as a gateway.
+
+* **Windows:** A network drive window opens automatically. Drag, drop, and edit files directly.
+* **Linux / macOS:** The server starts at `http://127.0.0.1:8080`.
+  * **Linux:** Mount using `davfs2` or your file manager's "Connect to Server" feature (`dav://127.0.0.1:8080`).
+  * **macOS:** Open Finder → Go → Connect to Server → `http://localhost:8080`.
+
+*Note: Automatic native mounting for Linux and macOS is currently being refined.*
+
+### 3. Closing the Vault
+Simply press `CTRL+C` in the terminal running DSPV. The server will gracefully shut down, flush all pending operations to disk, and purge the RAM.
+
+## 🛠️ Building from Source
+
+### Prerequisites
+* [Rust and Cargo](https://www.rust-lang.org/tools/install) (1.70+)
+
+### Compilation
+```bash
+git clone [https://github.com/g3noce/Dynamic-Secure-Portable-Volume.git](https://github.com/g3noce/Dynamic-Secure-Portable-Volume.git)
+cd Dynamic-Secure-Portable-Volume
+cargo build --release
+```
+The compiled binary will be located at `target/release/dspv`.
+
+### Running Tests
+The project includes an extensive suite of critical resilience and cryptographic tests.
+```bash
+cargo test
+```
+
+---
+
+> [!WARNING]
+> **Disclaimer**
+> This software is provided "as is". While it implements strong cryptographic primitives, the security of your data ultimately depends on the strength of your password and the physical security of the host machine (which could be compromised by keyloggers or malware). Always keep backups of your encrypted vaults.