T

Filippo Valsorda 1258d06b9d salsa20: panic when len(out) < len(in) following cipher.Stream

Change-Id: I5c8d603cc3ec844b8d44e51b3138bcf16e95c7fc
Reviewed-on: https://go-review.googlesource.com/112235
Reviewed-by: Adam Langley <agl@golang.org>
Run-TryBot: Filippo Valsorda <filippo@golang.org>

2018-05-09 19:27:45 +00:00

acme

acme/autocert: use valid certificates from the cache during renewal

2018-03-19 06:17:31 +00:00

argon2

crypto/{blake2b,blake2s,argon2,chacha20poly1305}: replace CPU feature detection

2018-04-30 18:12:35 +00:00

bcrypt

all: fix errors reported by vet, golint

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

blake2b

crypto/{blake2b,blake2s,argon2,chacha20poly1305}: replace CPU feature detection

2018-04-30 18:12:35 +00:00

blake2s

crypto/{blake2b,blake2s,argon2,chacha20poly1305}: replace CPU feature detection

2018-04-30 18:12:35 +00:00

blowfish

all: use HTTPS for links that support it

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

bn256

bn256: explicitly fix MakeAffine for ∞

2018-05-02 18:48:08 +00:00

cast5

crypto: add import comments.

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

chacha20poly1305

chacha20poly1305: correct AVX2 feature detection

2018-05-02 12:12:36 +00:00

cryptobyte

x/crypto: cryptobyte: manage integers with implicit tags

2018-04-20 17:11:55 +00:00

curve25519

all: fix article typos

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

ed25519

ed25519: require canonical signatures

2018-03-13 19:52:38 +00:00

hkdf

crypto: add import comments.

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

internal/chacha20

internal/chacha20: add s390x SIMD implementation

2018-04-26 23:03:45 +00:00

md4

md4: move the example to the right directory

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

nacl

nacl/sign: add package

2018-03-20 22:59:59 +00:00

ocsp

ocsp: remove error for > 1 certificate in response

2018-05-01 15:29:04 +00:00

openpgp

openpgp: fix vet issue in tests

2018-05-09 02:20:26 +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

ripemd160: use bits.Rotate for rotates

2018-03-08 18:56:24 +00:00

salsa20

salsa20: panic when len(out) < len(in) following cipher.Stream

2018-05-09 19:27:45 +00:00

scrypt

scrypt: update example to match recommendation two lines below

2018-05-03 21:59:45 +00:00

sha3

sha3: add NewLegacyKeccak256

2018-05-05 02:55:34 +00:00

ssh

ssh: fix copy and paste error

2018-05-01 15:52:21 +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

xtea: comment cleanup

2018-03-22 17:52:30 +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

CONTRIBUTING.md: remove note about not accepting Pull Requests

2018-03-14 18:02:59 +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.