glm-5.3-flash
1ccd5bbe0c
- params: the ADR-001/ADR-006 constants (`channels/socks5/sub`,
`alk/socks5`, `socks5:open`, `socks5:bind`), `socks5_open_spec()`
(Sub/External/channel-open marker; trivial empty-object input schema
with loud `additionalProperties: false`; reply
`{channel_id: integer, minimum 1}` required; `socks5:open` scope),
`Socks5Params {}` (deny_unknown_fields — empty stays valid forever),
the `establishment_reason` helper re-export.
- error: `SocksOpenError` (the ADR-049 §4 typed surface, shaped on
alktunnels' `TunnelOpenError`), the typed
`SocksEstablishmentReason` vocabulary (the five reason codes,
parse/as_str; unknown codes never aliased), `SocksOpenError::reason()`
as the typed view, and `SocksSessionError` (open vs in-stream `Rfc`
vs `Io` — a refused target is an RFC reply code through the session
type, consumer.md §Error surface). `SocksError`/`SocksServerError`/
`ReplyError` re-exported from the forked core.
- lib.rs re-exports the new public surface (convention 15).
- 9 new tests: spec shape, constants, serde round-trip +
unknown-field rejection, the reason mapping table, the
non-establishment classes (`FORBIDDEN`/`INVALID_INPUT`/
`too_many_channels`), future-reason non-aliasing, the three-plane
session surface.
- task `implementation/core-params-errors`: status → completed;
Notes + Summary filled.
Verification: cargo test (104 green), clippy --all-targets -D
warnings clean, fmt --check clean, doc --no-deps zero warnings,
both wasm checks (check + clippy on wasm32-unknown-unknown) clean.
41 lines
1.5 KiB
Rust
41 lines
1.5 KiB
Rust
//! alksocks — SOCKS5 (RFC 1928) as a produced resource on alkcall
|
|
//! channels.
|
|
//!
|
|
//! A producer/consumer protocol crate (the alktty/alktunnels shape):
|
|
//! the producer half registers the `channels/socks5/sub` open op and
|
|
//! drives the RFC 1928 conversation in-stream over the channel's
|
|
//! `BiStream`; the consumer half opens SOCKS5 channels and speaks the
|
|
//! protocol inside them. The defining posture: the protocol never
|
|
//! binds a port — kernel binds exist only as explicit, feature-gated
|
|
//! assembly shapes (`local`), never in the protocol layer.
|
|
//!
|
|
//! The RFC wire vocabulary and the explicit typestate live in
|
|
//! [`rfc1928`]: a targeted fork of fast-socks5 v1.0.0's `T`-generic
|
|
//! subset (MIT, third-party upstream) carrying two deliberate changes
|
|
//! (BIND support, `new_reply` publication) — see
|
|
//! `docs/architecture/rfc1928.md`, ADR-013, and ADR-011.
|
|
//!
|
|
//! Architecture: `docs/architecture/overview.md` (spec set:
|
|
//! wire.md, producer.md, consumer.md, rfc1928.md).
|
|
|
|
#![forbid(unsafe_code)]
|
|
|
|
pub mod rfc1928;
|
|
|
|
pub mod consumer;
|
|
pub mod egress;
|
|
pub mod error;
|
|
pub mod params;
|
|
pub mod producer;
|
|
pub mod wire;
|
|
|
|
pub use error::{
|
|
ReplyError, SocksError, SocksEstablishmentReason, SocksOpenError, SocksServerError,
|
|
SocksSessionError,
|
|
};
|
|
pub use params::{
|
|
establishment_reason, socks5_open_spec, Socks5Params, OP_SOCKS5_OPEN, SOCKS5_ALPN,
|
|
SOCKS5_BIND_SCOPE, SOCKS5_OPEN_SCOPE,
|
|
};
|
|
pub use wire::{addr_encoding_len, frame, DatagramReader, WireError, MAX_INNER_LEN};
|