Next | Query returned 330 messages, browsing 181 to 190 | Previous

History of commit frequency

CVS Commit History:


   2019-09-26 20:36:46 by Benny Siegert | Files touched by this commit (3)
Log message:
Update go112 to 1.12.10.

Commit ok'd by wiz@ for PMC.

Go 1.12.10:

net/http (through net/textproto) used to accept and normalize invalid
HTTP/1.1 headers with a space before the colon, in violation of RFC 7230. If
a Go server is used behind an uncommon reverse proxy that accepts and
forwards but doesn't normalize such invalid headers, the reverse proxy and
the server can interpret the headers differently. This can lead to filter
bypasses or request smuggling, the latter if requests from separate clients
are multiplexed onto the same upstream connection by the proxy. Such invalid
headers are now rejected by Go servers, and passed without normalization to
Go client applications.

The issue is CVE-2019-16276 and Go issue golang.org/issue/34540.

Go 1.12.9:

go1.12.9 (released 2019/08/15) includes fixes to the linker, and the os and
math/big packages. See the Go 1.12.9 milestone on our issue tracker for
details.
   2019-09-17 06:39:20 by Darrin B. Jewell | Files touched by this commit (1)
Log message:
lang/go: on osx 10.9 and earlier, use go110

go 1.11 removed support for osx 10.8 and 10.9
https://github.com/golang/go/issues/23122
   2019-09-10 22:19:54 by Roland Illig | Files touched by this commit (1) | Package updated
Log message:
lang/go: update _VARGROUPS in go-package.mk, small refactoring
   2019-09-10 22:01:06 by Roland Illig | Files touched by this commit (1)
Log message:
lang/go: extend _VARGROUPS section in go-dep.mk
   2019-08-14 17:42:52 by Benny Siegert | Files touched by this commit (3) | Package updated
Log message:
go112: update to 1.12.8 (security release).

net/http: Denial of Service vulnerabilities in the HTTP/2 implementation

net/http and golang.org/x/net/http2 servers that accept direct connections from
untrusted clients could be remotely made to allocate an unlimited amount of
memory, until the program crashes. Servers will now close connections if the
send queue accumulates too many control messages.

The issues are CVE-2019-9512 and CVE-2019-9514, and Go issue golang.org/issue/33606.
Thanks to Jonathan Looney from Netflix for discovering and reporting these issues.

This is also fixed in version v0.0.0-20190813141303-74dc4d7220e7 of
golang.org/x/net/http2.

net/url: parsing validation issue

url.Parse would accept URLs with malformed hosts, such that the Host field
could have arbitrary suffixes that would appear in neither Hostname() nor
Port(), allowing authorization bypasses in certain applications. Note that URLs
with invalid, not numeric ports will now return an error from url.Parse.

The issue is CVE-2019-14809 and Go issue golang.org/issue/29098.
Thanks to Julian Hector and Nikolai Krein from Cure53, and Adi Cohen (adico.me)
for discovering and reporting this issue.
   2019-08-14 17:17:41 by Benny Siegert | Files touched by this commit (3) | Package updated
Log message:
go111: update to 1.11.13 (security release).

net/http: Denial of Service vulnerabilities in the HTTP/2 implementation

net/http and golang.org/x/net/http2 servers that accept direct connections from
untrusted clients could be remotely made to allocate an unlimited amount of
memory, until the program crashes. Servers will now close connections if the
send queue accumulates too many control messages.

The issues are CVE-2019-9512 and CVE-2019-9514, and Go issue golang.org/issue/33606.
Thanks to Jonathan Looney from Netflix for discovering and reporting these issues.

This is also fixed in version v0.0.0-20190813141303-74dc4d7220e7 of
golang.org/x/net/http2.

net/url: parsing validation issue

url.Parse would accept URLs with malformed hosts, such that the Host field
could have arbitrary suffixes that would appear in neither Hostname() nor
Port(), allowing authorization bypasses in certain applications. Note that URLs
with invalid, not numeric ports will now return an error from url.Parse.

The issue is CVE-2019-14809 and Go issue golang.org/issue/29098.
Thanks to Julian Hector and Nikolai Krein from Cure53, and Adi Cohen (adico.me)
for discovering and reporting this issue.
   2019-07-14 17:19:55 by Benny Siegert | Files touched by this commit (3)
Log message:
Update go112 to 1.12.7.

This fixes a nasty code-generation bug, among other things:

go1.12.6 (released 2019/06/11) includes fixes to the compiler, the linker,
the go command, and the crypto/x509, net/http, and os packages.
See the Go 1.12.6 milestone on our issue tracker for details.

go1.12.7 (released 2019/07/08) includes fixes to cgo, the compiler,
and the linker. See the Go 1.12.7 milestone on our issue tracker for details.
   2019-07-14 14:25:19 by Benny Siegert | Files touched by this commit (3)
Log message:
Update go111 to 1.11.12.

go1.11.11 (released 2019/06/11) includes a fix to the crypto/x509 package.
See the Go 1.11.11 milestone on our issue tracker for details.

go1.11.12 (released 2019/07/08) includes fixes to the compiler and the linker.
See the Go 1.11.12 milestone on our issue tracker for details.
   2019-05-27 17:16:38 by Benny Siegert | Files touched by this commit (4)
Log message:
Update go112 to 1.12.5.

This release includes fixes to the compiler, the linker, the go command,
the runtime, and the os package.

Same as for go111, remove the pkg/bootstrap tree from the package.
   2019-05-27 16:33:11 by Benny Siegert | Files touched by this commit (4)
Log message:
Update go111 to 1.11.10.

This release includes fixes to the compiler, the linker, the go command, the
runtime, and the os package.

While here, remove pkg/bootstrap from the package, as it is only used
for bootstrapping.

Next | Query returned 330 messages, browsing 181 to 190 | Previous