docs: canonical README opening + SECURITY.md (#2)
* docs: canonical README opening per Hanzo OSS taxonomy * docs: add canonical SECURITY.md
This commit is contained in:
@@ -1,5 +1,49 @@
|
||||
# vfs
|
||||
|
||||
Object-store abstraction with content-addressed, PQ-encrypted block storage. The storage backplane for HIP-0107 streaming replication.
|
||||
|
||||
[]()
|
||||
[]()
|
||||
|
||||
## Quick start
|
||||
|
||||
```bash
|
||||
make build
|
||||
./bin/vfs put /tmp/in.txt --backend "s3://my-bucket/vfs-prefix?region=us-east-1" \
|
||||
--age-recipient "$RECIPIENT" --age-key /tmp/vfs.key
|
||||
```
|
||||
|
||||
## What this is
|
||||
|
||||
`vfs` is a 4 KiB block-level virtual filesystem that hashes every block with blake3-256, encrypts every block with `luxfi/age` (X25519, optionally hybrid PQ via ML-KEM-768), and stores them on a pluggable backend (`file://`, `s3://`, `gcs://`, `azureblob://`). In-memory LRU for the hot tier, object store for the cold tier — every Hanzo Go service that needs unlimited write capacity uses `vfs` instead of pre-sizing a PVC. Already exposes `func Mount()` for HIP-0106 inclusion.
|
||||
|
||||
## Specs
|
||||
|
||||
Implements:
|
||||
- HIP-0107 Streaming Replication over VFS
|
||||
- HIP-0106 Unified Cloud Binary (vfs subsystem — already exposes `Mount()`)
|
||||
|
||||
Companion to [hanzoai/replicate](https://github.com/hanzoai/replicate): `replicate` streams SQLite WAL frames file-level; `vfs` does block-level for any file.
|
||||
|
||||
## Architecture
|
||||
|
||||
```
|
||||
write() -> vfs.PutBlock -> blake3-256 hash -> luxfi/age encrypt
|
||||
|
|
||||
blocks/<2-hex-shard>/<full-hash>.zap.age
|
||||
|
|
||||
file:// | s3:// | gcs:// | azureblob://
|
||||
|
|
||||
in-memory LRU (hot)
|
||||
|
|
||||
FUSE mount (lands in 0.2.0)
|
||||
```
|
||||
|
||||
|
||||
---
|
||||
|
||||
# vfs
|
||||
|
||||
S3-backed virtual block filesystem with PQ encryption — unlimited write storage for stateful services.
|
||||
|
||||
[](https://github.com/hanzoai/vfs/actions/workflows/build.yml)
|
||||
|
||||
+17
@@ -0,0 +1,17 @@
|
||||
# Security Policy
|
||||
|
||||
## Reporting a vulnerability
|
||||
|
||||
Email security@hanzo.ai with details. Encrypt with our PGP key (fingerprint TBD).
|
||||
|
||||
We respond within 48 hours. Critical issues receive same-day acknowledgment.
|
||||
|
||||
## Scope
|
||||
|
||||
This policy covers code in this repository. For the broader Hanzo platform threat model, see [hanzoai/HIPs](https://github.com/hanzoai/HIPs).
|
||||
|
||||
## Sandbox boundary
|
||||
|
||||
`vfs` encrypts every block client-side with `luxfi/age` (X25519, optionally hybrid PQ via ML-KEM-768) before any byte touches the configured backend, so the object store sees only ciphertext. Block integrity is enforced via blake3-256 content addressing — corruption or substitution by the backend is detected on read.
|
||||
|
||||
For runtime sandbox guarantees, see HIP-0105 (in-process extension runtimes).
|
||||
Reference in New Issue
Block a user