Skip to content
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

Backport of docs: Update 0.18.x release notes into stable-website #5388

Merged
merged 4 commits into from
Dec 20, 2024
Merged

Backport of docs: Update 0.18.x release notes into stable-website #5388

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
408bd72
backport of commit e097cda8698c3ac25168d50d4387314f19ca214e
Dan-Heath Dec 18, 2024
8e04635
backport of commit e9e84fe402364de51bc7e5cdc701133c9461cb76
Dan-Heath Dec 18, 2024
9f5730b
backport of commit dca6243028484ec410f6ca88b3ffceb4508f79b0
Dan-Heath Dec 19, 2024
2f75397
backport of commit 0e743571916ff3f352c437d5a9b590fc0cc19fce
Dan-Heath Dec 19, 2024
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
31 changes: 31 additions & 0 deletions website/content/docs/release-notes/v0_18_0.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,6 +41,18 @@ description: >-
Learn more:&nbsp; <a href="#known-issues-and-breaking-changes">Known issues and breaking changes </a>
</td>
</tr>

<tr>
<td style={{verticalAlign: 'middle'}}>
Go version 1.23 TLS handshake behavior changes
</td>
<td style={{verticalAlign: 'middle'}}>
Boundary version 0.18.x uses Go version 1.23, which introduced a new TLS handshake behavior. Some VPN providers struggle with the TLS handshake being sent over 2 frames instead of 1, which can lead to Boundary version 0.18.x controllers, workers, or clients being unable to establish connections. As a workaround, you can revert back to the previous TLS handshake behavior.
<br /><br />
Learn more:&nbsp; <a href="#known-issues-and-breaking-changes">Known issues and breaking changes </a>
</td>
</tr>

</tbody>
</table>

Expand Down Expand Up @@ -228,5 +240,24 @@ description: >-
</td>
</tr>

<tr>
<td style={{verticalAlign: 'middle'}}>
0.18.x
</td>
<td style={{verticalAlign: 'middle'}}>
Boundary version 0.18.x CLI is unable to establish connections using the <code>boundary connect</code> command
</td>
<td style={{verticalAlign: 'middle'}}>
Boundary version 0.18.x uses Go version 1.23, which introduced a new TLS handshake behavior. Some VPN providers struggle with the TLS handshake being sent over 2 frames instead of 1, which can lead to Boundary version 0.18.x controllers, workers, or clients being unable to establish connections. As a workaround, you can revert back to the previous TLS handshake behavior.
<br /><br />
To revert back to the previous TLS handshake behavior, add the <code>tlskyber=0</code> parameters to the GODEBUG environment variable before the <code>boundary connect</code> command. For example:
<br /><br />
<code>GODEBUG=tlskyber=0 boundary connect ssh -target-id &lt;ID&gt;</code>
<br /><br />
Learn more: <a href="https://github.com/golang/go/issues/70047">Go issue #70047</a> and <a href="https://tip.golang.org/doc/go1.23">Go 1.23 Release Notes</a>
<br /><br />
</td>
</tr>

</tbody>
</table>
Loading