moby/vendor/golang.org/x/crypto/curve25519/internal/field
Sebastiaan van Stijn e48b58e1be
vendor: golang.org/x/crypto v0.16.0
full diff: https://github.com/golang/crypto/compare/v0.14.0...v0.16.0

Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-12-18 13:39:50 +01:00
..
fe.go go.mod: golang.org/x/crypto 5770296d904e90f15f38f77dfc2e43fdf5efc083 2021-12-03 09:19:28 +01:00
fe_amd64.go vendor: golang.org/x/crypto v0.16.0 2023-12-18 13:39:50 +01:00
fe_amd64.s vendor: golang.org/x/crypto v0.16.0 2023-12-18 13:39:50 +01:00
fe_amd64_noasm.go vendor: golang.org/x/crypto v0.16.0 2023-12-18 13:39:50 +01:00
fe_arm64.go vendor: golang.org/x/crypto v0.16.0 2023-12-18 13:39:50 +01:00
fe_arm64.s vendor: golang.org/x/crypto v0.16.0 2023-12-18 13:39:50 +01:00
fe_arm64_noasm.go vendor: golang.org/x/crypto v0.16.0 2023-12-18 13:39:50 +01:00
fe_generic.go vendor: golang.org/x/crypto v0.9.0 2023-09-18 18:17:29 +02:00
README go.mod: golang.org/x/crypto 5770296d904e90f15f38f77dfc2e43fdf5efc083 2021-12-03 09:19:28 +01:00
sync.checkpoint vendor: regenerate 2022-01-18 15:46:04 +01:00
sync.sh vendor: regenerate 2022-01-18 15:46:04 +01:00

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.