Skip to content

Conversation

@adamwight
Copy link

These functions are necessary when the connection is encrypted.

FIXME:

  • Test fails with an invalid mutex, maybe the state is not parsed from arguments?
  • This is the only function which attempts to read either client or server state from arguments, probably not a good thing.
  • Need to be more careful with cleanup and error conditions.

Adam Wight and others added 2 commits December 1, 2025 11:58
I believe the cyrus default secprops come from a zeroed block of
memory, which importantly means that `max_ssf` = 0 so encryption is
actually disallowed by the client and server started by sasl_auth.

In the long term, it's better if the security parameters come from the
application but this patch sets up a reasonable and permissive default
which should be no worse than the previous situation of preventing
encryption altogether.

Note that encryption will also require wiring the sasl_encode and
sasl_decode interface functions.
These functions are necessary to communication when the connection is
encrypted.

TODO:
- This is the only function which attempts to read either client or
  server state from arguments, probably not a good thing.
- Need to be more careful with cleanup and error conditions.
@adamwight adamwight marked this pull request as ready for review December 1, 2025 11:08
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.

1 participant