Skip to content

Add support for configurable SSH algorithms in diego-sshd#4914

Open
philippthun wants to merge 1 commit intocloudfoundry:mainfrom
sap-contributions:sshd-config
Open

Add support for configurable SSH algorithms in diego-sshd#4914
philippthun wants to merge 1 commit intocloudfoundry:mainfrom
sap-contributions:sshd-config

Conversation

@philippthun
Copy link
Member

@philippthun philippthun commented Mar 6, 2026

Add configuration schema and implementation to allow operators to configure SSH algorithms (ciphers, host key algorithms, key exchanges, and MACs) for diego-sshd running in app containers.

The diego.sshd configuration accepts comma-separated strings for each algorithm type. When configured, these values are passed as command-line flags to diego-sshd (using -allowedCiphers, -allowedHostKeyAlgorithms, -allowedKeyExchanges, -allowedMACs). Empty strings result in no flags being passed, allowing diego-sshd to use its defaults.

Both the sshd section and individual algorithm options are optional in all schemas (api, worker, clock, and deployment_updater), allowing operators to configure only the algorithms they need to restrict.

  • I have reviewed the contributing guide

  • I have viewed, signed, and submitted the Contributor License Agreement

  • I have made this pull request to the main branch

  • I have run all the unit tests using bundle exec rake

  • I have run CF Acceptance Tests

Add configuration schema and implementation to allow operators to
configure SSH algorithms (ciphers, host key algorithms, key exchanges,
and MACs) for diego-sshd running in app containers.

The diego.sshd configuration accepts comma-separated strings for each
algorithm type. When configured, these values are passed as command-line
flags to diego-sshd (using -allowedCiphers, -allowedHostKeyAlgorithms,
-allowedKeyExchanges, -allowedMACs). Empty strings result in no flags
being passed, allowing diego-sshd to use its defaults.

Both the sshd section and individual algorithm options are optional in
all schemas (api, worker, clock, and deployment_updater), allowing
operators to configure only the algorithms they need to restrict.
@philippthun philippthun marked this pull request as ready for review March 9, 2026 08:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant