From 45df4d0d9b577fecee798d672695fe24ff57fb1b Mon Sep 17 00:00:00 2001 From: mo khan Date: Tue, 15 Jul 2025 16:37:08 -0600 Subject: feat: migrate from Cedar to SpiceDB authorization system This is a major architectural change that replaces the Cedar policy-based authorization system with SpiceDB's relation-based authorization. Key changes: - Migrate from Rust to Go implementation - Replace Cedar policies with SpiceDB schema and relationships - Switch from envoy `ext_authz` with Cedar to SpiceDB permission checks - Update build system and dependencies for Go ecosystem - Maintain Envoy integration for external authorization This change enables more flexible permission modeling through SpiceDB's Google Zanzibar inspired relation-based system, supporting complex hierarchical permissions that were difficult to express in Cedar. Breaking change: Existing Cedar policies and Rust-based configuration will no longer work and need to be migrated to SpiceDB schema. --- vendor/bytes/SECURITY.md | 9 --------- 1 file changed, 9 deletions(-) delete mode 100644 vendor/bytes/SECURITY.md (limited to 'vendor/bytes/SECURITY.md') diff --git a/vendor/bytes/SECURITY.md b/vendor/bytes/SECURITY.md deleted file mode 100644 index b74a831c..00000000 --- a/vendor/bytes/SECURITY.md +++ /dev/null @@ -1,9 +0,0 @@ -# Security Policy - -Bytes is part of the Tokio project and uses the same security policy as [Tokio][tokio-security]. - -## Report a security issue - -The process for reporting an issue is the same as for [Tokio][tokio-security]. This includes private reporting via security@tokio.rs. - -[tokio-security]: https://github.com/tokio-rs/tokio/security/policy -- cgit v1.2.3