Spurious Hash Implementation in ECIES

[Jeffrey Walton]

Hi All (Wei),

I was interested in feedback on the Hash class. My testing of it's use
(relinquishing the properties of T in ECIES ciphertext object(C, V, T)
show no adverse side effects. But testing and knowing are two
different things.

Also, can I gain back a _small_ bit of T's properties by using a CRC
(word32 is the minimum Hash size if 0 is not used). I understand
either way it is an incorrect impleementation of ECIES (when not using
an approved Signature function).

Jeff

class TRUEHash : public
CryptoPP::IteratedHashWithStaticTransform<CryptoPP::word32,
     CryptoPP::BigEndian, 32, 4, TRUEHash>
{
public:
  static void InitState(HashWordType *state)
     { state[0] = 0x01; return; }
  static void Transform(CryptoPP::word32 *digest, const CryptoPP::word32 *data)
     { return; }
  static const char *StaticAlgorithmName() {return "TRUE HASH";}
};