qbit/go
1
0
Fork 0
mirror of https://github.com/golang/go synced 2024-11-23 05:10:09 -07:00
Code Releases Activity

doc/go1.19: minor adjustments and links

Browse Source 
A few last-minute clarifications before the release.

Change-Id: Ia0123441633c147aa3f76ea29ed26c7722e2416c
Reviewed-on: https://go-review.googlesource.com/c/go/+/419994
Reviewed-by: Ian Lance Taylor <iant@google.com>
This commit is contained in:
Russ Cox 2022-07-28 13:06:28 -04:00
parent 417be37048
commit 5c8ec89cb5
1 changed files with 15 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
doc/go1.19.html
View File

@ -31,7 +31,8 @@ Do not send CLs removing the interior tags from such phrases.
<h2 id="mem">Memory Model</h2> <h2 id="mem">Memory Model</h2>
<p><!-- https://go.dev/issue/50859 --> <p><!-- https://go.dev/issue/50859 -->
The <a href="/ref/mem">Go memory model</a> has been revised to align Go with The <a href="/ref/mem">Go memory model</a> has been
<a href="https://research.swtch.com/gomm">revised</a> to align Go with
the memory model used by C, C++, Java, JavaScript, Rust, and Swift. the memory model used by C, C++, Java, JavaScript, Rust, and Swift.
Go only provides sequentially consistent atomics, not any of the more relaxed forms found in other languages. Go only provides sequentially consistent atomics, not any of the more relaxed forms found in other languages.
Along with the memory model update, Along with the memory model update,
@ -378,11 +379,17 @@ as well as support for rendering them to HTML, Markdown, and text.
<p><!-- CL 391554 --><!-- CL 387554 --> <p><!-- CL 391554 --><!-- CL 387554 -->
The <a href="/pkg/crypto/rand/#Prime"><code>Prime</code></a> The <a href="/pkg/crypto/rand/#Prime"><code>Prime</code></a>
implementation was simplified. This will lead to different outputs for the implementation was changed to use only rejection sampling,
same random stream compared to the previous implementation. The internals which removes a bias when generating small primes in non-cryptographic contexts,
of <code>Prime</code> are not stable, should not be relied upon not to removes one possible minor timing leak,
change, and the output is now intentionally non-deterministic with respect and better aligns the behavior with BoringSSL,
to the input stream. all while simplifying the implementation.
The change does produce different outputs for a given random source
stream compared to the previous implementation,
which can break tests written expecting specific results from
specific deterministic random sources.
To help prevent such problems in the future,
the implementation is now intentionally non-deterministic with respect to the input stream.
</p> </p>
</dd> </dd>
</dl><!-- crypto/rand --> </dl><!-- crypto/rand -->
@ -390,7 +397,7 @@ as well as support for rendering them to HTML, Markdown, and text.
<dl id="crypto/tls"><dt><a href="/pkg/crypto/tls/">crypto/tls</a></dt> <dl id="crypto/tls"><dt><a href="/pkg/crypto/tls/">crypto/tls</a></dt>
<dd> <dd>
<p><!-- CL 400974 --><!-- https://go.dev/issue/45428 --> <p><!-- CL 400974 --><!-- https://go.dev/issue/45428 -->
The <code>tls10default</code> <code>GODEBUG</code> option has been The <code>GODEBUG</code> option <code>tls10default=1</code> has been
removed. It is still possible to enable TLS 1.0 client-side by setting removed. It is still possible to enable TLS 1.0 client-side by setting
<a href="/pkg/crypto/tls#Config.MinVersion"><code>Config.MinVersion</code></a>. <a href="/pkg/crypto/tls#Config.MinVersion"><code>Config.MinVersion</code></a>.
</p> </p>
@ -421,7 +428,7 @@ as well as support for rendering them to HTML, Markdown, and text.
</p> </p>
<p><!-- CL 396774 --> <p><!-- CL 396774 -->
Removal of the <code>x509sha1=1</code> <code>GODEBUG</code> option, Removal of the <code>GODEBUG</code> option<code>x509sha1=1</code>,
originally planned for Go 1.19, has been rescheduled to a future release. originally planned for Go 1.19, has been rescheduled to a future release.
Applications using it should work on migrating. Practical attacks against Applications using it should work on migrating. Practical attacks against
SHA-1 have been demonstrated since 2017 and publicly trusted Certificate SHA-1 have been demonstrated since 2017 and publicly trusted Certificate