From aa2481cbfe81d911eb62b642b7a6b5ec58bbea71 Mon Sep 17 00:00:00 2001 From: Sam Whited Date: Fri, 9 Sep 2016 21:06:31 -0500 Subject: [PATCH] scrypt: fix broken example in documentation Fixes golang/go#17046 Change-Id: I7fa7e0b700212992125de32524801048b56ac5d1 Reviewed-on: https://go-review.googlesource.com/28952 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 dc0124b1..7455395c 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 := scrypt.Key([]byte("some password"), salt, 16384, 8, 1, 32) +// dk, err := scrypt.Key([]byte("some password"), salt, 16384, 8, 1, 32) // // The recommended parameters for interactive logins as of 2009 are N=16384, // r=8, p=1. They should be increased as memory latency and CPU parallelism