You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
tailscale/tempfork/acme
Brad Fitzpatrick 079973de82 tempfork/acme: fix TestSyncedToUpstream with Windows line endings
Updates #10238

Change-Id: Ic85811c267679a9f79377f376d77dee3a9d92ce7
Signed-off-by: Brad Fitzpatrick <bradfitz@tailscale.com>
10 months ago
..
README.md tempfork/acme: add new package for x/crypto package acme fork, move 10 months ago
acme.go tempfork/acme: add new package for x/crypto package acme fork, move 10 months ago
acme_test.go tempfork/acme: add new package for x/crypto package acme fork, move 10 months ago
http.go tempfork/acme: add new package for x/crypto package acme fork, move 10 months ago
http_test.go tempfork/acme: add new package for x/crypto package acme fork, move 10 months ago
jws.go tempfork/acme: add new package for x/crypto package acme fork, move 10 months ago
jws_test.go tempfork/acme: add new package for x/crypto package acme fork, move 10 months ago
rfc8555.go tempfork/acme: add new package for x/crypto package acme fork, move 10 months ago
rfc8555_test.go tempfork/acme: add new package for x/crypto package acme fork, move 10 months ago
sync_to_upstream_test.go tempfork/acme: fix TestSyncedToUpstream with Windows line endings 10 months ago
types.go tempfork/acme: add new package for x/crypto package acme fork, move 10 months ago
types_test.go tempfork/acme: add new package for x/crypto package acme fork, move 10 months ago
version_go112.go tempfork/acme: add new package for x/crypto package acme fork, move 10 months ago

README.md

tempfork/acme

This is a vendored copy of Tailscale's https://github.com/tailscale/golang-x-crypto, which is a fork of golang.org/x/crypto/acme.

See https://github.com/tailscale/tailscale/issues/10238 for unforking status.

The https://github.com/tailscale/golang-x-crypto location exists to let us do rebases from upstream easily, and then we update tempfork/acme in the same commit we go get github.com/tailscale/golang-x-crypto@main. See the comment on the TestSyncedToUpstream test for details. That test should catch that forgotten step.