Repository navigation
fix(engine,session): require EncryptMethod (98) = 0 on the Logon acknowledgement - #196
Merged
Merged
Conversation
joaquinbejar
commented
Oct 20, 2026
joaquinbejar
left a comment
Owner
Author
There was a problem hiding this comment.
APPROVE. The required EncryptMethod check resolves the remaining finding from PR188 and PR192. The 17 independent engine handshakes, three protocol probes, 275 session tests, seven peer tests, interop and formatting checks pass. No new findings. Submitted as COMMENT because GitHub prevents the author account from approving its own pull request.
Codecov Report❌ Patch coverage is
... and 1 file with indirect coverage changes 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Codex's remaining P2 from #188/#192.
EncryptMethod(98) is a required field of the Logon (FIX44.xml,doc/fix_operations.md), but neither the engine's initiator nor the #93 poll driver checked it on the acknowledgement: an ack without 98 established the session.Changes
ironfix_session::header::check_encrypt_methodandEncryptMethodProblem: 98 must be present and0. It reportsSessionRejectReason1 (absent) or 5 (another method) withRefTagID98, in the existing text.EngineError::LogonRejected, as it does for a bad 108.doc/fix_operations.md, initiator step 6, documents it.Behaviour change
An initiator now refuses a Logon acknowledgement without 98, or with a 98 other than 0. A conforming counterparty always sends
98=0.Testing
initiator_tests::test_ack_encrypt_method_missing_or_unsupported_fails_handshakecovers both an absent 98 and 98=1.poll_driver_peer::test_ack_without_encrypt_method_is_rejected_and_ends_the_sessioncovers the poll driver.cargo test --workspace --all-features: 2647 passed, 0 failed. fmt, clippy -D warnings, doc and check-spanish are clean.Refs #93