T

Jake Burkhead 0b6b69c7d2 acme/autocert: return error from cachePut

Fixes https://github.com/golang/go/issues/23569

Change-Id: I0f3ffab74acd2b69da0bbec2e0e90e42c2618071
GitHub-Last-Rev: e66a888d643dacc290ef58649dcc248d1925219e
GitHub-Pull-Request: golang/crypto#35
Reviewed-on: https://go-review.googlesource.com/98756
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>

2018-03-06 22:18:58 +00:00

acme

acme/autocert: return error from cachePut

2018-03-06 22:18:58 +00:00

argon2

argon2: add Argon2id and update parameter recommendations

2018-02-06 19:08:13 +00:00

bcrypt

all: fix errors reported by vet, golint

2017-11-28 17:48:09 +00:00

blake2b

argon2: add new package implementing the Argon2 PBKDF family

2017-12-18 18:31:08 +00:00

blake2s

blake2s: fix vet format string issue

2017-11-05 17:26:29 +00:00

blowfish

all: use HTTPS for links that support it

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

bn256

bn256: don't claim a 128-bit security level.

2017-12-31 21:50:28 +00:00

cast5

crypto: add import comments.

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

chacha20poly1305

internal/chacha20: move up from chacha20poly1305/internal/chacha20

2018-01-10 14:51:33 +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: update document to mention RFC 8032

2017-10-31 16:01:30 +00:00

hkdf

crypto: add import comments.

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

internal/chacha20

internal/chacha20: move up from chacha20poly1305/internal/chacha20

2018-01-10 14:51:33 +00:00

md4

md4: move the example to the right directory

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

nacl

nacl/auth: use KeySize constant consistently.

2017-11-27 23:00:03 +00:00

ocsp

all: run gofmt -s on source code

2017-11-28 19:40:09 +00:00

openpgp

openpgp: allow NewEntity to specify the default cipher

2018-02-14 00:00:28 +00:00

otr

otr: add missing return on error path

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

pbkdf2

pbkdf2: add benchmarks

2017-12-19 04:11:29 +00:00

pkcs12

all: run gofmt -s on source code

2017-11-28 19:40:09 +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: add missing license header

2017-09-30 17:46:04 +00:00

sha3

all: run gofmt -s on source code

2017-11-28 19:40:09 +00:00

ssh

ssh: document how to unmarshal public keys

2018-02-27 08:58:43 +00:00

tea

all: fix errors reported by vet, golint

2017-11-28 17:48:09 +00:00

twofish

all: use HTTPS for links that support it

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

xtea

all: fix errors reported by vet, golint

2017-11-28 17:48:09 +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.