madscientist
/
SNFMulti
Beobachten 1
Favorisieren 0
Fork 0
Code Issues 0 Pull-Requests 0 Releases 0 Wiki Aktivität
97 Commits
3 Branches
Struktur: b3ea1b3ee3
Branches Tags
${ item.name }
Erstelle Branch ${ searchTerm }
von „b3ea1b3ee3“
${ noResults }
Commit graph

9 Commits (b3ea1b3ee3ab10235902196ea4acfd5b062d7274)

Autor SHA1 Nachricht Datum
  Pete McNeil d5d8aaefca tidy namespace snfNETmgr vor 4 Jahren
  Pete McNeil e9e960f4b5 RuntimeCheck to cd::RuntimeCheck vor 4 Jahren
  Pete McNeil 28ae11eac4 snfNETmgr not using namespace std vor 4 Jahren
  Pete McNeil 3bf13f0602 Tweaked RuntimeCheck descriptions vor 4 Jahren
  Pete McNeil 978f01d630 Cleaned up timestamp functions vor 4 Jahren
  madscientist 6d3a6a8abf 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. vor 15 Jahren
  madscientist 08a48da626 Minor tweaks to eliminate compiler warnings in snfNETmgr.* vor 15 Jahren
  madscientist 7faa99d01f Re-factored for CodeDweller separation vor 15 Jahren
  madscientist b313d3961a setup vor 15 Jahren