mmb
Write test code to make sure nothing goes terribly wrong with encryption/decryption/authentication.
We should make a list of every known "fuckup vector" of anything security-critical we do (or use from an external library).
Then, write code to test it the best way we can.
And run this test code as often as possible when making changes to the codebase (arguably before any commit).
This will require some careful thoughts and as much external review/feedbacks as possible, but should nonetheless be considered a priority.
Marking it as part of the 1.2.0 milestone to make sure we don't forget it before the next release.
I suggest performing any security operation in a completely separated C code using its own crypto primitives, and checking against these results.
That way we completely eliminate the possibility of python/potr/athything messing with the checks themselves without being detected.
I started a test suite using unittest.
It needs a lot more tests and the weechat mock will need to have more added to it as we test more things.
