3 Commits

Include renames

Author	SHA1	Message	Date
Dave Cheney	36d74d6fed	go.crypto/ssh: fix panic unmarshalling channelOpenFailureMsg ... I introduced this problem in change set 33 when I redefined RejectionReason from a uint32 to an int. I have added a test to verify the message can be marshaled correctly. This was a bit hard to track down as the recover in clientConn mainLoop would catch the panic and shutdown the connection. We probably shouldn't be using panic inside marshal/unmarshal, at least not without a way to let the user know why the recover logic tripped. R=agl, kardianos, gustav.paul CC=golang-dev https://golang.org/cl/6210063	2012-05-18 09:11:31 +10:00
Dave Cheney	73a4e109cb	go.crypto/ssh: add benchmarks for marshal and unmarshal ... R=agl CC=golang-dev https://golang.org/cl/5730045	2012-03-04 14:01:23 -08:00
Russ Cox	470549d502	go.crypto: initial code ... Manual edits to README. Moved from main Go repository, deleted Makefiles, ran gofix -r go1rename. Tested with: go test code.google.com/p/go.crypto/... R=golang-dev, bradfitz CC=golang-dev https://golang.org/cl/5564059	2012-01-25 15:31:12 -05:00