VS-15: scaffold meshcentral-amt-redirect crate #54
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/amt-redirect-scaffold-vs-15"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Scaffolds the
meshcentral-amt-redirectcrate named in VS-15. VS-15 is an explicit deferred tracking placeholder: the Intel AMT redirection-protocol client (IDE-R / SOL / KVM / APF) cannot be implemented or smoke-tested end-to-end without a real AMT host or simulator, neither of which exists in the customer base yet. This PR lands the typed surface so the four AMT specialty routes and the upper AMT layers have something to wire onto incrementally, without pretending the protocols work.What this does
meshcentral-amt-redirect(added tomembersandworkspace.dependencies).sessionmodule: the sharedSTART_REDIRECTION_SESSION/AUTHENTICATE_SESSIONhandshake opcodes, aRedirectTarget(host, TLS-vs-plain port 16994/16993, AMT credentials), and anopen()stub.ider(drivesoneclickrecovery.ashx),sol(commander.ashx),kvm(ipkvm.ashx),apf(apf.ashx).RedirectErrorwith aNotYetImplemented(&'static str)variant; every entry point returns it. Per-feature wire framing is documented as TODO against the legacyamt-redir-*/apf.jsmodules.What this does NOT do
.ashxroutes are deliberately left at their existing 501 hints.Verification
cargo build -p meshcentral-amt-redirectandcargo clippy -p meshcentral-amt-redirect -- -D warningsboth clean in the dev container.🤖 Generated with Claude Code