arne
/
cryptopp
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Update comments

pull/795/head
Jeffrey Walton 2019-01-25 19:49:17 -05:00
parent 779e28a9b0
commit 82f80124e6
No known key found for this signature in database
GPG Key ID: B36AB348921B1838
1 changed files with 9 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
chacha.cpp
View File

@ -425,7 +425,10 @@ void ChaChaTLS_Policy::CipherResynchronize(byte *keystreamBuffer, const byte *IV
void ChaChaTLS_Policy::SeekToIteration(lword iterationCount)
{
// Should we throw here???
// Should we throw here??? If the initial block counter is
// large then we can wrap and process more data as long as
// data processed in the security context does not exceed
// 2^32 blocks or approximately 256 GB of data.
CRYPTOPP_ASSERT(iterationCount <= std::numeric_limits<word32>::max());
m_state[12] = (word32)iterationCount; // low word
}
@ -447,11 +450,12 @@ void ChaChaTLS_Policy::OperateKeystream(KeystreamOperation operation,
ChaCha_OperateKeystream(operation, m_state, m_state[12], discard,
m_rounds, output, input, iterationCount);
// If this fires it means ChaCha_OperateKeystream generated a carry
// that was discarded. The problem is, the RFC does not specify what
// should happen when the counter block wraps. All we can do is
// inform the user that something bad may happen because we don't
// If this fires it means ChaCha_OperateKeystream generated a counter
// block carry that was discarded. The problem is, the RFC does not
// specify what should happen when the counter block wraps. All we can
// do is inform the user that something bad may happen because we don't
// know what we should do.
// Also see https://github.com/weidai11/cryptopp/issues/790.
CRYPTOPP_ASSERT(discard==0);
}