Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Gssapi sequence fixes #1248

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

SimonWilkinson
Copy link
Member

A couple of fixes for issues with checking sequence ordering in GSSAPI

Simon Wilkinson added 2 commits June 17, 2024 10:30
Sequence errors are supplemental information in GSSAPI. This means
that they are not fatal, unless they are returned alongside a failure
error code. This change makes our behaviour the same as MIT's - sequence
errors are non-fatal, and return valid output information.
A typo in _gssapi_msg_order_check means that sequence numbers
received out of sequence are not correctly added to the internal
order array.
@jaltman
Copy link
Member

jaltman commented Jun 20, 2024

RFC2743 1.2.3: Per-Message Replay Detection and Sequencing describes the compliant behavior implemented by this pull request.

Copy link
Member

@jaltman jaltman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change looks good to me with the exception that there are several functions where *minor_status is left unset. As a result the caller will receive a non-GSS_S_COMPLETE with potentially random garbage for minor_status.

lib/gssapi/krb5/arcfour.c Show resolved Hide resolved
lib/gssapi/krb5/arcfour.c Show resolved Hide resolved
lib/gssapi/krb5/unwrap.c Show resolved Hide resolved
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants