7 Commits (ab44fbfb3f8d10669340e66feacef7c06dcac0b3)

Author	SHA1	Message	Date
Mariano Cano	6d644880bd	Allow to kms signers to define the SignatureAlgorithm ... CloudKMS keys signs data using an specific signature algorithm, in RSA keys, this can be PKCS#1 RSA or RSA-PSS, if the later is used, x509.CreateCertificate will fail unless the template SignatureCertificate is properly set. On contrast, AWSKMS RSA keys, are just RSA keys, and can sign with PKCS#1 or RSA-PSS schemes, so right now the way to enforce one or the other is to used templates.	3 years ago
Mariano Cano	163eb7029c	Refactor cloudkms signer to return an error on the constructor.	4 years ago
Mariano Cano	d30a95236d	Use always go.step.sm/crypto	4 years ago
Mariano Cano	fa8116497c	Make Signer public and add contructor NewCloudKMS.	5 years ago
Mariano Cano	dff498f17f	Add tests for cloudkms.	5 years ago
Mariano Cano	e60beeb7fc	Make cloudkms more robust. ... * Automatically create key rings if needed. * User CryptoKeyVersions if needed. * Add support to close the client. * Add new pareters to CreateKey responses to make things easier.	5 years ago
Mariano Cano	d13754166a	Add support for cloudkms and softkms.	5 years ago