Alex Vaghin 6575f7ea32 acme: build up full chain certs when requested
The latest ACME spec (v3) changed the wording to:

    ... the server MUST send one or more link relation header
    fields [RFC5988] with relation "up", each indicating a single
    certificate resource for the issuer of this certificate.  The server
    MAY also include the "up" links from these resources to enable the
    client to build a full certificate chain.

See https://tools.ietf.org/html/draft-ietf-acme-acme-03#section-6.3.1.

Before this change, Client was fetching only the first "up" link, but never
checked to follow the chain further. To my knowledge, Let's Encrypt never
provided a chain longer than 1, this is just to make the Client future proof.

Also fixes google/acme#26.

Change-Id: I35cf5f1997b21a0b2a2d0a732043a7e04b7f1c45
Reviewed-on: https://go-review.googlesource.com/26693
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2016-08-15 19:30:22 +00:00
2014-12-09 23:26:36 +00:00
2014-12-09 23:26:36 +00:00
2014-12-09 23:26:36 +00:00
2016-04-25 23:11:06 +00:00
2014-12-09 23:26:36 +00:00
2014-12-09 23:26:36 +00:00
2014-12-09 23:26:36 +00:00
2016-07-06 16:40:51 +00:00
2014-12-09 23:26:36 +00:00
2014-12-09 23:26:36 +00:00
2014-12-09 23:26:36 +00:00
2014-12-09 23:26:36 +00:00
2016-07-06 16:40:51 +00:00
2014-12-09 23:26:36 +00:00
2014-12-09 23:26:36 +00:00
2014-12-09 23:26:36 +00:00
2014-12-08 10:41:13 +11:00
2015-03-18 17:04:25 +00:00
2015-02-18 23:42:20 +00:00
2012-03-17 15:19:30 +11:00
2012-01-25 15:31:12 -05:00

This repository holds supplementary Go cryptography libraries.

To submit changes to this repository, see http://golang.org/doc/contribute.html.
S
Description
Mirror of ys-ll/crypto (GitHub), kept for paraterm builds
https://golang.org/x/crypto
Readme BSD-3-Clause
8.1 MiB
Languages
Go 88.6%
Assembly 11.1%
C 0.3%