mirror of https://github.com/NVIDIA/OpenShell.git synced 2026-10-12 04:39:51 +08:00

Files

T

History

JoffrefandClaude Opus 5.5 1134d60602 fix(core): classify NAT64 addresses by the longest matching prefix

embedded_ipv4 returned the first registered prefix that contained the
address. With a configured 2001:db8::/32 and a later-discovered
2001:db8:8c52:7003::/96, 2001:db8:8c52:7003::7f00:1 was read through the
/32 as 140.82.112.3 and passed the SSRF checks, while the /96 route
translates it to 127.0.0.1.

Pick the longest matching prefix, the well-known prefix included, the
same way the route that carries the packet does. The tests register the
broad prefix first and check loopback, metadata and private destinations
under the nested one. They use RFC 9637 documentation space because the
registry is process-wide and a 2001:db8::/32 would change how other
tests classify their 2001:db8 addresses.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Joffref <mjoffre@blaxel.ai>

2026-09-27 21:32:21 -07:00

src

fix(core): classify NAT64 addresses by the longest matching prefix

2026-09-27 21:32:21 -07:00

build_version.rs

fix(tui): replace alpha badges with version (#3114 )

2026-09-02 15:13:25 +00:00

build.rs

fix(tui): replace alpha badges with version (#3114 )

2026-09-02 15:13:25 +00:00

Cargo.toml

feat(policy): establish one canonical authored policy representation (#3334 )

2026-09-16 17:36:31 +00:00

README.md

feat(supervisor-middleware): add network egress middleware (#2027 )

2026-07-16 17:47:49 -07:00

README.md

openshell-core

Shared types, constants, configuration, and helpers used across OpenShell crates.

Object Metadata

Top-level user-facing objects use a Kubernetes-style metadata convention. The metadata shape provides:

Stable server-generated ID.
Human-readable name.
Creation timestamp.
Optional labels for filtering and automation.

Code that works with object metadata should use the traits in openshell_core::metadata instead of reaching into protobuf fields directly:

use openshell_core::{ObjectId, ObjectLabels, ObjectName};

let id = sandbox.object_id();
let name = sandbox.object_name();
let labels = sandbox.object_labels();

Trait methods must tolerate missing metadata and return safe empty values rather than panicking.

Label Rules

Labels follow Kubernetes-style key and value conventions:

Keys may include an optional DNS-prefix followed by /.
Names are limited to alphanumeric characters plus -, _, and ..
Values use the same character set and may be empty.
Selectors use comma-separated key=value pairs with AND semantics.

Validate labels at API ingress before persisting objects.

Inference Profiles

Provider inference profiles live in this crate so the gateway, sandbox, and router agree on provider defaults. Profiles define:

Auth header style.
Default upstream headers.
Client-supplied passthrough headers.
Supported inference protocol shapes.

Do not duplicate provider-specific inference behavior in callers. Add shared behavior here, then consume it from the gateway, sandbox, and router.

Middleware Contracts

Built-in supervisor middleware identifiers, host-selector matching, and pure configuration validation live in openshell_core::middleware. Policy admission and the supervisor runtime consume the same contract without introducing a dependency from the policy crate to the supervisor implementation.

Protobuf Struct Conversion

Use openshell_core::proto_struct when crossing between serde_json values and prost_types::{Struct, Value}. Both conversion directions live in this module; JSON-to-protobuf conversion is fallible so callers cannot silently replace an unrepresentable number.