kris/th5
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

crypto/tls: clarify concurrent use of Config

Browse Source 
LGTM=r, agl
R=agl, r
CC=golang-codereviews
https://golang.org/cl/77530044
This commit is contained in:
Brad Fitzpatrick 2014-03-20 08:32:06 -07:00
parent ef4934a9ed
commit ab3538d779
1 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
common.go
View File

@ -201,12 +201,15 @@ type ClientSessionCache interface {
Put(sessionKey string, cs *ClientSessionState) Put(sessionKey string, cs *ClientSessionState)
} }
// A Config structure is used to configure a TLS client or server. After one // A Config structure is used to configure a TLS client or server.
// has been passed to a TLS function it must not be modified. // After one has been passed to a TLS function it must not be
// modified. A Config may be reused; the tls package will also not
// modify it.
type Config struct { type Config struct {
// Rand provides the source of entropy for nonces and RSA blinding. // Rand provides the source of entropy for nonces and RSA blinding.
// If Rand is nil, TLS uses the cryptographic random reader in package // If Rand is nil, TLS uses the cryptographic random reader in package
// crypto/rand. // crypto/rand.
// The Reader must be safe for use by multiple goroutines.
Rand io.Reader Rand io.Reader
// Time returns the current time as the number of seconds since the epoch. // Time returns the current time as the number of seconds since the epoch.