T

Kevin Burke 34d0413e1b scrypt: update recommended parameters for 2017

Previously we documented recommended parameters for scrypt from 2009,
which was eight years ago. Update those parameters and also provide
some guidance to users for configuring those settings in 2017. On my
late 2015 Macbook Pro, the scrypt benchmark with N=1<<15, r=8, p=1
completes in 91 milliseconds.

Add an Example with a salt.

Fixes golang/go#22082.

Change-Id: I23e3920db67583c9fce093768a32e67ab9c979f5
Reviewed-on: https://go-review.googlesource.com/67070
Reviewed-by: Adam Langley <agl@golang.org>

2017-09-30 16:10:57 +00:00

acme

acme/autocert: add Cache to Manager example

2017-09-28 14:24:50 +00:00

bcrypt

bcrypt: fix C compatibility code

2017-05-22 14:29:59 +00:00

blake2b

blake2b: fix typo in error message

2017-09-27 20:05:19 +00:00

blake2s

blake2s: implement BLAKE2X

2017-07-05 21:44:04 +00:00

blowfish

all: use HTTPS for links that support it

2017-06-29 04:21:55 +00:00

bn256

bn256: fix equations in comments

2016-12-06 19:59:59 +00:00

cast5

crypto: add import comments.

2014-12-09 23:26:36 +00:00

chacha20poly1305

all: make overlap rules wording consistent

2017-09-11 15:03:43 +00:00

cryptobyte

cryptobyte: include changes from review of 57810

2017-09-12 19:18:25 +00:00

curve25519

all: fix article typos

2017-09-15 13:46:28 +00:00

ed25519

ed25519: don't use constant-time functions in Verify.

2017-08-03 20:31:46 +00:00

hkdf

crypto: add import comments.

2014-12-09 23:26:36 +00:00

md4

md4: move the example to the right directory

2017-07-20 17:59:35 +00:00

nacl

all: make overlap rules wording consistent

2017-09-11 15:03:43 +00:00

ocsp

ocsp: remove a redundant conditional expression from an if statement

2017-07-11 14:53:18 +00:00

openpgp

all: fix article typos

2017-09-15 13:46:28 +00:00

otr

otr: add missing return on error path

2017-01-18 18:54:26 +00:00

pbkdf2

crypto: add import comments.

2014-12-09 23:26:36 +00:00

pkcs12

all: fix article typos

2017-09-15 13:46:28 +00:00

poly1305

all: use HTTPS for links that support it

2017-06-29 04:21:55 +00:00

ripemd160

crypto: add import comments.

2014-12-09 23:26:36 +00:00

salsa20

all: make overlap rules wording consistent

2017-09-11 15:03:43 +00:00

scrypt

scrypt: update recommended parameters for 2017

2017-09-30 16:10:57 +00:00

sha3

sha3: delete unused field

2017-08-25 22:01:21 +00:00

ssh

ssh: remove unused buffer.eof return value

2017-09-25 11:19:01 +00:00

tea

x/crypto: add support for Tiny Encryption Algorithm (TEA)

2015-07-29 20:20:17 +00:00

twofish

all: use HTTPS for links that support it

2017-06-29 04:21:55 +00:00

xtea

crypto: add import comments.

2014-12-09 23:26:36 +00:00

xts

all: make overlap rules wording consistent

2017-09-11 15:03:43 +00:00

.gitattributes

crypto: copying .gitattributes to all subrepositories

2014-12-23 06:54:52 +00:00

.gitignore

convert .hgignore to .gitignore.

2014-12-08 10:41:13 +11:00

AUTHORS

all: use HTTPS for links that support it

2017-06-29 04:21:55 +00:00

codereview.cfg

crypto: add codereview.cfg

2015-03-18 17:04:25 +00:00

CONTRIBUTING.md

doc: add CONTRIBUTING.md

2015-02-18 23:42:20 +00:00

CONTRIBUTORS

all: use HTTPS for links that support it

2017-06-29 04:21:55 +00:00

LICENSE

LICENSE: add

2012-03-17 15:19:30 +11:00

PATENTS

go.crypto: add PATENTS file to the subrepo.

2012-04-16 11:25:08 +10:00

README.md

README: add improvements

2017-07-19 14:12:01 +00:00

README.md

Go Cryptography

This repository holds supplementary Go cryptography libraries.

Download/Install

The easiest way to install is to run go get -u golang.org/x/crypto/.... You can also manually git clone the repository to $GOPATH/src/golang.org/x/crypto.

Report Issues / Send Patches

This repository uses Gerrit for code changes. To learn how to submit changes to this repository, see https://golang.org/doc/contribute.html.

The main issue tracker for the crypto repository is located at https://github.com/golang/go/issues. Prefix your issue with "x/crypto:" in the subject line, so it is easy to find.

Note that contributions to the cryptography package receive additional scrutiny due to their sensitive nature. Patches may take longer than normal to receive feedback.