Repository navigation
🚀 Release: Encrypted Block-Based Write Support & Stability Improvements
This release introduces a major overhaul of the write path, significantly improving correctness and stability when modifying encrypted files.
✨ Highlights
Block-aware encrypted writes
Writes are now handled using proper block iteration with read–decrypt–modify–encrypt–write semantics, ensuring data integrity even for unaligned offsets and partial writes.
Correct handling of CTR encryption offsets
The write implementation now correctly maps file offsets to cipher block ranges, fixing issues where written data was not persisted correctly.
Improved SETATTR support
File truncation, timestamp updates, and permission changes are now properly handled, enabling correct behavior for editors and tools that rely on temporary files and atomic replace patterns.
Better compatibility with common editors (e.g. GNOME, VS Code, nano)
Temporary file workflows using .goutputstream-* and similar patterns now work as expected.
Internal cleanup and logging improvements
Refactored code paths and clearer debug output to simplify future maintenance and debugging.
This filesystem prioritizes correctness and cryptographic safety.
Due to block-based encryption and FUSE overhead in Node.js, write performance is currently limited. Future releases may introduce caching and write coalescing to improve throughput.
🛠️ Breaking Changes
None.
If you want, I can also:
make it shorter / more marketing-style
add a TL;DR
tailor it for a pre-release / alpha warning
include benchmarks or known limitations
Just tell me 👍