acmed

Commit Graph

Author	SHA1	Message	Date
Rodolphe Breard	4eb0423da3	Reformat log messages	5 years ago
Rodolphe Breard	51cfd49f08	Refactor the account management Until now, the account management was archaic and it was impossible to improve it without this heavy refactoring. Accounts are now disjoint from both certificates and endpoints. They have their own hooks and their own environment variables. They are stored in a binary file instead of the PEM exports of the private and public keys. This refactoring will allow account management to evolve into something more serious, with real key rollover, contact information update and so on.	5 years ago
Rodolphe Breard	f640688a3b	Refactor the hash function interface	5 years ago
Rodolphe Breard	4614d6c407	Add partial EdDSA support Currently, OpenSSL does not have the required `EVP_PKEY_get1_ED(25519\|448)` functions, hence EdDSA has been partially implemented and disabled. Once OpenSSL 3.0.0 is out and the `openssl` crates implements the bindings to those functions, full EdDSA implementation could be done and activated. Conditional compilation has been implemented using `rustc-cfg` instructions rather than features so it can be activated from the build script depending on whether or not the cryptographic library supports Ed25519 and Ed448. `7c664b1f1b`	5 years ago
Rodolphe Breard	387adc7c4f	Remove the useless calls to `map_err`	5 years ago
Rodolphe Breard	1350257300	Put Ed25519 support in a feature	5 years ago
Rodolphe Breard	636fbf9cf6	Refactor the JWS signature algorithm management Being tied with the key type, the signature algorithm should therefore be at the same place than the key type, hence `acme_common::crypto`. This reorganization will allow to specify the account key type as well as the signature algorithm in the configuration.	5 years ago
Rodolphe Breard	d7dbd58823	Move the hashing operation inside the signing function This hashing operation is part of the signing process itself and should therefore not be exposed outside of the signing function.	5 years ago
Rodolphe Breard	eabcddb0af	Add support for RSA 2048 account keys	5 years ago
Rodolphe Breard	1ab5b4012e	Use the correct algorithm and hash function for JWK signatures Since there is currently no possibility to chose a different account key type, the current implementation only supports the ES256 algorithm. With the upcoming support of different key types, it had to be changed. This commit add support for ES384 although there is no configuration option that can activate the actual use of it through account keys using the NIST P-384 curve.	5 years ago
Rodolphe Breard	996ea85be4	Format code	5 years ago
Jakub Pastuszek	155feb345c	always use NAMED_CURVE format for EC key storage; fixes #9	5 years ago
Rodolphe Breard	f1f95c4d99	Display a more precise error message for unknown EC keys	5 years ago
Rodolphe Breard	55f4d3416b	Refactor the JWK implementation	6 years ago
Rodolphe Breard	4ea49512d6	Remove the standalone feature As discussed in #2, ring is not mature enough to replace OpenSSL. Hence, the standalone mode which has been made to implement such a replacement has to be removed until ring becomes usable.	6 years ago
Rodolphe Breard	84102922fa	Move KeyType to a dedicated module	6 years ago
Rodolphe Breard	70df290306	Rewrite the crypto keys abstraction Until now, the crypto key abstraction used two different type: PublicKey and PrivateKey. Unfortunately, it does not work with ring and should therefore be rewrote with a single type: KeyPair.	6 years ago
Rodolphe Breard	e42d242868	Remove useless closures	6 years ago
Rodolphe Breard	63e35712fe	Create an abstraction around public and private keys Since it is planned to add a "standalone" feature that will replace OpenSSL by crates not linking to any external library, it is required to abstract all the OpenSSL specific types. This is a huge work and therefore is divided in several steps. This first one is dedicated to public and private keys. rel #2	6 years ago

19 Commits (4eb0423da3f0379aa2274507d7c161a15e7babf8)