# Native agent transport regressions These are local Linux tests, **not VM/MVP acceptance**. They use ephemeral PKI, strict server-name/CA verification and mandatory client certificates on loopback. No production endpoint, VM, enrollment, job approval or database is touched. The OpenSSL fixture must set a session-id context for client authentication. On this host (OpenSSL 1.1.1w), the isolated replay regression originally failed on reconnect with `ssl_get_prev_session`, code `336433429`, reason `session id context uninitialized`; the client received TLS `InternalError`. Disabling the session cache and tickets did not provide that context. The fix sets a fixture-specific session context and restores normal caching/tickets; it changes neither production TLS nor certificate verification. Handshake diagnostics print only SSL codes and static library/function/reason metadata. Locked versions: openssl 0.10.82 / openssl-sys 0.9.118; reqwest 0.12.28 uses rustls 0.23.46 with ring 0.17.14 (workspace disables reqwest default TLS). The replay test asserts missing response returns an error without a fabricated ACK, repeats the exact encoded batch/message ID, and retains one deduplicated application record. No execution retry is introduced. Rotation retains its three identity/crash/recovery tests. Its harness also runs the four HTTPS contract tests because it compiles and uses that same transport implementation; rotation-only fixtures live in the rotation test, without dead-code allowances. Reproduce locally (commands, not a VM acceptance recipe): ```sh OPENSSL_CONF=/dev/null cargo test -p rmm-agent --test https_channel --locked real_mtls_hello_poll_durable_replay_and_fencing -- --exact --nocapture cargo test -p rmm-agent --test https_channel --test certificate_rotation --locked cargo clippy -p rmm-agent --test https_channel --test certificate_rotation --locked -- -D warnings ``` `OPENSSL_CONF=/dev/null` isolates only the test process from host OpenSSL config; it does not disable TLS, trust, name verification or mandatory mTLS. ## Observed local verification (2026-11-12) - Isolated pre-fix replay: failed with the server reason/code above and client `received fatal alert: InternalError` on the second explicit send. - After the context fix: isolated pair of targets passed (7 + 4 tests). - Five additional consecutive native runs with the normal environment passed (7 + 4 each; 55 test executions, seven distinct cases because the HTTPS contract is deliberately included in the rotation harness). - Targeted `cargo clippy ... -- -D warnings` passed; file-scoped rustfmt check passed. No dead-code/lint suppression was added. - VM execution, production backend integration and production wiring were not performed by this dispatch; Linux-MVP acceptance remains outside this result.