Go library for Enrollment over Secure Transport (EST), the certificate enrollment protocol defined in RFC 7030. It provides:
- an EST client library
- an
http.Handlerthat serves EST in front of your CA (NewRouterand theCAinterface) estclient, a command line client built on the libraryestserver, a server with a mock CA for testing and development
go get github.com/misiektoja/go-pki-estThe package name is est. Requires Go 1.27.3 or newer.
The command line tools install with:
go install github.com/misiektoja/go-pki-est/cmd/estclient@latestgo install github.com/misiektoja/go-pki-est/cmd/estserver@latest| Standard | Coverage | Enabled by |
|---|---|---|
| RFC 7030 EST | /cacerts, /csrattrs, /simpleenroll, /simplereenroll and /serverkeygen, with or without an additional path segment |
Always |
| RFC 7030 section 3.5 | tls-unique proof of possession over TLS 1.2 |
Client.SigningKey. The CA checks the value |
| RFC 7030 section 2.3 | Renewal with a password or token instead of the certificate | ServerConfig.PasswordRenewal |
| RFC 7030 section 3.3.3 and RFC 5054 | TLS-SRP sign-in without certificates | Client.SRPUsername and a go-tls-srp listener |
| RFC 6750 | Bearer tokens | Client.BearerToken and ServerConfig.CheckBearerToken |
| RFC 8951 | Whitespace in base64 and the Content-Transfer-Encoding header ignored |
Always |
| TPM 2.0 credential protection | /tpmenroll, an operation outside RFC 7030 |
CA.TPMEnroll |
ML-DSA keys work for enrollment, renewal over TLS 1.3 and server-generated keys. Composite ML-DSA
and SLH-DSA requests need a signature hook, because Go cannot verify them. /fullcmc is not
implemented.
Enroll a key with an EST server that asks for a password:
client := &est.Client{
Host: "est.example.com:8443",
ExplicitAnchor: anchor, // *x509.CertPool with the root of the EST server
Username: "device-1",
Password: "one-time-secret",
}
cert, err := client.Enroll(ctx, csr) // csr is a parsed *x509.CertificateRequest
if err != nil {
log.Fatal(err)
}To serve EST, implement the CA interface and pass it to est.NewRouter, which returns an
http.Handler for your TLS server.
Getting started runs estserver and
enrolls, renews and gets a server-generated key with estclient, then shows the same from Go.
Full documentation is at misiektoja.github.io/go-pki-est.
- Getting started
- Support matrix
- Architecture
- Enrollment and renewal and Signing in
- Embedding the server and The CA interface
- Server authentication and TLS-SRP
- Post-quantum algorithms
- estclient and estserver
- Troubleshooting
- Security model and Verifying a release
The package documentation on pkg.go.dev describes every exported type.
- No
/fullcmcand no CMS error responses. - The router does not check the
tls-uniquevalue or revocation. The CA does. - TLS 1.3 has no
tls-uniquevalue, so ML-DSA renewals carry no binding. - Composite ML-DSA and SLH-DSA need host hooks and cannot renew over TLS.
estserverissues to anyone and is for testing only.
Known limitations explains each gap.
This project began as a fork of globalsign/est by GMO GlobalSign. The protocol implementation, both command line tools and the test server come from that project. The first fixes made here were offered upstream in globalsign/est#59 to globalsign/est#66.
This fork is maintained separately so fixes and new features ship in its own releases without waiting for upstream review. Changes that suit upstream are still offered there. NOTICE records the attribution.
SUPPORT.md says where to ask questions and what to include in a bug report. Check Troubleshooting first. Report vulnerabilities privately as SECURITY.md describes. The Contributing Guide lists the development checks and the Code of conduct applies to every project space. CHANGELOG.md records the changes in each release and DEPENDENCIES.md lists the third-party modules and their licenses.