diff options
| author | Matt Silverlock <silverlock@google.com> | 2018-09-13 20:58:55 +0300 |
|---|---|---|
| committer | Matt Silverlock <silverlock@google.com> | 2018-09-13 20:58:55 +0300 |
| commit | 1aeabd195284b0b9e2be63137c303377d84d7eb8 (patch) | |
| tree | f2098b745684c0b2096f227052bcbde813b39edf | |
| parent | 51f47194a536d357035c4ad9304e2fa42dde262a (diff) | |
[docs] Clarify usage of GenerateRandomKey
| -rw-r--r-- | README.md | 12 |
1 files changed, 7 insertions, 5 deletions
@@ -1,10 +1,9 @@ -securecookie -============ +# securecookie + [](https://godoc.org/github.com/gorilla/securecookie) [](https://travis-ci.org/gorilla/securecookie) [](https://sourcegraph.com/github.com/gorilla/securecookie?badge) - -securecookie encodes and decodes authenticated and optionally encrypted +securecookie encodes and decodes authenticated and optionally encrypted cookie values. Secure cookies can't be forged, because their values are validated using HMAC. @@ -33,7 +32,10 @@ to not use encryption. If set, the length must correspond to the block size of the encryption algorithm. For AES, used by default, valid lengths are 16, 24, or 32 bytes to select AES-128, AES-192, or AES-256. -Strong keys can be created using the convenience function GenerateRandomKey(). +Strong keys can be created using the convenience function +`GenerateRandomKey()`. Note that keys created using `GenerateRandomKey()` are not +automatically persisted. New keys will be created when the application is +restarted, and previously issued cookies will not be able to be decoded. Once a SecureCookie instance is set, use it to encode a cookie value: |