forked from secure-systems-lab/securesystemslib
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Inheritance CrytoSigner -> _{RSA,...}Signer does not make sense. We want to just create CryptoSigner by throwing a pyca private key at it. Composition, seems to be better, if at all. The nesting now gets a bit deep. SslibSigner._crypto_signer._signer._private_key (sslibsigner will go away, but still) Is CryptoSigner._private_key enough? Yes, and we'd have to - do scheme check to original dispatch in init (okay), - case handle in sign (okay), and - either, - re-parse additional sign params from scheme on each sign (not nice), - or store different additional sign parameters (this could work) class SignArgs: class RSAArgs - padding - hash_algorithm class ECDSAArgs - signature_algorithm Signed-off-by: Lukas Puehringer <[email protected]>
- Loading branch information
Showing
1 changed file
with
52 additions
and
60 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters