New generates an AcmeWrapper given a configuration

CertNeedsUpdate returns whether the current certificate either does not exist, or is <X days from expiration, where X is set up in config, or does not

GetCertificate returns the current TLS certificate

Renew generates a new certificate

GetEmail returns the user email (if any) NOTE: NOT threadsafe

GetPrivateKey returns the private key for the given user. NOTE: NOT threadsafe

GetRegistration returns the registration currently being used NOTE: NOT threadsafe

TLSConfig returns a TLS configuration that will automatically work with the golang ssl listener. This sets it up so that the server automatically uses

initACME initailizes the acme client - it does everything from reading/writing the user private key and registration files, to ensuring that the user

http://stackoverflow.com/questions/15323767/does-golang-have-if-x-in-construct-similar-to-python

AcmeDisabled allows to enable/disable acme-based certificate. Note that it is assumed that this function is only called during server runtime (ie, you

AddSNI adds a domain name and certificate pair to the AcmeWrapper. Whenever a request is for the passed domain, its associated certifcate is returned.

RemSNI removes a domain name and certificate pair from the AcmeWrapper. It is assumed that they were added using AddSNI.

SetNewCert loads a new TLS key/cert from the given files. Running it with the same filenames as existing cert will reload them

checks if a is a subset of b

backgroundExpirationChecker is exactly that - it runs in the background and ensures that messages regarding certificate expiration as well as any rene

generateKey generates a key to use for registration in acme

loadPrivateKey reads a key from file This code copied from caddy: https://github.com/mholt/caddy/blob/master/caddy/https/crypto.go

AcmeWrapper version of LoadX509KeyPair reads and parses a public/private key pair from a pair of files. The files must contain PEM encoded data. Pulle

savePrivateKey is used to write the given key to file This code copied from caddy: https://github.com/mholt/caddy/blob/master/caddy/https/crypto.go

writeCert takes an acme CertificateResource (as returned from the acme.RenewCertificate and the acme.ObtainCertificate functions), and writes the cert

CleanUp removes the challenge domain from SNI. Part of acme.ChallengeProvider interface

Present sets up the challenge domain thru SNI. Part of acme.ChallengeProvider interface

TLSConfigGetCertificate is the main function used in the ACME wrapper. This is set in tls.Config to the GetCertificate property. Note that Certificate

TOSAgree always agrees to the terms of service. This should only be really used if you realize that you could be selling your soul without being notif

TOSDecline always declines to the terms of service. This can be usd for testing, when you want to make sure that ACME is really off, or that the user

We now test to make sure that if the domain is changed, the cert is changed

checks if the two arrays of strings contain the same elements