Skip to content

Bump libssh to master 2025-11-17#90362

Merged
rschu1ze merged 5 commits intoClickHouse:masterfrom
Revertionist:libssh-forward-to-master
Nov 20, 2025
Merged

Bump libssh to master 2025-11-17#90362
rschu1ze merged 5 commits intoClickHouse:masterfrom
Revertionist:libssh-forward-to-master

Conversation

@Revertionist
Copy link
Copy Markdown
Contributor

@Revertionist Revertionist commented Nov 19, 2025

Changelog category (leave one):

  • Build/Testing/Packaging Improvement

Changelog entry (a user-readable short description of the changes that goes into CHANGELOG.md):

Bump libssh from 0.9.8 to master (0.11.3). This resolves CVE-2025-5318.

Details

Addresses CVE GHSA-98qw-prqm-9f4p

libssh master (libssh-0.12) contains 2 PKI signing functions that were until now manually implemented in ClickHouse's fork (see here). Instead of continuing to manage these custom patches, this PR uses the native signing functionality available in libssh (we need to bump to the development version of libssh for that). Reference: #89801 (comment)

@rschu1ze rschu1ze self-assigned this Nov 19, 2025
Comment thread src/Server/SSH/SSHPtyHandlerFactory.h
Comment thread src/Common/SSHWrapper.cpp Outdated
rschu1ze

This comment was marked as resolved.

@rschu1ze rschu1ze changed the title forward libssh to master 17-11-2025 Bump libssh to master 2025-11-17 Nov 19, 2025
@rschu1ze rschu1ze added the can be tested Allows running workflows for external contributors label Nov 19, 2025
@clickhouse-gh
Copy link
Copy Markdown
Contributor

clickhouse-gh Bot commented Nov 19, 2025

Workflow [PR], commit [9cf872c]

@clickhouse-gh clickhouse-gh Bot added pr-build Pull request with build/testing/packaging improvement submodule changed At least one submodule changed in this PR. labels Nov 19, 2025
@rschu1ze
Copy link
Copy Markdown
Member

@Revertionist Some build + tests were destroyed. Do you like to check?

@Revertionist
Copy link
Copy Markdown
Contributor Author

I will check, could you give me a brief idea on what these tests are?

Before raising the PR I just tried building on a linux VM

@Revertionist
Copy link
Copy Markdown
Contributor Author

@rschu1ze Two required checks are failing but these seem unrelated to the libssh upgrade I made. Am I allowed to make changes to the ClickHouse/tests folder?

@rschu1ze
Copy link
Copy Markdown
Member

There is a weird build error, I merged from master once more.

@rschu1ze
Copy link
Copy Markdown
Member

Am I allowed to make changes to the ClickHouse/tests folder?

Yes, but it is not needed to change anything in this directory.

@rschu1ze
Copy link
Copy Markdown
Member

I think we are good (test and build failures are unrelated). Merging.

@rschu1ze rschu1ze enabled auto-merge November 20, 2025 14:00
@rschu1ze rschu1ze added this pull request to the merge queue Nov 20, 2025
@rschu1ze rschu1ze added the pr-must-backport Pull request should be backported intentionally. Use this label with great care! label Nov 20, 2025
Merged via the queue into ClickHouse:master with commit 238a3e1 Nov 20, 2025
12 of 14 checks passed
@robot-ch-test-poll robot-ch-test-poll added the pr-synced-to-cloud The PR is synced to the cloud repo label Nov 20, 2025
@robot-clickhouse-ci-2 robot-clickhouse-ci-2 added the pr-must-backport-synced The `*-must-backport` labels are synced into the cloud Sync PR label Nov 20, 2025
@robot-ch-test-poll1 robot-ch-test-poll1 added the pr-backports-created Backport PRs are successfully created, it won't be processed by CI script anymore label Nov 20, 2025
rschu1ze pushed a commit that referenced this pull request Nov 25, 2025
This is an amalgamation of
- #90362 and
- #90612

The first PR bumps libssh from 0.9.8 to dev (future 0.12). This fixes
CVE-2025-5318.

The second PR resolves a TSAN failure (*) that the first PR introduced.

(*) #90663
@rschu1ze rschu1ze mentioned this pull request Nov 25, 2025
rschu1ze pushed a commit that referenced this pull request Nov 25, 2025
This is an amalgamation of
- #90362 and
- #90612

The first PR bumps libssh from 0.9.8 to dev (future 0.12). This fixes
CVE-2025-5318.

The second PR resolves a TSAN failure (*) that the first PR introduced.

(*) #90663
@rschu1ze rschu1ze mentioned this pull request Nov 25, 2025
rschu1ze pushed a commit that referenced this pull request Nov 25, 2025
This is an amalgamation of
- #90362 and
- #90612

The first PR bumps libssh from 0.9.8 to dev (future 0.12). This fixes
CVE-2025-5318.

The second PR resolves a TSAN failure (*) that the first PR introduced.

(*) #90663
@rschu1ze rschu1ze mentioned this pull request Nov 25, 2025
rschu1ze pushed a commit that referenced this pull request Nov 25, 2025
This is an amalgamation of
- #90362 and
- #90612

The first PR bumps libssh from 0.9.8 to dev (future 0.12). This fixes
CVE-2025-5318.

The second PR resolves a TSAN failure (*) that the first PR introduced.

(*) #90663
@rschu1ze rschu1ze mentioned this pull request Nov 25, 2025
rschu1ze pushed a commit that referenced this pull request Nov 25, 2025
This is an amalgamation of
- #90362 and
- #90612

The first PR bumps libssh from 0.9.8 to dev (future 0.12). This fixes
CVE-2025-5318.

The second PR resolves a TSAN failure (*) that the first PR introduced.

(*) #90663
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

can be tested Allows running workflows for external contributors pr-backports-created Backport PRs are successfully created, it won't be processed by CI script anymore pr-build Pull request with build/testing/packaging improvement pr-must-backport Pull request should be backported intentionally. Use this label with great care! pr-must-backport-synced The `*-must-backport` labels are synced into the cloud Sync PR pr-synced-to-cloud The PR is synced to the cloud repo submodule changed At least one submodule changed in this PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants