crypto

Files

T

Gofmt to update doc comments to the new formatting.

For golang/go#51082.

Change-Id: I076031b6613691eefbb0f21739366e3fd2011ec9
Reviewed-on: https://go-review.googlesource.com/c/crypto/+/399356
Run-TryBot: Russ Cox <rsc@golang.org>
TryBot-Result: Gopher Robot <gobot@golang.org>
Auto-Submit: Russ Cox <rsc@golang.org>
Reviewed-by: Ian Lance Taylor <iant@google.com>

2022-04-11 22:02:26 +00:00

_asm

curve25519/internal/field: fix generator module reference to x/crypto

2021-05-13 16:48:29 +00:00

fe_alias_test.go

all: gofmt

2022-04-11 22:02:26 +00:00

fe_amd64_noasm.go

curve25519: replace field implementation with filippo.io/edwards25519

2021-05-05 21:26:54 +00:00

fe_amd64.go

all: gofmt

2022-04-11 22:02:26 +00:00

fe_amd64.s

all: add //go:build lines to assembly files

2021-05-13 12:29:33 +00:00

fe_arm64_noasm.go

curve25519: replace field implementation with filippo.io/edwards25519

2021-05-05 21:26:54 +00:00

fe_arm64.go

curve25519: replace field implementation with filippo.io/edwards25519

2021-05-05 21:26:54 +00:00

fe_arm64.s

all: add //go:build lines to assembly files

2021-05-13 12:29:33 +00:00

fe_bench_test.go

curve25519: replace field implementation with filippo.io/edwards25519

2021-05-05 21:26:54 +00:00

fe_generic.go

curve25519: replace field implementation with filippo.io/edwards25519

2021-05-05 21:26:54 +00:00

fe_test.go

curve25519: replace field implementation with filippo.io/edwards25519

2021-05-05 21:26:54 +00:00

fe.go

curve25519: replace field implementation with filippo.io/edwards25519

2021-05-05 21:26:54 +00:00

README

curve25519: replace field implementation with filippo.io/edwards25519

2021-05-05 21:26:54 +00:00

sync.checkpoint

curve25519: replace field implementation with filippo.io/edwards25519

2021-05-05 21:26:54 +00:00

sync.sh

curve25519: replace field implementation with filippo.io/edwards25519

2021-05-05 21:26:54 +00:00

README

This package is kept in sync with crypto/ed25519/internal/edwards25519/field in
the standard library.

If there are any changes in the standard library that need to be synced to this
package, run sync.sh. It will not overwrite any local changes made since the
previous sync, so it's ok to land changes in this package first, and then sync
to the standard library later.