From 1f94bef427e370e425e55b172f3b5e300ef38304 Mon Sep 17 00:00:00 2001 From: Filip Haglund Date: Sun, 29 Apr 2018 10:40:40 +0000 Subject: [PATCH] scrypt: update example to match recommendation two lines below Change-Id: I6eb5db30df9bc1c4b3c4124c9cdd3d504d33ad9d GitHub-Last-Rev: 1f585c4bf946a3241f8c38e1e954c4e5f8dc4713 GitHub-Pull-Request: golang/crypto#43 Reviewed-on: https://go-review.googlesource.com/110120 Reviewed-by: Brad Fitzpatrick --- scrypt/scrypt.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scrypt/scrypt.go b/scrypt/scrypt.go index ff28aae..9b25b5a 100644 --- a/scrypt/scrypt.go +++ b/scrypt/scrypt.go @@ -218,7 +218,7 @@ func smix(b []byte, r, N int, v, xy []uint32) { // For example, you can get a derived key for e.g. AES-256 (which needs a // 32-byte key) by doing: // -// dk, err := scrypt.Key([]byte("some password"), salt, 16384, 8, 1, 32) +// dk, err := scrypt.Key([]byte("some password"), salt, 32768, 8, 1, 32) // // The recommended parameters for interactive logins as of 2017 are N=32768, r=8 // and p=1. The parameters N, r, and p should be increased as memory latency and