Skip to content

Conversation

guusdk
Copy link
Member

@guusdk guusdk commented Oct 14, 2025

In server-to-server configuration on the admin console, there’s a checkbox that controls if any other authentication mechanism can be used, if SASL EXTERNAL was attempted, but failed.

The rationale being that if a strong mechanism fails, using a weaker mechanism can lead to exploitable security loopholes.

The current text for this option is:

If attempting to validate a cerificate fails, the connection is closed and not attempted via dialback authentication

This is confusing. Improve it, for example by using:

Treat invalid TLS certificates as fatal (do not attempt other, possibly weaker, forms methods of authentication)

In server-to-server configuration on the admin console, there’s a checkbox that controls if any other authentication mechanism can be used, if SASL EXTERNAL was attempted, but failed.

The rationale being that if a strong mechanism fails, using a weaker mechanism can lead to exploitable security loopholes.

The current text for this option is:

> If attempting to validate a cerificate fails, the connection is closed and not attempted via dialback authentication

This is confusing. Improve it, for example by using:

> Treat invalid TLS certificates as fatal (do not attempt other, possibly weaker, forms methods of authentication)
@guusdk guusdk added the backport 5.0 on merge, GHA will generate a PR with these changes against 5.0 branch label Oct 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport 5.0 on merge, GHA will generate a PR with these changes against 5.0 branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant