Fixed valgrind complaint about using uninitialized data when generating a OneTimePad. The algorithm uses unsigned char x as a register. Each next random byte in the pad is based on encrypting the last-- so a first byte is needed. Original code used an uninitialized x on purpose in order to get a supposedly unpredictable byte out of RAM. To make valgrind happy (and truly to make the algorithm better) x is now initialized by encrypting a 0 with the pad generator. This value is not directly exposed in the generated pad. The first byte in the one time pad is not the result of encrypting 0 but instead the result of encrypting the result of that operation. So, the first byte is based on the state of the pad generator just prior to making the OneTimePad. This is probably harder to predict than the state of the stack (where x would have come from) anyway.

git-svn-id: https://svn.microneil.com/svn/SNFMulti/trunk@23 dc71a809-1921-45c4-985c-09c81d0142d9

snfNETmgr.cpp

@@ -315,7 +315,7 @@ void snfNETmgr::evolvePad(string Entropy) {
 PadBuffer snfNETmgr::OneTimePad(int Len) {                                      // Get Len bytes of one time pad.
     PadBuffer B;                                                                // Start with a buffer.
     B.reserve(Len);                                                             // Reserve Len bytes.
-    unsigned char x;                                                            // Get an unsigned char, unknown value.
+    unsigned char x = PadGenerator.Encrypt(0);                                  // Get an unexposed byte to start with.
     for(int a = 0; a < Len; a++) {                                              // Create Len bytes of pad by evolving
         B.push_back(x = PadGenerator.Encrypt(x));                               // x through itself and copying the
     }                                                                           // data into the buffer.