certificates/kms/sshagentkms
Herman Slatman 2d85d4c1c1 Add non-TLS server and improve crypto.Decrypter interface
A server without TLS was added to serve the SCEP endpoints. According
to the RFC, SCEP has to be served via HTTP. The `sscep` client, for
example, will stop any URL that does not start with `http://` from
being used, so serving SCEP seems to be the right way to do it.

This commit adds a second server for which no TLS configuration is
configured. A distinct field in the configuration, `insecureAddress`
was added to specify the address for the insecure server.

The SCEP endpoints will also still be served via HTTPS. Some clients
may be able to work with that.

This commit also improves how the crypto.Decrypter interface is
handled for the different types of KMSes supported by step. The
apiv1.Decrypter interface was added. Currently only SoftKMS
implements this interface, providing a crypto.Decrypter required
for SCEP operations.
2021-05-26 16:09:38 -07:00
..
testdata Add support for using ssh-agent as a KMS 2020-11-04 09:06:23 +01:00
sshagentkms.go Add non-TLS server and improve crypto.Decrypter interface 2021-05-26 16:09:38 -07:00
sshagentkms_test.go add //nolint for new 1.16 deprecation warnings 2021-02-18 20:14:20 -08:00