boulder/core
Aaron Gable e2c8f6743a
Introduce new core.AcmeChallenge type (#5012)
ACME Challenges are well-known strings ("http-01", "dns-01", and
"tlsalpn-01") identifying which kind of challenge should be used
to verify control of a domain. Because they are well-known and
only certain values are valid, it is better to represent them as
something more akin to an enum than as bare strings. This also
improves our ability to ensure that an AcmeChallenge is not
accidentally used as some other kind of string in a different
context. This change also brings them closer in line with the
existing core.AcmeResource and core.OCSPStatus string enums.

Fixes #5009
2020-08-11 15:02:16 -07:00
..
proto Use 2-space indents in all proto files (#5006) 2020-08-05 10:38:19 -07:00
challenges.go Introduce new core.AcmeChallenge type (#5012) 2020-08-11 15:02:16 -07:00
challenges_test.go Make authz2 the default storage format (#4476) 2019-10-21 15:29:15 -04:00
core_test.go Introduce new core.AcmeChallenge type (#5012) 2020-08-11 15:02:16 -07:00
interfaces.go Introduce new core.AcmeChallenge type (#5012) 2020-08-11 15:02:16 -07:00
objects.go Introduce new core.AcmeChallenge type (#5012) 2020-08-11 15:02:16 -07:00
objects_test.go Introduce new core.AcmeChallenge type (#5012) 2020-08-11 15:02:16 -07:00
util.go Move CA RPC non-nil checks out of wrappers (#4971) 2020-07-22 17:42:16 -07:00
util_test.go Move CA RPC non-nil checks out of wrappers (#4971) 2020-07-22 17:42:16 -07:00