Alternative TLS implementation in Go

Kyle Consalus 67c5445327 Removed bytes.Add and bytes.AddByte; we now have 'append'. ... Changed all uses of bytes.Add (aside from those testing bytes.Add) to append(a, b...). Also ran "gofmt -s" and made use of copy([]byte, string) in the fasta benchmark. R=golang-dev, r, r2 CC=golang-dev https://golang.org/cl/3302042		2010-12-01 11:59:13 -08:00
alert.go	crypto/tls: simpler implementation of record layer	2010-04-26 22:19:04 -07:00
ca_set.go	crypto/tls: use pool building for certificate checking	2010-11-05 09:54:56 -04:00
common.go	crypto/tls: client certificate support.	2010-08-16 11:22:22 -04:00
conn.go	Removed bytes.Add and bytes.AddByte; we now have 'append'.	2010-12-01 11:59:13 -08:00
generate_cert.go	log: new interface	2010-10-12 12:59:18 -07:00
handshake_client.go	crypto/tls: use pool building for certificate checking	2010-11-05 09:54:56 -04:00
handshake_messages_test.go	crypto/tls: client certificate support.	2010-08-16 11:22:22 -04:00
handshake_messages.go	use append	2010-10-27 19:47:23 -07:00
handshake_server_test.go	gofmt -s -w src misc	2010-10-22 10:06:33 -07:00
handshake_server.go	gofmt -s -w src misc	2010-10-22 10:06:33 -07:00
Makefile	build: no required environment variables	2010-08-18 10:08:49 -04:00
prf_test.go	gofmt -s -w src misc	2010-10-22 10:06:33 -07:00
prf.go	crypto/hmac: make Sum idempotent	2010-08-26 13:32:29 -04:00
tls.go	crypto/tls: use pool building for certificate checking	2010-11-05 09:54:56 -04:00