Skip to content

Add info about TLS cipher suites and 1.3 key exchanges #999

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
pawelulewicz-da wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Add info about TLS cipher suites and 1.3 key exchanges #999

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 14 additions & 1 deletion docs-main/global-synchronizer/reference/configuration-reference.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -177,12 +177,25 @@ canton.participants.participant.ledger-api.tls.client-auth {
}
```

All private keys must be in PKCS#8 PEM format. You can also restrict the minimum TLS version and allowed cipher suites:
All private keys must be in PKCS#8 PEM format. You can also restrict the minimum TLS version:

```
canton.participants.participant.ledger-api.tls.minimum-server-protocol-version = TLSv1.3
```

and allowed cipher suites:

```
canton.participants.participant.ledger-api.tls.ciphers =
[
"TLS_AES_256_GCM_SHA384",
"TLS_AES_128_GCM_SHA256",
"TLS_CHACHA20_POLY1305_SHA256"
]
```

For 1.3 suites, customize the supported key exchanges using the Java `jdk.tls.namedGroups` property.

@thibault-da thibault-da Jul 7, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did we at least manually check that this indeed works? You can leave it as is here but can you also create an issue in the Canton repo (labeled with team-canton-security) to check that this gets applied as expected? I'm not 100% sure how this get threaded through from JDK properties to netty shaded / boringssl etc...

@pawelulewicz-da pawelulewicz-da Jul 7, 2026

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not really, I just checked the docs: https://docs.oracle.com/en/java/javase/11/security/java-secure-socket-extension-jsse-reference-guide.html

I expected to verify that in the review.

@pawelulewicz-da pawelulewicz-da Jul 7, 2026

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll postpone this PR then, as we probably shouldn't publish it if we're not sure.


## Traffic configuration

Your validator automatically purchases traffic (sequencer throughput) using Canton Coin. Configure the top-up behavior in `standalone-validator-values.yaml`:
Expand Down