Run manually for releases

Build: #2 was successful Manual run by daryl herzmann

Build result summary

Details

Completed
Queue duration
2 seconds
Duration
2 minutes
Labels
None
Agent
Default Agent
Revision
26875ddee2ec4135e0fe23b6201629d30aa5d37e
Total tests
333

Tests

Code commits

Author Commit Message Commit date
Guus der Kinderen Guus der Kinderen 26875ddee2ec4135e0fe23b6201629d30aa5d37e Add additional debug logging.
Guus der Kinderen Guus der Kinderen b7aab55f4b2760a2317c1014ed1d2c0762037b69 OF-1849: Allow StartTLS on DirectTLS port
When DNS SRV records are misconfigured, connections that are expected to receive DirectTLS data could receive non-encrypted data (optionally to be encrypted with StartTLS later).

This commit adds a new configuration option 'xmpp.server.tls.on-plain-detection-allow-nondirecttls-fallback' (default: true) that can be used to toggle this behavior.
Guus der Kinderen Guus der Kinderen 7c63408f78c089679a9424f294e54a7f26befbdb OF-793: Add comment to clarify code structure.
Guus der Kinderen Guus der Kinderen 0e41d3ea29f6bcd1c98b838d40fd55b9e1a60d8d OF-793: Write </stream:stream> on correct writer
This commit ensures that an end-stream tag, as written by outgoing s2s connections, is written on the proper writer. This change intends to prevent issues where plain-text '</stream:stream>' is written on socket that's supposed to be encrypted.
Guus der Kinderen Guus der Kinderen 91118086f76d43cb6484fa08696c92ac610b71d0 OF-793: Log data that triggers "Unsupported record version Unknown-" exception
With some frequency, Openfire logs exceptions with this message: "javax.net.ssl.SSLException: Unsupported record version Unknown-47.115". One source of this appears to be in S2S Dialback negotiation.

This appears to be caused by Openfire trying to parse plain-text data as TLS: the decimal representation 47 115 equals to the characters '/' and 's'. A common place for these characters to occur in XMPP would be in stream close tags: </stream:stream>.

This commit allows the content of the buffer that's being parsed by the TLS handler to be logged in its hexadecimal representation, when the exception occurs.

In a test environment, I've found this hex string to be logged by this: "3c2f73747265616d3a73747265616d3e". Converted to characters, this is: "</stream:stream>"

Jira issues

IssueDescriptionStatus
6 more issues…
Unknown Issue TypeOF-793Could not obtain issue details from Jira
Unknown Issue TypeOF-1017Could not obtain issue details from Jira
Unknown Issue TypeOF-1251Could not obtain issue details from Jira
Unknown Issue TypeOF-1433Could not obtain issue details from Jira
Unknown Issue TypeOF-1829Could not obtain issue details from Jira

Shared artifacts

Artifact File size
.rpm files 294 MB