madscientist
/
SNFMulti
Observar 1
Favorito 0
Fork 0
Código Issues 0 Pull requests 0 Versões 0 Wiki Atividade
101 Commits
3 Branches
Tag: 869c039bef
Branches Tags
${ item.name }
Criar branch ${ searchTerm }
de 869c039bef
${ noResults }
Gráfico de commits

11 Commits (869c039bef12a6cdc191781f0c0a76dd7eb00c85)

Autor SHA1 Mensagem Data
  Pete McNeil 3a4f5ea518 MANGLER to Mangler - conformity 4 anos atrás
  Pete McNeil 43d297c8bd finish up namespace tidy to get a clean build 4 anos atrás
  Pete McNeil d5d8aaefca tidy namespace snfNETmgr 4 anos atrás
  Pete McNeil e9e960f4b5 RuntimeCheck to cd::RuntimeCheck 4 anos atrás
  Pete McNeil 28ae11eac4 snfNETmgr not using namespace std 4 anos atrás
  Pete McNeil 3bf13f0602 Tweaked RuntimeCheck descriptions 4 anos atrás
  Pete McNeil 978f01d630 Cleaned up timestamp functions 4 anos atrás
  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. 15 anos atrás
  madscientist 08a48da626 Minor tweaks to eliminate compiler warnings in snfNETmgr.* 15 anos atrás
  madscientist 7faa99d01f Re-factored for CodeDweller separation 15 anos atrás
  madscientist b313d3961a setup 15 anos atrás