aboutsummaryrefslogtreecommitdiffstats
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
* Add signature generation operation classes. Remove sign() fromlloyd2010-03-0520-72/+474
| | | | | | PK_Signing_Key, though for the moment the class remains because there are a few pieces of code that use it to detect if signatures are supported, or for passing to functions in look_pk
* The operation can assume the key will continue to exist as long as it does,lloyd2010-03-042-7/+6
| | | | so keep the curve and cofactor in ECDH op by reference instead of value.
* Remove some unnecessary usages of PK_Signing_Keylloyd2010-03-043-54/+30
|
* Client_Key_Exchange needs modification for DH changeslloyd2010-03-041-14/+14
|
* This checkin represents a pretty major change in how PK operations arelloyd2010-03-0421-282/+221
| | | | | | | | | | | | | | | | | | | | | | | | | | | | performed. Up until now, each key object (eg DSA_PublicKey or ECDH_PrivateKey) had two jobs: contain the key material, and know how to perform any operations on that key. However because of a desire to support alternative implementations (GNU MP, hardware, whatever), there was a notion of operations, with the key objects containing an op that they got via engine rather than actually implementing the underlying algorithms directly. Now, represent the operation as an abstract interface (typically mapping a byte string to a byte string), and pass a plain Public_Key& or Private_Key& to the engine. The engine does any checks it wants (eg based on name, typeid, key sizes, etc), and either returns nothing (I'll pass) or a pointer to a new operation that represents signatures or encryption or what-have-you using that key. This means that plain key objects no longer contain operations. This is a major break with the traditional interface. On the other hand, using these 'bare' operations without padding, KDFs, etc is 99% of the time a bad idea anyway (and if you really need them, there are options so you get the bare op but via the pubkey.h interfaces). Currently this change is only implemented for DH and ECDH (ie, key agreement algorithms). Additionally the optional engines (gnump and openssl) have not been updated. I'll probably wait to touch those until after I can change them all in one go for all algos.
* Clean up PK_Key_Agreement slightlylloyd2010-03-042-21/+32
|
* Fix typoslloyd2010-03-041-2/+2
|
* Inline simple DSA funcslloyd2010-03-042-21/+6
|
* Remove ElGamal load hook functionslloyd2010-03-042-47/+23
|
* Remove NR load hookslloyd2010-03-042-58/+34
|
* Remove no-op DH_Public_Key::X509_load_hooklloyd2010-03-042-12/+1
|
* Remove DSA load hooks functionslloyd2010-03-042-32/+17
|
* Cleanupslloyd2010-03-041-5/+4
|
* Remove IF_Scheme_PrivateKey::PKCS8_load_hooklloyd2010-03-046-35/+30
|
* New IF constructors, simplifies RSA/RWlloyd2010-03-046-72/+67
|
* Remove DH_PrivateKey::PKCS8_load_hooklloyd2010-03-042-15/+23
|
* Remove unnecessary virtual destructors from ECC key base typeslloyd2010-03-041-4/+0
| | | | (already have them, via Public_Key's virtual destructor)
* Add back the Integrity_Failure exception. For one, removing it causeslloyd2010-03-041-0/+9
| | | | | problems for Monotone, and anyway it is a reasonable exception to have around for signalling MAC validation errors, etc.
* Fix GOST pubkey encoding when x.bytes() != y.bytes()lloyd2010-03-041-1/+1
|
* Fix exception textlloyd2010-03-041-1/+1
|
* Quite the hack, here.lloyd2010-03-043-1/+11
| | | | | | | | | | | | | | | | | GOST 34.10 public keys use a funky encoding. There is no standard for PKCS #8 format private keys, so the obvious choice is to act exactly the same as ECDSA/ECDH (following the rule of thumb that if you're going to make up a random non-standard thing, at least try to copy something that's standard for something else). However the public key encoding uses a weird scheme for encoding the OID in the algorithm identifier, which we don't want to use for the PKCS #8 encoding. Add a new function to Private_Key, pkcs8_algorithm_identifier, which by default just calls algorithm_identifier(). However GOST_3410_PrivateKey overrides it, and calls EC_PublicKey::algorithm_identifier(), basically skipping over the virtual function hierarchy, so it doesn't pick up the funky format from the public key's version of algorithm_identifier().
* Fix GOST 34.10 pubkey encodinglloyd2010-03-042-3/+13
|
* Fix loading ElGamal keyslloyd2010-03-041-6/+4
|
* Catch parse errors in OID, throw Invalid_OIDlloyd2010-03-041-1/+9
|
* Fix ElGamal pubkey encoding (OID was unknown)lloyd2010-03-041-1/+1
|
* Catch any exception for parsing name, assume it's a bad OIDlloyd2010-03-041-1/+1
|
* Changes to CVC to deal with the fact that you can't create an uninitializedlloyd2010-03-043-8/+10
| | | | ECDSA_PublicKey object anymore.
* Remove more load hookslloyd2010-03-047-17/+10
|
* Remove load hooks from ECC classes, unusedlloyd2010-03-043-21/+16
|
* Kill pkcs8_decoderlloyd2010-03-048-158/+0
|
* Add similar decoding constructors to the private keyslloyd2010-03-0416-82/+164
|
* Remove X509_Decoder. Fix GOST-34.10 DER constructor (was default to normal ECC)lloyd2010-03-0410-173/+24
|
* Add a new constructor to each public key algorithm (only the publiclloyd2010-03-0419-114/+193
| | | | | | | keys so far, private keys not changed) that takes an AlgorithmIdentifier and a MemoryRegion<byte>&. This performs the X.509 decoding. It is not possible anymore to create uninitialized PK objects.
* The code in pk_codecs was actually entirely tied to the code inlloyd2010-03-0412-13/+7
| | | | | | pubkey; you literally could not compile any pubkey code without it. Move it up to the pubkey dir, it wasn't at all useful to have it in its own dir.
* Kill pkcs8_encoderlloyd2010-03-048-124/+4
|
* Add a pkcs8_private_key similiar to x509_subject_public_keylloyd2010-03-048-27/+49
|
* Add a new function to public key x509_subject_public_key which returnslloyd2010-03-0411-140/+34
| | | | | what x509_encoder()->key_bits() used to return. This is much simpler than using the explicit encoder objects. Remove X509_Encoder entirely.
* Add a new function to Public_Key, algorithm_identifier(), which justlloyd2010-03-048-23/+36
| | | | | returns the AlgorithmIdentifier representing this scheme (OID + domain params if any).
* Fix stupid typolloyd2010-03-031-1/+1
|
* Pass the args to SIMD_32 variant of rotate_left/rotate_right as constlloyd2010-03-031-6/+6
| | | | | reference. Otherwise Visual C++ dies because apparently the Win32 ABI doesn't know how to pass a __m128i as a function parameter. :/
* Only disable VC++ warning C4275 with DLL buildslloyd2010-03-031-2/+2
|
* Unused variable warning in catch statementlloyd2010-03-031-1/+1
|
* Unused variable warning in catch statementlloyd2010-03-031-1/+1
|
* Fix VC++ static lib buildslloyd2010-03-031-0/+4
|
* Fix Windows distclean targetlloyd2010-03-031-1/+3
|
* Disable VC warning 4275lloyd2010-03-031-1/+1
|
* Remove BOTAN_DLL from templates, VC++ doesn't like itlloyd2010-03-032-2/+2
|
* Reorganize where some CVC code goes to avoid template bloat + VC problemslloyd2010-03-037-95/+66
|
* Minor cleanups in Salsa20 codelloyd2010-03-032-42/+9
|
* Use static_cast if using std::time-based get_nanoseconds_clock to makelloyd2010-03-031-2/+6
| | | | | | it obvious that truncation is occuring. Something to deal with in 2038 I guess, though get_nanoseconds_clock is already an unknown/unspecified epoch (since the Windows timer uses 1/1/1601 as the epoch)
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-18 21:02:29 +0000