Skip to content

Document the post-quantum TLS compatibility setting #26629

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
dvdksn wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Document the post-quantum TLS compatibility setting #26629

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
17 changes: 17 additions & 0 deletions content/manuals/ai/sandboxes/configuration/settings.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -779,6 +779,23 @@ make an untrusted certificate authority trusted or resolve other certificate
errors. For an untrusted internal CA, see
[certificate troubleshooting](../troubleshooting.md#api-calls-fail-with-a-certificate-error).

#### tls.postQuantumKeyExchange {.wrap-anywhere}

{{< setting-metadata type="boolean" default="true" >}}

Set this to `false` if a firewall or TLS-inspecting proxy drops or stalls
Docker Sandboxes HTTPS connections because it can't handle post-quantum key
exchange:

```console
$ sbx settings set tls.postQuantumKeyExchange false
$ sbx daemon restart
```

This disables post-quantum key exchange for TLS connections made by the host
CLI and daemon. Changes apply on the next CLI invocation and require a daemon
restart. Set it back to `true` and restart the daemon to restore the default.

### Shared agent skills

Shared agent skills are experimental.
Expand Down
Loading