mirror of
https://github.com/hanzoai/s3.git
synced 2026-10-30 14:59:09 +00:00
zooqueen
dd74d3e6d6
hanzoai/s3 was an AGPL-3.0 MinIO fork whose network-copyleft blocks embedding
and reselling as a managed service. Replace it wholesale with a fork of
SeaweedFS (github.com/seaweedfs/seaweedfs, Apache-2.0, Go) which ships a
built-in S3 gateway + Filer.
- License: AGPL-3.0 -> Apache-2.0 (upstream LICENSE kept verbatim, incl.
"Copyright 2025 Chris Lu"); NOTICE added crediting SeaweedFS. No AGPL/BUSL/
SSPL/GPL or enterprise ("ee") files remain.
- Module: go.mod path set to github.com/hanzoai/s3 with a self-replace
(replace github.com/seaweedfs/seaweedfs => ./) so the ~1800 internal Go files
keep their upstream import paths with zero churn. Internal identifiers and
import paths are intentionally NOT renamed.
- CLI rebrand: the binary is built as `s3` (was `weed`); root usage, per-command
help/usage/flag strings, shell autocomplete program name, and the product name
in CLI output now read "Hanzo S3" / `s3`. Users never see `weed`.
(e.g. `s3 server`, `s3 filer`, `s3 master`, `s3 volume`, `s3 s3`, `s3 mount`.)
- Build: `make` (or `go build -o s3 ./weed`) builds the `s3` binary green;
`cmd/weed-db` and `cmd/weed-sql` also build; `go vet ./weed/command/` clean.
- README/LLM.md rewritten for Hanzo S3; AGENTS.md/CLAUDE.md symlinks preserved.
- Dropped a 33MB prebuilt Mach-O `stress` binary upstream had committed; `.gitignore`
updated to ignore the `s3` build output.
56 lines
1.9 KiB
Go
56 lines
1.9 KiB
Go
package repl_util
|
|
|
|
import (
|
|
"sync"
|
|
|
|
"github.com/seaweedfs/seaweedfs/weed/glog"
|
|
"github.com/seaweedfs/seaweedfs/weed/kms"
|
|
"github.com/seaweedfs/seaweedfs/weed/pb/filer_pb"
|
|
"github.com/seaweedfs/seaweedfs/weed/s3api"
|
|
"github.com/seaweedfs/seaweedfs/weed/util"
|
|
)
|
|
|
|
var (
|
|
sseInitMu sync.Mutex
|
|
sseInitialized bool
|
|
)
|
|
|
|
// InitializeSSEForReplication sets up SSE-S3 and SSE-KMS decryption so that
|
|
// replication sinks can transparently decrypt encrypted objects.
|
|
// SSE-S3 is initialized from the filer (KEK stored on filer).
|
|
// SSE-KMS is initialized from Viper config (security.toml [kms] section or
|
|
// WEED_KMS_* environment variables).
|
|
// SSE-C cannot be decrypted (customer key not available) and will error at
|
|
// decryption time.
|
|
//
|
|
// Safe to call multiple times; only the first successful initialization takes
|
|
// effect. Failed attempts do not prevent future retries.
|
|
func InitializeSSEForReplication(filerSource filer_pb.FilerClient) error {
|
|
sseInitMu.Lock()
|
|
defer sseInitMu.Unlock()
|
|
if sseInitialized {
|
|
return nil
|
|
}
|
|
|
|
// Initialize SSE-S3 key manager from filer
|
|
if err := s3api.GetSSES3KeyManager().InitializeWithFiler(filerSource); err != nil {
|
|
return err
|
|
}
|
|
|
|
// Attempt KMS initialization from Viper config.
|
|
// KMS configuration is typically in the S3 config file which the
|
|
// replication commands don't load directly. Support loading from
|
|
// security.toml [kms] section or WEED_KMS_* environment variables.
|
|
loader := kms.NewConfigLoader(util.GetViper())
|
|
if err := loader.LoadConfigurations(); err != nil {
|
|
glog.Warningf("KMS initialization from config failed: %v (SSE-KMS decryption will not be available)", err)
|
|
} else if err := loader.ValidateConfiguration(); err != nil {
|
|
glog.Warningf("KMS configuration validation failed: %v (SSE-KMS decryption will not be available)", err)
|
|
} else {
|
|
glog.V(0).Infof("KMS initialized for replication")
|
|
}
|
|
|
|
sseInitialized = true
|
|
return nil
|
|
}
|