Adam Langley f752484c74 crypto/tls: don't select TLS 1.2 cipher suites in prior versions. ... AES-GCM cipher suites are only defined for TLS 1.2, although there's nothing really version specific about them. However, development versions of NSS (meaning Firefox and Chrome) have an issue where they'll advertise TLS 1.2-only cipher suites in a TLS 1.1 ClientHello but then balk when the server selects one. This change causes Go clients not to advertise TLS 1.2 cipher suites unless TLS 1.2 is being used, and prevents servers from selecting them unless TLS 1.2 has been negotiated. https://code.google.com/p/chromium/issues/detail?id=297151 https://bugzilla.mozilla.org/show_bug.cgi?id=919677 R=golang-dev, rsc CC=golang-dev https://golang.org/cl/13573047		2013-09-26 17:09:56 -04:00
..
cmd	cmd/go: "go test -c -test.bench=XX fmt" shouldn't hang	2013-09-25 16:18:33 -04:00
lib9	all: compiler/bootstrap for dragonfly/amd64	2013-08-24 01:18:04 +10:00
libbio	build: more "undefined behavior" fixes	2013-09-10 14:54:55 -04:00
libmach	libmach: accept OS X binary generated by external linker	2013-09-10 11:50:34 -07:00
pkg	crypto/tls: don't select TLS 1.2 cipher suites in prior versions.	2013-09-26 17:09:56 -04:00
all.bash
all.bat
all.rc
clean.bash
clean.bat
clean.rc
make.bash	make.bash: exit if dist fails	2013-08-19 11:18:43 +10:00
make.bat	cmd/dist: fix windows build.	2013-08-02 14:29:04 -07:00
Make.dist
make.rc
race.bash
race.bat
run.bash	cgo: enable cgo on dragonfly	2013-09-04 15:19:21 -07:00
run.bat	runtime/race: add end-to-end test on windows	2013-08-15 12:13:00 +10:00
run.rc	build: remove builder from test suite (fix build)	2013-08-01 13:49:00 +10:00
sudo.bash